[OPSAWG] Erik Kline's No Objection on draft-ietf-opsawg-vpn-common-10: (with COMMENT)

[Erik Kline via Datatracker <[e-mail]>]

Erik Kline has entered the following ballot position for
draft-ietf-opsawg-vpn-common-10: 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/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


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



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

[S3, question]

* Should "ipv6/ttl" actually be "ipv6/hoplimit"?

  I'm not sure what might have been defined in other YANG documents
  elsewhere, but "ttl" is not the term normally associated with IPv6
  (8200s3).

* Should "ipv6/protocol" actually be "ipv6/nextheader"?

  The field in the header is actually "Next Header" (8200s3), but
  is the intention here to identify the next "logical higher-layer
  protocol", i.e. skipping over other headers that might be in
  between the IPv6 header and, say, a TCP header?

* How does "private or public cloud" count as "external connectivity"?

  Seems like the referenced 4364s11 is primarily concerned with
  Internet access.  I guess it seems odd to me to consider a VPN
  endpoint in a cloud instance especially different from any other
  (e.g., physical) endpoint...