Re: [OPSAWG] Fwd: [mpls] New Liaison Statement, "LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) Requirements and Reference Model for optimized traceroute of joint Internet Pro

2024-02-16 Thread loa
r STD5/ICMP lies, but possibly someone that know could forward. And I think it would be a good idea to call on Scott to coordinate a response. /Loa > id="lineBreakAtBeginningOfSignature">Sent from my iPhoneBegin forwarded > message:From: > Greg Mirsky gregimir...@gmail.comD

Re: [OPSAWG] Fwd: [mpls] New Liaison Statement, "LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) Requirements and Reference Model for optimized traceroute of joint Internet Pro

2024-02-16 Thread loa
Greg, I'm not the expert on ICMP, but as far as I see you are correct. I very much would like an ICMP expert to look at this, but I don't know who to contact. Can anyone help me? /Loa > Hi Loa, > thank you for bringing to the discussion this liaison. I've looked through > the p

Re: [OPSAWG] [mpls] New I-D -> Guidelines for Charactering "OAM" -review

2024-01-19 Thread loa
ould we ask that the directorates put an instruction for the directorate reviewers to try to capture this? The rest of the document seems fine to me. /Loa > Hi Adrian, > thank you for your kind consideration of my notes. Please find my follow-up > notes below tagged by GIM>>. >

Re: [OPSAWG] Support in working group last calls

2013-09-10 Thread Loa Andersson
the document - after all you are co-author; but please note that the IETF consensus process does not work by voting. And maybe a pointer to the Tao of IETF. /Loa On 2013-09-10 13:39, Melinda Shore wrote: On 9/10/2013 3:29 AM, Loa Andersson wrote: Melinda, in general I agree with you - but I

Re: [OPSAWG] Please welcome our new chair!

2016-02-07 Thread Loa Andersson
a funny hat... do I read this right if I understand it like this - small things I give one or more cookies - big big things, I wear a funny hat when I give you the cookies right? /Loa PS Remember that we have runnig cookie code, ask ekr :) W Could you please send a private message to me :-

Re: [OPSAWG] [mpls] IOAM, iOAM, and oOAM abbreviations

2023-12-17 Thread Loa Andersson
is created it is easy to distinguish from existing once.It is also a heads up to wg chairs that there is documents where this should be considered. /LoaSent from my iPadOn 14 Dec 2023, at 23:10, Italo Busi wrote: Loa, Greg,   I am not sure we really need abbreviations for in-band and out

Re: [OPSAWG] [mpls] [IPv6] [Detnet] IOAM, iOAM, and oOAM abbreviations

2023-12-18 Thread Loa Andersson
shable from the existing. If we say that the IOAM for In-situ OAM exists, we should not consider iOAM or oOAM as abbreviations for whatever meaning. /Loa > > Stewart > ___ > mpls mailing list > m...@ietf.org > https://www.ietf.org/

Re: [OPSAWG] WG Adoption Call for draft-pignataro-opsawg-oam-whaaat-question-mark-03

2024-04-21 Thread Loa Andersson
this a more general guidance than just to refer to RFC 9197. I also think we should make "OAM" well-known, so we don't have to expand it when we use e.g. "In situ OAM" in a title. Other than that I support adopting the draft as a working group draft. /Loa -- Loa Ande