Re: [CCAMP] [Editorial Errata Reported] RFC7139 (3924)

["Adrian Farrel" <[e-mail]>]

Hi Fatai,

I'm having trouble understanding the report.

RFC 4328 shows the value 5 as "reserved (for future use)." This is the
equivalent of the IANA tag "Unassigned".

RFC 7139 creates the "OTN Signal Type" registry and includes the value 5 as
Unassigned.

I don't find any other mention of the value 5 in RFC 7139, so I don't understand
how this value is being specially treated. In particular, I don't find any
mention in the table of Signal Types in section 5.

Also, I don't understand the meaning of "Reserved (for G.709)". Does it mean
that the G.709 Recommendation can make a code point allocation? Does it mean
that a future update of RFC 7139 might want to request allocation of this value
for a very specific purpose and so it would be bad to allocate it for something
else?

And lastly, given that these are OTN signal types, and given that OTN is defined
in G.709, why would this value need special reservation treatment "for G.709"?

I'm inclined to reject your Errata Report, but want to give you a chance to
clarify.

Thanks,
Adrian

> -----Original Message-----
> From: RFC Errata System [mailto:[e-mail]]
> Sent: 21 March 2014 03:05
> To: [e-mail]; [e-mail];
> [e-mail]; [e-mail];
> [e-mail]; [e-mail]; [e-mail];
> [e-mail]; [e-mail]
> Cc: [e-mail]; [e-mail]; [e-mail]
> Subject: [Editorial Errata Reported] RFC7139 (3924)
> 
> The following errata report has been submitted for RFC7139,
> "GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport
> Networks".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7139&eid=3924
> 
> --------------------------------------
> Type: Editorial
> Reported by: Fatai Zhang <[e-mail]>
> 
> Section: 11
> 
> Original Text
> -------------
> 5        Unassigned                            [RFC4328]
> 
> 
> Corrected Text
> --------------
> 5       Reserved (for G.709)                  [RFC7139]
> 
> Notes
> -----
> (1)Unassigned->Reserved (for G.709)
> (2)[RFC4328]->[RFC7139]
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC7139 (draft-ietf-ccamp-gmpls-signaling-g709v3-12)
> --------------------------------------
> Title               : GMPLS Signaling Extensions for Control of Evolving G.709
Optical
> Transport Networks
> Publication Date    : March 2014
> Author(s)           : F. Zhang, Ed., G. Zhang, S. Belotti, D. Ceccarelli, K.
Pithewan
> Category            : PROPOSED STANDARD
> Source              : Common Control and Measurement Plane
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG