Skip to main content

IPv6 Address Specific BGP Extended Community Attribute
draft-ietf-l3vpn-v6-ext-communities-02

Yes

(Ross Callon)

No Objection

(Alexey Melnikov)
(Dan Romascanu)
(Jari Arkko)
(Lisa Dusseault)
(Pasi Eronen)
(Robert Sparks)
(Tim Polk)

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

Ross Callon Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection (2009-08-13) Unknown
Comment removed as Discuss on draft-ietf-l3vpn-as4octet-ext-community cleared.
Alexey Melnikov Former IESG member
No Objection
No Objection () Unknown

                            
Dan Romascanu Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection (2009-08-11) Unknown
Section 1., paragraph 1:
>    IPv4 Addres Specific Extended Community, but do not support IPv6

  Nit: s/Addres/Address/


Section 4., paragraph 1:
>    All the security considerations for BGP Extended Communities apply
>    here.

  It would be useful to provide a reference.


Section 6., paragraph 2:
>    [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
>    Requirement Levels", BCP 14, RFC 2119, March 1997.

  The document doesn't use any RFC 2119 keywords, yet seems to have RFC
  2119 boilerplate text. Suggest to remove the text and the reference.
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Robert Sparks Former IESG member
No Objection
No Objection () Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection (2009-08-12) Unknown
I agree with Pasi's DISCUSS regarding optional transitive attributes. (We have unhappy operational experience that validates his concern.)

I recommend that we resolve the problem by inserting a normative reference to draft-scudder-idr-optional-transitive-01. While we could approve the current document today, we couldn't publish it until draft-scudder-idr-optional-transitive-01 is also published.

We should encourage the idr wr to expedite work on that draft-scudder-idr-optional-transitive-01.
Russ Housley Former IESG member
No Objection
No Objection (2009-08-12) Unknown
  It woudl be good to add the clarification requested in the Gen-ART
  review by Miguel Garcia to the IANA Considerations.  Please see:

  http://www.softarmor.com/rai/temp-gen-art/
    draft-ietf-l3vpn-v6-ext-communities-02-garcia.txt
Tim Polk Former IESG member
(was No Record, Discuss) No Objection
No Objection () Unknown