Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)
RFC 4576

Note: This ballot was opened for revision 04 and is now closed.

(Alex Zinin) Yes

(Harald Alvestrand) No Objection

Comment (2004-02-05 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I have been reasured by the Routing ADs that there can never be a case where one OSPF network is connected to two 2547 VPNs that both inject routes into the OSPF network, and where it's expected to have routes related to one VPN injected into the other VPN.
If that ever happened, one bit is not enough - but apparently, OSPF isn't used that way.
If the document is revised for other reasons, a sentence or two saying so would be nice.

(Steven Bellovin) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ned Freed) No Objection

Comment (2004-01-30 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Silly nit: RFC 2119 terms defined and used to but RFC 2119 not listed in normative references.

(Ted Hardie) (was Discuss) No Objection

(Scott Hollenbeck) No Objection

Comment (2004-03-15)
No email
send info
I believe there should be a normative reference to RFC 2119 added (it's mentioned in the text, but not cited), but that's something the RFC Editor can address.

(Russ Housley) (was Discuss) No Objection

(David Kessens) No Objection

(Thomas Narten) No Objection

(Jon Peterson) No Objection

(Bert Wijnen) No Objection

(Allison Mankin) Abstain