I have submitted updated documents 2833bis-15 and 2833bisdata-08. I
believe, as I stated before, that this clears all Discuss and IETF Last
Call comments.
Changes in 2833bis:
====================
Changed abstract to say this about the deprecated RFC 2833 event codes:
"The remainder of the event codes defined in RFC 2833 are
conditionally reserved in case other documents revive their use. See
Section 7 and Appendix A for details."
Changed the last part of the second paragraph of section 1.2 to say:
"Appendix A describes the changes from RFC 2833 [12] and in particular
indicates the disposition of the event codes defined in [12]."
In section 7 "IANA Considerations", added a paragraph to the expert
reviewer's duties as follows:
"The expert is further responsible for providing guidance on the
allocation of event codes to the proposed events. Specifically, the
expert must indicate whether the event appears to be the same as one
defined in RFC 2833 but not specified in any new document. In this
case the event code specified in RFC 2833 for that event SHOULD be
assigned to the proposed event. Otherwise event codes MUST be
assigned from the set of available event codes listed below. If this
set is exhausted, the criterion for assignment from the reserved set
of event codes is to first assign those that appear to have the
lowest probability of being revived in their RFC 2833 meaning in a
new specification."
Changed the description of available and reserved codes in section 7 to
read:
"Legal event codes range from 0 to 255. The initial registry content
is shown in Table 7, and consists of the sixteen events defined in
Section 3 of this document. The remaining codes have the following
disposition:
o codes 17-22, 50-51, 90-95, 113-120, 169, and 206-255 are available
for assignment;
o codes 23-40, 49, and 52-63 are reserved for events defined in
[16];
o codes 121-137 and 174-205 are reserved for for events defined in
[17];
o codes 16, 41-48, 64-88, 96-112, 138-168, and 170-173 are reserved
in the first instance for specifications reviving the
corresponding RFC 2833 events, and in the second instance for
general assignment after all other codes have been assigned."
Changed the last part of Appendix A in the spirit of the preceding
changes. In particular, Table 8 now shows all of the codes for the
deprecated RFC 2833 events as "Reserved".
Changes in 2833bisdata:
=======================
Changed the following event code assignments in the tables in which they
appear:
CRdSeg from 41 to 23
CReSeg from 43 to 24
MRdSeg from 46 to 25
MReSeg from 48 to 26
V32AC from 64 to 27
V8bISeg from 65 to 28
V8bRSeg from 66 to 29
V21L300 from 67 to 30
V21H300 from 68 to 31
Reordered the list in the IANA Considerations section accordingly.
Tom Taylor
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art
