WG,
we haven't receive any feedback.
I'll proceed with asking for the code points allocation.
-m
Le 01/06/2017 à 12:29, Martin Vigoureux a écrit :
Dear WG,
we have received an early allocation request (see details below) from
the authors of draft-ietf-bess-evpn-igmp-mld-proxy.
Please let us
Dear WG,
we have received an early allocation request (see details below) from
the authors of draft-ietf-bess-evpn-igmp-mld-proxy.
Please let us know if you are aware of any code-point conflict, or
if you have issues with the WG moving forward with this early allocation.
We envisage to procee
Hi Martin,
I have already made the request for the following code points in another
thread but here let me make it here as well:
>0x06 - Selective Multicast Ethernet Tag Route
>0x07 - IGMP Join Synch Route
>0x08 - IGMP Leave Synch Route
Needed for the following draft:
https://tools.ietf.org/ht
WG,
we haven't heard any opposition to proceeding with this early allocation.
We will thus move forward.
-m
Le 31/01/2017 à 11:55, Martin Vigoureux a écrit :
Dear WG,
we have received early allocation requests from the authors of
draft-ietf-bess-evpn-prefix-advertisement and
draft-ietf-bess-e
Dear WG,
we have received early allocation requests from the authors of
draft-ietf-bess-evpn-prefix-advertisement and
draft-ietf-bess-evpn-bum-procedure-updates: (see details below).
Please let us know if you are aware of any code-point conflict, or
if you have issues with the WG moving forwar