Yes, IANA has acknowledged this.  But it won't appear in the registry 
until the draft is ready for publication as an RFC.

On 10/15/2018 11:53 PM, Xiejingrong wrote:
> BESS WG:
>
> Had the IANA ack'ed the request of adding the value 2 (Name LIR-PF) ?
>
> I have not seen it in 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_bgp-2Dparameters_bgp-2Dparameters.xhtml-23pmsi-2Dtunnel-2Dattributes&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=SLspw81-g1YnerSbyR4wVksLFbTE0tg5RiaFqroktpE&e=
>
> Thanks.
> Jingrong
>
> -----Original Message-----
> From: BESS [mailto:[email protected]] On Behalf Of 
> [email protected]
> Sent: Wednesday, October 10, 2018 12:53 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [bess] I-D Action: draft-ietf-bess-mvpn-expl-track-12.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
>
>          Title           : Explicit Tracking with Wild Card Routes in 
> Multicast VPN
>          Authors         : Andrew Dolganow
>                            Jayant Kotalwar
>                            Eric C. Rosen
>                            Zhaohui Zhang
>       Filename        : draft-ietf-bess-mvpn-expl-track-12.txt
>       Pages           : 18
>       Date            : 2018-10-09
>
> Abstract:
>     The MVPN specifications provide procedures to allow a multicast
>     ingress node to invoke "explicit tracking" for a multicast flow or
>     set of flows, thus learning the egress nodes for that flow or set of
>     flows.  However, the specifications are not completely clear about
>     how the explicit tracking procedures work in certain scenarios.  This
>     document provides the necessary clarifications.  It also specifies a
>     new, optimized explicit tracking procedure.  This new procedure
>     allows an ingress node, by sending a single message, to request
>     explicit tracking of each of a set of flows, where the set of flows
>     is specified using a wildcard mechanism.  This document updates RFCs
>     6514, 6625, and 7524.
>
>
> The IETF datatracker status page for this draft is:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dmvpn-2Dexpl-2Dtrack_&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=IbfNIjAs_IGX1-zHjQkho0Beih9ye-K5dJadYTD3KPc&e=
>
> There are also htmlized versions available at:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dbess-2Dmvpn-2Dexpl-2Dtrack-2D12&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=pvX7bR0yD-Ps5xQp5Chx9znYPBsvN1OPcOqdHykWbtk&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dietf-2Dbess-2Dmvpn-2Dexpl-2Dtrack-2D12&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=uEZq-1orypvLdV0mt38qRc6XnZUYPoeQlPGa7AboW6M&e=
>
> A diff from the previous version is available at:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dietf-2Dbess-2Dmvpn-2Dexpl-2Dtrack-2D12&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=5ARY4wCXV5wFMvi_B6cxOAwwbK10uQtiIEyLo1fyGoI&e=
>
>
> Please note that it may take a couple of minutes from the time of submission 
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_internet-2Ddrafts_&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=BD9UsKgQrN-hZxM4pV_hN0RYLbvP1_yHwv07FPpSHcQ&e=
>
> _______________________________________________
> BESS mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=x2nsWkJvMS2mofrLcPRDRW8tGPbjWHWTEZrHyhzzy-M&e=
>
> _______________________________________________
> BESS mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=-lXQr57gjaAzIOLwbMkK7R9-pM63sLMIM4FA1yr70zc&s=x2nsWkJvMS2mofrLcPRDRW8tGPbjWHWTEZrHyhzzy-M&e=

_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to