draft-ietf-kitten-gssapi-extensions-iana-03.txt   draft-ietf-kitten-gssapi-extensions-iana-04.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: September 25, 2008 March 24, 2008 Expires: September 26, 2008 March 25, 2008
Namespace Considerations and Registries for GSS-API Extensions Namespace Considerations and Registries for GSS-API Extensions
draft-ietf-kitten-gssapi-extensions-iana-03.txt draft-ietf-kitten-gssapi-extensions-iana-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 25, 2008. This Internet-Draft will expire on September 26, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes the ways in which the GSS-API may be extended This document describes the ways in which the GSS-API may be extended
and directs the creation of an IANA registry for various GSS-API and directs the creation of an IANA registry for various GSS-API
namespaces. namespaces.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
3. Extensions to the GSS-API . . . . . . . . . . . . . . . . . 3 3. Extensions to the GSS-API . . . . . . . . . . . . . . . . 3
4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . 3 4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . 3
5. Language Binding-Specific GSS-API Namespaces . . . . . . . 4 5. Language Binding-Specific GSS-API Namespaces . . . . . . . 4
6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . 4 6. Extension-Specific GSS-API Namespaces . . . . . . . . . . 4
7. Registration Form(s) . . . . . . . . . . . . . . . . . . . 4 7. Registration Form . . . . . . . . . . . . . . . . . . . . 4
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . 6
8.1. Initial Namespace Registrations . . . . . . . . . . . . . . 6 8.1. Initial Namespace Registrations . . . . . . . . . . . . . 7
8.2. Registration Maintenance Guidelines . . . . . . . . . . . . 6 8.2. Registration Maintenance Guidelines . . . . . . . . . . . 7
8.2.1. Expert Reviews of Individual Submissions . . . . . . . . . 7 8.2.1. Sub-Namespace Symbol Pattern Matching . . . . . . . . . . 7
9. Security Considerations . . . . . . . . . . . . . . . . . . 7 8.2.2. Expert Reviews of Individual Submissions . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . 8 8.2.3. Change Control . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9. Security Considerations . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . . 8 10. References . . . . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . 8 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . 11
1. Conventions used in this document 1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
There is a need for private-use and mechanism-specific extensions to There is a need for private-use and mechanism-specific extensions to
the Generic Security Services Application Programming Interface (GSS- the Generic Security Services Application Programming Interface (GSS-
API). As such extensions are designed and standardized (or not), API). As such extensions are designed and standardized (or not),
both at the IETF and elsewhere, there is a non-trivial risk of both at the IETF and elsewhere, there is a non-trivial risk of
namespace pollution and conflicts. To avoid this we set out namespace pollution and conflicts. To avoid this we set out
guidelines for extending the GSS-API and direct the creation of an guidelines for extending the GSS-API and direct the creation of an
IANA registry for GSS-API namespaces. IANA registry for GSS-API namespaces.
Registrations of individual items and sub-namespaces are allowed. Registrations of individual items and sub-namespaces are allowed.
Each sub-namespace may provide different rules for registration, Each sub-namespace may provide different rules for registration,
e.g., for mechanism-specific and private-use extensions. All e.g., for mechanism-specific and private-use extensions.
Standards-Track uses of the GSS-API namespaces will be registered as
part of the RFC publication process. See Section 8.2.
3. Extensions to the GSS-API 3. Extensions to the GSS-API
Extensions to the GSS-API can be categorized as follows: Extensions to the GSS-API can be categorized as follows:
o Abstract API extensions o Abstract API extensions
o Implementation-specific o Implementation-specific
o Mechanism-specific o Mechanism-specific
o Language binding-specific o Language binding-specific
Extensions to the GSS-API may be purely semantic, without effect on Extensions to the GSS-API may be purely semantic, without effect on
skipping to change at page 3, line 48 skipping to change at page 3, line 46
namespaces. namespaces.
Extensions that affect the GSS-API namespaces should be registered Extensions that affect the GSS-API namespaces should be registered
with the IANA as described herein. with the IANA as described herein.
4. Generic GSS-API Namespaces 4. Generic GSS-API Namespaces
The abstract API namespaces for the GSS-API are: The abstract API namespaces for the GSS-API are:
o Type names o Type names
o Function names o Function names
o Constant names for each type o Constant names for various types
o Constant values for each type o Constant values for various types
o Name types (OID, type name and syntaxes) o Name types (OID, type name and syntaxes)
Additionally we have namespaces associates with the OBJECT IDENTIFIER Additionally we have namespaces associates with the OBJECT IDENTIFIER
(OID) type: (OID) type. The IANA already maintains a registry of such OIDs:
o Mechanism OIDs o Mechanism OIDs
o Name Type OIDs o Name Type OIDs
5. Language Binding-Specific GSS-API Namespaces 5. Language Binding-Specific GSS-API Namespaces
Language binding specific namespaces include: Language binding specific namespaces include, among others:
o Header/interface module names o Header/interface module names
o Object classes and/or types o Object classes and/or types
o Methods and/or functions o Methods and/or functions
o Constant names o Constant names
o Constant values o Constant values
6. Extension-Specific GSS-API Namespaces 6. Extension-Specific GSS-API Namespaces
Extensions to the GSS-API may create additional namespaces. See Extensions to the GSS-API may create additional namespaces. See
Section 8.2. Section 8.2.
7. Registration Form(s) 7. Registration Form
Registrations for GSS-API namespaces SHALL take the following form: Registrations for GSS-API namespaces SHALL take the following form:
+----------------+--------------------+-----------------------------+ +--------------+---------------------+------------------------------+
| Registration | Possible Values | Description | | Registration | Possible Values | Description |
| Field | | | | Field | | |
+----------------+--------------------+-----------------------------+ +--------------+---------------------+------------------------------+
| Registration | 'Instance', | Indicates whether this | | Registration | 'Instance', | Indicates whether this entry |
| type | 'Sub-Namespace' | entry reserves a given | | type | 'Sub-Namespace' | reserves a given symbol name |
| | | symbol name (and possibly, | | | | (and possibly, constant |
| | | constant value), or whether | | | | value), or whether it |
| | | it reserves an entire | | | | reserves an entire |
| | | sub-namespace (the name is | | | | sub-namespace (the name is a |
| | | a "prefix") or constant | | | | pattern) or constant value |
| | | value range. | | | | range. |
+----------------+--------------------+-----------------------------+ +--------------+---------------------+------------------------------+
| Bindings | 'Generic', | Indicates the name of the | | Bindings | 'Generic', | Indicates the name of the |
| | 'C-bindings', | programming language that | | | 'C-bindings', | programming language that |
| | 'Java', 'C#', | this registration involves, | | | 'Java', 'C#', | this registration involves, |
| | <programming | or, if 'Generic', that this | | | <programming | or, if 'Generic', that this |
| | language name> | is an entry for the generic | | | language name> | is an entry for the generic |
| | | abstract GSS-API (i.e., not | | | | abstract GSS-API (i.e., not |
| | | specific to any programming | | | | specific to any programming |
| | | language). | | | | language). |
+----------------+--------------------+-----------------------------+ +--------------+---------------------+------------------------------+
| Object Type | 'Data-Type', | Indicates the type of the | | Object Type | 'Data-Type', | Indicates the type of the |
| | 'Function', | object(s) whose symbolic | | | 'Function', | object whose symbolic name |
| | 'Method', | name or constant value this | | | 'Method', | or constant value this entry |
| | 'Integer', | entry registers. The | | | 'Integer', | registers. The possible |
| | 'String', 'OID', | possible values of this | | | 'String', 'OID', | values of this field depend |
| | 'Context Flag', | field depend on the | | | 'Context-Flag', | on the programming language |
| | 'Name Type', | programming language in | | | 'Name-Type', | in question, therefore they |
| | 'Header File | question, therefore they | | | 'Macro', | are not all specified here. |
| | Name', etcetera | are not all specified here. | | | 'Header-File-Name', | |
+----------------+--------------------+-----------------------------+ | | 'Module-Name', | |
| Symbol | <Symbol name or | The name(s) of symbols or | | | 'Class', etcetera | |
| Name/Prefix | name prefix> | values being registered. | +--------------+---------------------+------------------------------+
+----------------+--------------------+-----------------------------+ | Symbol | <Symbol name or | The name of a symbol or |
| Binding of | <Name of abstract | If the registration is for | | Name/Prefix | name pattern> | symbol sub-namespace being |
| | API element of | a specific language binding | | | | registered. See |
| | which this object | of the GSS-API, then this | | | | Section 8.2.1 |
| | is a binding> | names the abstract API | +--------------+---------------------+------------------------------+
| | | element of which it is a | | Binding of | <Name of abstract | If the registration is for a |
| | | binding (OPTIONAL). | | | API element of | specific language binding of |
+----------------+--------------------+-----------------------------+ | | which this object | the GSS-API, then this names |
| Constant | <Constant value> | The value(s) of the | | | is a binding> | the abstract API element of |
| Value/Range(s) | or <constant value | constant named by the | | | | which it is a binding |
| | range> | <Symbol Name/Prefix> |
| | | (OPTIONAL). | | | | (OPTIONAL). |
+----------------+--------------------+-----------------------------+ +--------------+---------------------+------------------------------+
| Description | <Text> | Description of object(s) | | Constant | <Constant value> or | The value of the constant |
| | | being registered. | | Value/Range | <constant value | named by the <Symbol |
+----------------+--------------------+-----------------------------+ | | range> | Name/Prefix>. This field is |
| | | present only for Instance |
| | | and Sub-namespace |
| | | registrations of Constant |
| | | object types. |
+--------------+---------------------+------------------------------+
| Description | <Text> | Description of the |
| | | registration. Multiple |
| | | instances of this field may |
| | | result (see Section 8.2.3). |
+--------------+---------------------+------------------------------+
| Registration | Values from | Describes the rules for | | Registration | Values from | Describes the rules for |
| Rules | [RFC2434], such as | allocation of items that | | Rules | [RFC2434], such as | allocation of items that |
| | 'IESG Approval', | fall in this sub-namespace, | | | 'IESG Approval', | fall in this sub-namespace, |
| | 'Expert Review', | for entries with Rgistratio | | | 'Expert Review', | for entries with |
| | 'First Come First | Type of Sub-namespace | | | 'First Come First | Registration Type of |
| | Served', 'Private | (OPTIONAL). For private use | | | Served', 'Private | Sub-namespace (OPTIONAL). |
| | Use', etcetera. | sub-namespaces the | | | Use', etcetera. | For private use |
| | | submitter MUST provide the | | | | sub-namespaces the submitter |
| | | e-mail address of a | | | | MUST provide the e-mail |
| | | responsible contact. | | | | address of a responsible |
+----------------+--------------------+-----------------------------+ | | | contact. |
| Reference | <Reference> | Reference to document that | | Reference | <Reference> | Reference to document that |
| | | describes the object(s) | | | | describes the registration, |
| | | being registered, if any | | | | if any (OPTIONAL). Multiple |
| | | (OPTIONAL). | | | | instances of this field are |
+----------------+--------------------+-----------------------------+ | | | allowed, with one reference |
| Expert | <Name of expert | (OPTIONAL, see | | | | each. |
| Reviewer(s) | reviewers, | Section 8.2.1) | +--------------+---------------------+------------------------------+
| | possibly WG names> | | | Expert | <Name of expert | OPTIONAL, see Section 8.2.2. |
+----------------+--------------------+-----------------------------+ | Reviewer | reviewers, possibly | Multiple instances of this |
| Status | 'Standards-Track', | Status of the registration. | | | WG names> | field are allowed, with one |
| | 'Informational', | | | | | expert reviewer |
| | 'Experimental', | | | | | per-instance. |
| | 'Obsolete', | | +--------------+---------------------+------------------------------+
| | 'Other' | | | Expert | <Notes from the | Expert reviewers may request |
+----------------+--------------------+-----------------------------+ | Review Notes | expert review> | that some comments be |
| | | included with the |
| | | registration, e.g., |
| | | regarding security |
| | | considerations of the |
| | | registered extension. |
+--------------+---------------------+------------------------------+
| Status | 'Registered', | Status of the registration. |
| | 'Obsoleted' | |
+--------------+---------------------+------------------------------+
| Obsoleting | <Reference> | Reference to document, if |
| Reference | | any, that obsoletes this |
| | | registration. Multiple |
| | | instances of this field are |
| | | allowed, with one reference |
| | | each. (OPTIONAL) |
+--------------+---------------------+------------------------------+
The IANA should create a single GSS-API namespace registry, or The IANA should create a single GSS-API namespace registry, or
multiple registries, one for symbolic names and one for constant multiple registries, one for symbolic names and one for constant
values, and/or it may create a registry per-programming language, at values, and/or it may create a registry per-programming language, at
its convenience. its convenience.
Entries in these registries should consist of all the fields from Entries in these registries should consist of all the fields from
their corresponding registration entries. their corresponding registration entries.
Entries should be sorted by: registration type, progamming language, Entries should be sorted by: registration type, progamming language,
object type, and symbol name/prefix. object type, and symbol name/pattern.
8. IANA Considerations 8. IANA Considerations
This document deals with IANA considerations throughout. This document deals with IANA considerations throughout.
Specifically it creates a single registry of various kinds of things, Specifically it creates a single registry of various kinds of things,
thought the IANA may instead create multiple registries each for one thought the IANA may instead create multiple registries each for one
of those kinds of things. Of particular interest may be that IANA of those kinds of things. Of particular interest may be that IANA
will now be the registration authority for the GSS-API name type OID will now be the registration authority for the GSS-API name type OID
space. space.
skipping to change at page 6, line 46 skipping to change at page 7, line 22
[RFC2743], [RFC2744], [RFC2853], [RFC1964] and [RFC4121] and others [RFC2743], [RFC2744], [RFC2853], [RFC1964] and [RFC4121] and others
will be supplied during the IANA review portion of the RFC publishing will be supplied during the IANA review portion of the RFC publishing
process. The KITTEN WG chairs MUST indicate that such content has process. The KITTEN WG chairs MUST indicate that such content has
been reviewed by the WG and that there is WG consensus that the been reviewed by the WG and that there is WG consensus that the
entries are in agreement with those RFCs. entries are in agreement with those RFCs.
8.2. Registration Maintenance Guidelines 8.2. Registration Maintenance Guidelines
Standards-Track RFCs can create new items with any non-conflicting Standards-Track RFCs can create new items with any non-conflicting
Symbol Name/Prefix value for this registry by virtue of IESG approval Symbol Name/Prefix value for this registry by virtue of IESG approval
to publish as a Standards-Track RFC. The status of such entries to publish as a Standards-Track RFC -- that is, without additional
SHALL initially be as specified by the RFC (defaulting to 'Standards- expert review.
Track').
Standards-Track RFCs can mark existing entries as obsolete or Standards-Track RFCs can mark existing entries as obsolete, and can
historic, and can even create conflicting entries if explicitly even create conflicting entries if explicitly stated (the IESG, of
stated (the IESG, of course, should review conflicts very carefully). course, should review conflicts carefully, and may reject them).
IANA shall also consider submissions from individuals, and via IANA shall also consider submissions from individuals, and via
Informational and Experimental RFCs, subject to Expert Review. IANA Informational and Experimental RFCs, subject to Expert Review. IANA
SHALL allow such registrations if a) they are not conflicting, and b) SHALL allow such registrations if a) they are not conflicting, b)
if expert review passes. Guidelines for expert reviews are given provided that the registration is for object types other than
below. The Status of any such registrations SHALL agree with the Context-Flags, and c) subject to expert review. Guidelines for
Status of the source RFC, or, for individual registrations, 'Other'. expert reviews are given below.
8.2.1. Expert Reviews of Individual Submissions 8.2.1. Sub-Namespace Symbol Pattern Matching
Expert review selection SHALL be as follows. If, at the time that Sub-namespace registrations must provide a pattern for matching
the IANA receives an individual submission for registration in this symbols for which the sub-namespace's registration rules apply. The
registry, there is are any IETF Working Groups chartered to produce pattern consists of a string with the following special tokens:
GSS-API-related documents, then the IANA SHALL ask the chairs of such o '*', meaning "match any string."
WGs to be expert reviewers or to name one. If there are no such WGs o "%m", meaning "match any mechanism family short-hand name."
at that time, then the IANA SHALL ask past chairs of the KITTEN WG o "%i", meaning "match any implementor vanity short-hand name."
and the author/editor of this RFC to act as expert reviewers or name
an alternate. For example, "GSS_%m_*" matches "GSS_krb5_foo" since "krb5" is a
common short-hand for the Kerberos V GSS-API mechanism [RFC1964].
But "GSS_%m_*" does not match "GSS_foo_bar" unless "foo" is asserted
to be a short-hand for some mechanism.
8.2.2. Expert Reviews of Individual Submissions
Expert review selection SHALL be done as follows. If, at the time
that the IANA receives an individual submission for registration in
this registry, there is are any IETF Working Groups chartered to
produce GSS-API-related documents, then the IANA SHALL ask the chairs
of such WGs to be expert reviewers or to name one. If there are no
such WGs at that time, then the IANA SHALL ask past chairs of the
KITTEN WG and the author/editor of this RFC to act as expert
reviewers or name an alternate.
Expert reviewers of individual registration submissions with Expert reviewers of individual registration submissions with
Registration Type == Sub-namespace should check that the registration Registration Type == Sub-namespace should check that the registration
request has a suitable description (which need not be sufficiently request has a suitable description (which need not be sufficiently
detailsed for others to implement) and that the Symbol Name/Prefix is detailsed for others to implement) and that the Symbol Name/Prefix is
sufficiently descriptive of the purpose of the sub-namespace or the sufficiently descriptive of the purpose of the sub-namespace or
name of the submitter or associated company. reflective of the name of the submitter or associated company.
Expert reviewers of individual registration submissions with Expert reviewers of individual registration submissions with
Registration Type == Instance should check that the Symbol Name falls Registration Type == Instance should check that the Symbol Name falls
under a sub-namespace controlled by the submitter and that the Status under a sub-namespace controlled by the submitter. Registration of
of the submission is "Informational." Registration of such entries such entries which do not fall under such a sub-namespace may be
which do not fall under such a sub-namespace may be allowed provided allowed provided that they correspond to long existing non-standard
that they correspond to long existing non-standard extensions to the extensions to the GSS-API and this can be easily checked or
GSS-API and this can be easily checked or demonstrated, otherwise demonstrated, otherwise IESG Protocol Action is REQUIRED (see
IESG Protocol Action is REQUIRED (see previous section). Also, previous section). Also, reviewers should check that any
reviewers should check that any registration of constant values for registration of constant values have a detailed description that is
types which have Standard-Track status have a detailed description suitable for other implementors to reproduce, and that they don't
that is suitable for other implementors to reproduce, and that they conflict with other usages or are otherwise dangerous in the
don't conflict with other usages or are otherwise dangerous in the
reviewers estimation. reviewers estimation.
Expert reviewers should review impact on mechanisms, security and
interoperability, and may reject or annotate registrations which can
have mechanism impact that requires IESG protocol action. Consider,
for example, new versions of GSS_Init_sec_context() and/or
GSS_Accept_sec_context which have new input and/or output parameters
which imply changes on the wire or in behaviour that may result in
interoperability issues. A reviewer could choose to add notes to the
registration describing such issues, or the reviewer might conclude
that the danger to Internet interoperability is sufficient to warrant
rejecting the registration.
8.2.3. Change Control
Registered entries may be marked obsoleted using the same expert
review process as for registering entries. Obsoleted entries are
not, however, to be deleted, but merely marked having Obsoleted
Status. Note that entries may be created as obsoleted to record the
fact that the given symbol(s) have been used before, even though
continued use of them is discouraged.
Registered entries may also be updated in two other ways: additional
references, obsoleting references, and descriptions may be added.
All changes are subject to expert review. The submitter of a change
request need not be the same as the original submitter.
Registrations may be modified by addtion, but under no circumstance
may any fields be modified except for the Status field.
The IANA SHALL add a field describing the date that a an addition or
modification was made, and a description of the change.
9. Security Considerations 9. Security Considerations
This document has no security considerations. General security considerations relating to IANA registration
services apply; see [RFC2434].
Also, expert reviewers should look for and may document security
related issues with submitters' GSS-API extensions, to the best of
the reviewers' ability given the information furnished by the
submitter. Reviewers may add comments regarding their limited
ability to review a submission for security problems if the submitter
is unwilling to provide sufficient documentation.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
 End of changes. 29 change blocks. 
119 lines changed or deleted 194 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/