RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 4873, "GMPLS Segment Recovery", May 2007

Note: This RFC has been updated by RFC 9270

Source of RFC: ccamp (rtg)

Errata ID: 935
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Held for Document Update by: Adrian Farrel

 

Section 2

Near the end of the second-to-last paragraph on page 5, RFC 4873 says:

                                                        [...].  The
   branch node of a recovery LSP creates an SRRO by copying the RRO from
|  the Resv message of associated recovery LSP into a new SRRO object.
   Any SRROs present in the recovery LSP's Resv message are also copied.

It should say:
                                                        [...].  The
   branch node of a recovery LSP creates an SRRO by copying the RRO from
|  the Resv message of the associated recovery LSP into a new SRRO
   object.  Any SRROs present in the recovery LSP's Resv message are
   also copied.

Rationale:  missing article.


Section 3.2

On page 7, the last sentence of Section 3.2 says:

|              [...].  This object MUST NOT be used when association is
   made according to the methods defined in [RFC4090].

It should say:

|              [...].  This object MUST NOT be used when an association
   is made according to the methods defined in [RFC4090].

Rationale:  missing article.


Section 4.1

On page 8, Section 4.1 says:

                   [...].  This includes the definition of subobjects
|  defined for EXPLICIT_ROUTE object.  The class of the
   SECONDARY_EXPLICIT_ROUTE object is 200 (of the form 11bbbbbb).

It should say:

                   [...].  This includes the definition of subobjects
|  defined for the EXPLICIT_ROUTE object.  The class of the
   SECONDARY_EXPLICIT_ROUTE object is 200 (of the form 11bbbbbb).

Rationale:  missing article.


Section 4.2

In the second paragraph on page 10, Section 4.2 says:

|  At a branch node, the SERO, together with the Path message of LSP
   being recovered, provides the information to create the recovery LSP.
   [...]

It should say:

|  At a branch node, the SERO, together with the Path message of the LSP
   being recovered, provides the information to create the recovery LSP.
   [...]

Rationale:  missing article.


Section 4.2.1

Near the bottom of page 10, the first paragraph of Section 4.2.1 says:

                                                          [...].  The
|  processing of these events depend on a number of factors.

It should say:
                                                          [...].  The
|  processing of these events depends on a number of factors.
                                    ^
Rationale:  grammar.


Section 4.3.2

The second sentence of Section 4.3.2 says:

|                      [...].  When a branch or merge node receives
   notification of an LSP failure and it is unable to recover from that
   failure, [...]

It should say:
|                      [...].  When a branch or merge node receives a
   notification of an LSP failure and it is unable to recover from that
   failure, [...]

Rationale:  missing article.


Section 6.2

The last sentence of the third paragraph of Section 6.2,
on mid-page 17, says:

                                                             [...].  The
   dynamically identified information, together with the Path message of
|  LSP being recovered, is used to create the recovery LSP.

It should say:
                                                             [...].  The
   dynamically identified information, together with the Path message of
|  the LSP being recovered, is used to create the recovery LSP.

Rationale:  missing article.


It should say:

[see above]

Notes:

editorial nits.

from pending

Report New Errata



Advanced Search