[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mpls
Subject:    Re: [mpls] [Editorial Errata Reported] RFC7697 (4586)
From:       Loa Andersson <loa () pi ! nu>
Date:       2016-01-10 12:33:04
Message-ID: 56924F80.3020709 () pi ! nu
[Download RAW message or body]

Stewart,

Yes - exactly! However Errata is there to capture both technical and
editorial errors.

This is an editorial errata, if we neglect it, i.e. not add a note in
the errata system, that it is know and will be taken care of if we ever
do an update. The effect would be that we will see the same errata
reported over again; and a number mails that authors/chairs/ADs have to
respond to. Today this is piece of a cake, we are all up to speed, but
in the future what happen will fade into the background (new chairs/ADs)
and someone will have to dig into this to understand it.

Far better to  respond to the errata "Approved - hold for potential
update."

/Loa

On 2016-01-10 05:06, Stewart Bryant (stbryant) wrote:
> Loa
> 
> Surely this is of marginal value and should not be other than fixed in next update. \
> After all it will be obvious to the reader what the value is. 
> Stewart
> 
> Sent from my iPad
> 
> > On 9 Jan 2016, at 07:27, Loa Andersson <loa@pi.nu> wrote:
> > 
> > Deborah,
> > 
> > The nature of this is such that I don't we need to much process to
> > approve it. As the wg chair I support this. If you are OK with it
> > just go ahead and approve.
> > 
> > /Loa
> > 
> > > On 2016-01-09 15:17, RFC Errata System wrote:
> > > The following errata report has been submitted for RFC7697,
> > > "MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance \
> > > (OAM) Identifiers Management Information Base (MIB)". 
> > > --------------------------------------
> > > You may review the report below and at:
> > > http://www.rfc-editor.org/errata_search.php?rfc=7697&eid=4586
> > > 
> > > --------------------------------------
> > > Type: Editorial
> > > Reported by: Venkatesan Mahalingam <venkat.mahalingams@gmail.com>
> > > 
> > > Section: 9.1
> > > 
> > > Original Text
> > > -------------
> > > 9.1.  IANA Considerations for MPLS-OAM-ID-STD-MIB
> > > 
> > > IANA has to assign the OID { mplsStdMIB 21 } to the
> > > MPLS-OAM-ID-STD-MIB module specified in this document.
> > > 
> > > 
> > > Corrected Text
> > > --------------
> > > 9.1.  IANA Considerations for MPLS-OAM-ID-STD-MIB
> > > 
> > > IANA has assigned the OID { mplsStdMIB 21 } to the
> > > MPLS-OAM-ID-STD-MIB module specified in this document.
> > > 
> > > 
> > > Notes
> > > -----
> > > 
> > > 
> > > Instructions:
> > > -------------
> > > This erratum 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.
> > > 
> > > --------------------------------------
> > > RFC7697 (draft-ietf-mpls-tp-oam-id-mib-11)
> > > --------------------------------------
> > > Title               : MPLS Transport Profile (MPLS-TP) Operations, \
> > > Administration, and Maintenance (OAM) Identifiers Management Information Base \
> > > (MIB) Publication Date    : January 2016
> > > Author(s)           : P. Pan, S. Aldrin, M. Venkatesan, K. Sampath, T. Nadeau, \
> > > S. Boutros Category            : PROPOSED STANDARD
> > > Source              : Multiprotocol Label Switching
> > > Area                : Routing
> > > Stream              : IETF
> > > Verifying Party     : IESG
> > > 
> > 
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


[prev in list] [next in list] [prev in thread] [next in thread]