Re: [sfc] New version of draft-ietf-bess-nsh-bgp-control-plane

[Adrian Farrel <[e-mail]>]

Hi Med,

In line...

>   o  The SFIR is advertised by the node hosting the service function
>                                    ^^^^^^^^^^^^ 
>      instance (i.e., the SFF).
>
>
> I guess what is meant here is that the SFF is servicing this SFI, not that
the
> SFI is embedded in the same node as the SFF. No?

Yeah. That can be clarified.
I'll hold it for completion of the IESG discussions.

> Also, you may consider updating this list: 
>
>     40    | Network Address Translator    | [This.I-D] | Date-to-be-set
>     41    | NAT44                         | [This.I-D] | Date-to-be-set
>     42    | NAT64                         | [This.I-D] | Date-to-be-set
>     43    | NPTv6                         | [This.I-D] | Date-to-be-set
>
> With these types:
>
>   o  Basic NAT44            ==> Section 2.1 of RFC 3022
>   o  NAPT44                 ==> Section 2.2 of RFC 3022
>   o  Destination NAT        ==> RFC 8512
>   o  NAT64                  ==> RFC 6146
>   o  SIIT                   ==> RFC 7915
>   o  EAM                    ==> RFC 7757
>   o  NPTv6                  ==> RFC 6296
>   o  DS-Lite                ==> RFC 6333

Considered, but not done :-Z

Our list was derived from RFC 7498 and RFC 8300.

It's quite likely that the list you give may need to be added, but at the
moment we don't have much push for more than we've listed. I think other
additional SFTs can be added at pretty much any time in the future.

Best,
Adrian