[OPSAWG] Tsvart last call review of draft-ietf-opsawg-vpn-common-06
Reviewer: Wesley Eddy Review result: Almost Ready This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-...@ietf.org if you reply to or forward this review. (1) I noticed in the "qos-classification-policy" there is "l4" support either TCP or UDP. It isn't clear if other transport protocols are purposefully not included. Should this also support SCTP and/or DCCP, or other transport protocol numbers in general? Are the QUIC aspects that might be matched contained within the UDP fields supported? (2) Is the allowable MTU another aspect of VPN services that should be able to be expressed? (3) ICMP isn't mentioned as an identity type, and I wondered if this should be. ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common
Hi OPSAWG, no, I am not aware of any IPR that applies to this draft Italo > -Original Message- > From: Joe Clarke (jclarke) [mailto:jcla...@cisco.com] > Sent: lunedì 22 marzo 2021 14:33 > To: opsawg@ietf.org > Subject: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common > > Authors, contributors, and WG members, as we are in WGLC for this > document, we want to solicit knowledge of any IPR that may pertain to the > draft-ietf-opsawg-vpn-common work. > > Please state either, "no, I am not aware of any IPR that applies to this > draft" or, > "yes, I am aware of IPR that applies this draft". > > If there is IPR, it must be disclosed in compliance with IETF IPR rules > (i.e., RFCs > 3669, 5378, and 8179). Please indicate if this has been done. > > If you have any additional details, please share those as well. > > If you are an author or contributor, you must reply to indicate IPR status. > > Joe > > ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
