[mpls] Alvaro Retana's No Objection on draft-ietf-mpls-sfc-05: (with COMMENT)

[Alvaro Retana <[e-mail]>]

Alvaro Retana has entered the following ballot position for
draft-ietf-mpls-sfc-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mpls-sfc/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for a very clear document!

I think that the only NSH functionality not included in this document is the O
bit (OAM packet).  I know that, even in rfc8300, the operation (beyond setting
the bit) is not defined...and that work is still in progress in the SFC WG. 
However, given that this document describes a "logical representation of the
NSH", I think it is necessary to point out why the coverage is not complete. 
In looking through the mail archive, I like the thoughts posted by one of the
authors [1] and would like to see something like that reflected in the document.

[1] https://mailarchive.ietf.org/arch/msg/mpls/b9Duw-9ShdCrIRyis3TOJWw-_pw

nits:

s/(as described in Section 4.1/(as described in Section 4.1)

s/(see [I-D.ietf-bess-nsh-bgp-control-plane]/(see
[I-D.ietf-bess-nsh-bgp-control-plane])

s/TC:  The TC bits have no meaning./TC:  The TC bits have no meaning in this
case.

s/to determine to which SFF or instance of an SF (an SFI) to deliver the
packet./to determine which SFF or instance of an SF (an SFI) to deliver the
packet to.