Commit b6bc758b authored by Darshak Thakore's avatar Darshak Thakore

Setup repository for draft-dthakore-scte-urn

parent 7035db9c
*.redxml
*.txt
*.html
*.pdf
*~
*.swp
/*-[0-9][0-9].xml
.refcache
venv/
issues.json
draft-dthakore-scte-urn.xml
[submodule "lib"]
path = lib
url = git@github.com:martinthomson/i-d-template
language: python
sudo: false
addons:
apt:
packages:
- python-pip
install:
- gem install kramdown-rfc2629
- pip install xml2rfc
script: make ghpages
# Contributing
Before submitting feedback, please familiarize yourself with our current issues
list and review the [working group
documents](https://datatracker.ietf.org/wg/scte/documents/) and [mailing
list discussion](https://mailarchive.ietf.org/arch/browse/scte/). If you're
new to this, you may also want to read the [Tao of the
IETF](https://www.ietf.org/tao.html).
Be aware that all contributions to the specification fall under the "NOTE WELL"
terms outlined below.
1. The best way to provide feedback (editorial or design) and ask questions is
sending an e-mail to our mailing list
([info](https://www.ietf.org/mailman/listinfo/scte)). This will ensure that
the entire Working Group sees your input in a timely fashion.
2. If you have **editorial** suggestions (i.e., those that do not change the
meaning of the specification), you can either:
a) Fork this repository and submit a pull request; this is the lowest
friction way to get editorial changes in.
b) Submit a new issue to Github, and mention that you believe it is editorial
in the issue body. It is not necessary to notify the mailing list for
editorial issues.
c) Make comments on individual commits in Github. Note that this feedback is
processed only with best effort by the editors, so it should only be used for
quick editorial suggestions or questions.
3. For non-editorial (i.e., **design**) issues, you can also create an issue on
Github. However, you **must notify the mailing list** when creating such issues,
providing a link to the issue in the message body.
Note that **github issues are not for substantial discussions**; the only
appropriate place to discuss design issues is on the mailing list itself.
## NOTE WELL
Any submission to the [IETF](https://www.ietf.org/) intended by the Contributor
for publication as all or part of an IETF Internet-Draft or RFC and any
statement made within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF sessions, as
well as written and electronic communications made at any time or place, which
are addressed to:
* The IETF plenary session
* The IESG, or any member thereof on behalf of the IESG
* Any IETF mailing list, including the IETF list itself, any working group
or design team list, or any other list functioning under IETF auspices
* Any IETF working group or portion thereof
* Any Birds of a Feather (BOF) session
* The IAB or any member thereof on behalf of the IAB
* The RFC Editor or the Internet-Drafts function
* All IETF Contributions are subject to the rules of
[RFC 5378](https://tools.ietf.org/html/rfc5378) and
[RFC 3979](https://tools.ietf.org/html/rfc3979)
(updated by [RFC 4879](https://tools.ietf.org/html/rfc4879)).
Statements made outside of an IETF session, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not IETF Contributions in the context of this notice.
Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and [RFC
3979](https://tools.ietf.org/html/rfc3979) for details.
A participant in any IETF activity is deemed to accept all IETF rules of
process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity acknowledges that written, audio and video
records of meetings may be made and may be available to the public.
include lib/main.mk
lib/main.mk:
ifneq (,$(shell git submodule status lib 2>/dev/null))
git submodule sync
git submodule update --init
else
git clone --depth 10 -b master https://github.com/martinthomson/i-d-template.git lib
endif
# iana-scte-urn
IETF draft to register scte urn in IANA
# Full Title
This is the working area for the Individual internet-draft, "Full Title".
* [Editor's copy](https://cablelabs.github.io/iana-scte-urn/)
* [Individual Draft] (https://tools.ietf.org/html/draft-dthakore-scte-urn)
## Building the Draft
Formatted text and HTML versions of the draft can be built using `make`.
```sh
$ make
```
This requires that you have the necessary software installed. See [the
instructions](https://github.com/martinthomson/i-d-template/blob/master/doc/SETUP.md).
## Contributing
Before submitting feedback, please familiarize yourself with our current issues
list and review the [working group
documents](https://datatracker.ietf.org/wg/scte/documents/) and [mailing
list discussion](https://mailarchive.ietf.org/arch/browse/scte/). If you're
new to this, you may also want to read the [Tao of the
IETF](https://www.ietf.org/tao.html).
Be aware that all contributions to the specification fall under the "NOTE WELL"
terms outlined below.
1. The best way to provide feedback (editorial or design) and ask questions is
sending an e-mail to our mailing list
([info](https://www.ietf.org/mailman/listinfo/scte)). This will ensure that
the entire Working Group sees your input in a timely fashion.
2. If you have **editorial** suggestions (i.e., those that do not change the
meaning of the specification), you can either:
a) Fork this repository and submit a pull request; this is the lowest
friction way to get editorial changes in.
b) Submit a new issue to Github, and mention that you believe it is editorial
in the issue body. It is not necessary to notify the mailing list for
editorial issues.
c) Make comments on individual commits in Github. Note that this feedback is
processed only with best effort by the editors, so it should only be used for
quick editorial suggestions or questions.
3. For non-editorial (i.e., **design**) issues, you can also create an issue on
Github. However, you **must notify the mailing list** when creating such issues,
providing a link to the issue in the message body.
Note that **github issues are not for substantial discussions**; the only
appropriate place to discuss design issues is on the mailing list itself.
## NOTE WELL
Any submission to the [IETF](https://www.ietf.org/) intended by the Contributor
for publication as all or part of an IETF Internet-Draft or RFC and any
statement made within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF sessions, as
well as written and electronic communications made at any time or place, which
are addressed to:
* The IETF plenary session
* The IESG, or any member thereof on behalf of the IESG
* Any IETF mailing list, including the IETF list itself, any working group
or design team list, or any other list functioning under IETF auspices
* Any IETF working group or portion thereof
* Any Birds of a Feather (BOF) session
* The IAB or any member thereof on behalf of the IAB
* The RFC Editor or the Internet-Drafts function
* All IETF Contributions are subject to the rules of
[RFC 5378](https://tools.ietf.org/html/rfc5378) and
[RFC 3979](https://tools.ietf.org/html/rfc3979)
(updated by [RFC 4879](https://tools.ietf.org/html/rfc4879)).
Statements made outside of an IETF session, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not IETF Contributions in the context of this notice.
Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and [RFC
3979](https://tools.ietf.org/html/rfc3979) for details.
A participant in any IETF activity is deemed to accept all IETF rules of
process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity acknowledges that written, audio and video
records of meetings may be made and may be available to the public.
machine:
python:
version: 2.7.6
ruby:
version: 2.2.3
checkout:
post:
- git fetch origin gh-pages --depth 10
dependencies:
pre:
- pip install xml2rfc
- gem install kramdown-rfc2629
test:
override:
- make
deployment:
production:
branch: /.*/
commands:
- make ghpages
This diff is collapsed.
Subproject commit 230fda2bbbfc94d9cc700589a76bf09be89730b3
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment