Some initial questions/comments:
1. security label is defined as opaque data in the draft, but then how would
narrowing work in an inter-op way with opaque data? Or should we define the
format for some common use cases (like security enforcement, QoS ...) , and
adding a sub-type in TS_SECLABEL
2
On Tue, 6 Mar 2018, Hu, Jun (Nokia - US/Mountain View) wrote:
Some initial questions/comments:
1. security label is defined as opaque data in the draft, but then how would
narrowing work in an inter-op way with opaque data? Or should we define the
format for some common use cases (like securit
> -Original Message-
> From: Paul Wouters [mailto:p...@nohats.ca]
> Sent: Tuesday, March 06, 2018 5:53 PM
> To: Hu, Jun (Nokia - US/Mountain View)
> Cc: ipsec@ietf.org WG ; Sahana Prasad
>
> Subject: RE: [IPsec] Fwd: New Version Notification for draft-sprasad-ipsecme-
> labeled-ipsec-00.