[bess] [IANA #830536] Protocol Action: 'BGP ACCEPT_OWN Community Attribute' to Proposed Standard (draft-ietf-l3vpn-acceptown-community-10.txt)

-John > > > On Jun 26, 2015, at 3:23 PM, Amanda Baber via RT > appro...@iana.org> wrote: > > > > Dear Authors: > > > > ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED > > > > We've completed the IANA Actions for the following RFC-to-be: > &

[bess] [IANA #830536] Protocol Action: 'BGP ACCEPT_OWN Community Attribute' to Proposed Standard (draft-ietf-l3vpn-acceptown-community-10.txt)

Dear Authors: ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED We've completed the IANA Actions for the following RFC-to-be: draft-ietf-l3vpn-acceptown-community-10 IANA has updated the reference for the following registration in the BGP Well-known Communities registry: 0x0001 ACCEPT

[bess] [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-06.txt)

C-ietf-bess-orf-covering-prefixes-03. Does that > make a difference? > > Also, I assume that this string will be replaced with an RFC number > when one is assigned. Is that right? > > Otherwise, it looks OK. > > Ron > > > > -Original Message- >

[bess] [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-06.txt)

Dear Authors: ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED We've completed the IANA Actions for the following RFC-to-be: draft-ietf-bess-orf-covering-prefixes-06 ACTION 1: IANA has updated the reference for the following BGP Outbound Route Filtering (ORF) Type: 65 CP-ORF [RFC-ietf-