I am also wondering if hop-by-hop options been considered for this
application? Their interpretation in the network is unabiguous and
they also have the advantage that the work with any IP protocol or
encapsulation.

IPv6 hop-by-hop options has been considered. See
draft-brockners-inband-oam-transport-05. This has not yet been
broken out into a separate draft.

[UC]:


        “The
   Segment Routing Header (SRH) for IPv6 offers the ability to transport
   TLV structured data, similar to what NSH does (see
   [I-D.ietf-6man-segment-routing-header]).  In an domain where in-situ
   OAM is used, insertion of the in-situ OAM data is enabled at the
   required edge nodes (i.e. at the in-situ OAM encapsulating/
   decapsulating nodes) by means of configuration.”

I see SRH TLVs are being used for IOAM data. This is fine at the insertion 
point at the edge node as mentioned above,
but can you help explain how IAOM data gets added along the path towards the 
egress ? (yes, if you are in hop-by-hop EH, like SRH ).
Only way you can do this is by slapping 8200 encapsulation at every node? Is 
this correct ?

--
Uma C.
_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to