From nobody Fri Oct 28 03:44:02 2022 Return-Path: X-Original-To: ippm@ietfa.amsl.com Delivered-To: ippm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B78C14CF1C; Fri, 28 Oct 2022 03:44:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s1QR1QYGbvrZ; Fri, 28 Oct 2022 03:43:59 -0700 (PDT) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6AEEC14CF08; Fri, 28 Oct 2022 03:43:59 -0700 (PDT) Received: by mail-pg1-x532.google.com with SMTP id 20so4493682pgc.5; Fri, 28 Oct 2022 03:43:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=MwpEYMFQ4uyLil/kdmbBBlGAKqF4NdJgNxB0+fzDYSE=; b=oiFDt16E2X8O3agkhyHGdllNHyo1i0Alb5l7DwNH0NxQMIZQfWb9ebssi8Xi3DhSu0 z6R0wtm5ElQcYHeQPcHW5Rnr5S+GjwgBPXt7lUg9f7njY+Xr+BLEdLtOzVoJzE4IWXsE pBzN+L0K0UZ2auCFC9hjA4pAvwJFzePZTBIueNyA58K0nKzuiCodxUY5PzEMNgLiBCf/ lDwNJ9zdguVUVeJXDk8IWh99IrDi8nJL+apoyiwkOiK4sRrXy/snjeGids7zq4weOXg4 6oRUNX51dJ96ViUYTZEO6gdkUH03SdWCQE0c7XZDmO6L5fyr5CUkmXYlh10mOHXDAN2o p0Ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MwpEYMFQ4uyLil/kdmbBBlGAKqF4NdJgNxB0+fzDYSE=; b=SOkyYCilWwFqjou3jfHjST/AHACg/3oJbAg0OA29ZqJkp6SGlie+SmDQ5f44DSJV5U rzTaSoCj4LPzNyqYvErVViKk9iRGI/XJmW0aicscSqcnsCNhdiO3Mr+MEI1XIKuxUtqQ RUAIXdfMpOSp8P6uTF229VzfMuUU6RD+xkTIdK9sUQpfq5DoI/YO5t3mlGQSxYWCQIHj XrUI1mi/WnGvg+QNbgg6IKg8LQ7GEOHIom8wGTU6eGLi7zAUp6VEEpj+euZSuo0f9o4W e0jFLWHtLKnXSZpt5I4zffRrZMOcbal7pOJYV8hnl4/J1oxIrTeHw9tKUoOJXktN/vS0 b0Rw== X-Gm-Message-State: ACrzQf0GzXioJp1bB9xkWtZicvnQXVA2OMzjghq6+7NLFZxBnfRsQJ9L tG7S3LUgSyaiwClLo8tOpMcwyde2gfRhJZ5um/F0iVO/ X-Google-Smtp-Source: AMsMyM7N7JBGddPoJZBm/aa2Xl+rkpg/O2sNn6bnPR55VRX+uJbyRJ7SnqviC8vkjfWj6hxR8Oz2K8nioCgxRDfj8Lw= X-Received: by 2002:a63:4a41:0:b0:452:bab5:156a with SMTP id j1-20020a634a41000000b00452bab5156amr46272318pgl.486.1666953839044; Fri, 28 Oct 2022 03:43:59 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 28 Oct 2022 03:43:58 -0700 From: Alvaro Retana In-Reply-To: <202210281022397100489@zte.com.cn> References: <202210281022397100489@zte.com.cn> MIME-Version: 1.0 Date: Fri, 28 Oct 2022 03:43:58 -0700 Message-ID: To: xiao.min2@zte.com.cn Cc: ippm@ietf.org, marcus.ihlar@ericsson.com, ippm-chairs@ietf.org, iesg@ietf.org, draft-ietf-ippm-ioam-conf-state@ietf.org Content-Type: multipart/alternative; boundary="0000000000006eeef905ec15ef0d" Archived-At: Subject: Re: [ippm] Alvaro Retana's No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT) X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2022 10:44:00 -0000 --0000000000006eeef905ec15ef0d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi! Yes, those changes work for me. Thanks! Alvaro. On October 27, 2022 at 10:22:46 PM, xiao.min2@zte.com.cn ( xiao.min2@zte.com.cn) wrote: Hi Alvaro, Please check inline my responses. Best Regards, Xiao Min Original *From: *AlvaroRetana *To: *=E8=82=96=E6=95=8F10093570; *Cc: *ippm@ietf.org ;ippm-chairs@ietf.org < ippm-chairs@ietf.org>;marcus.ihlar@ericsson.com = ; iesg@ietf.org ;draft-ietf-ippm-ioam-conf-state@ietf.org < draft-ietf-ippm-ioam-conf-state@ietf.org>; *Date: *2022=E5=B9=B410=E6=9C=8826=E6=97=A5 21:40 *Subject: **Re: Alvaro Retana's No Objection on draft-ietf-ippm-ioam-conf-state-07: (with COMMENT)* On October 26, 2022 at 3:08:08 AM, xiao.min2@zte.com.cn wrote: Xiao Min: Hi! .... > [XM]>>> OK. Combining your comment and that one from Eric Vyncke on the > abstract, I propose to change the abstract (and the corresponding text in= the > introduction) as below. > > NEW > > This document describes a generic format for the echo request/reply > mechanisms used in IPv6, MPLS, Service Function Chain (SFC) and Bit > Index Explicit Replication (BIER) environments, which can be used > within the In situ Operations, Administration, and Maintenance (IOAM) > domain, allowing the IOAM encapsulating node to discover the enabled > IOAM capabilities of each IOAM transit and IOAM decapsulating node. This text still says that the "document describes a generic format...used in IPv6, MPLS, Service Function Chain (SFC) and Bit Index Explicit Replication (BIER) environments". I think this is still misleading because, as you point out below, the work to make this generic format work in IPV6, MPLS, etc. hasn't been done. In fact, all the drafts mentioned below are individual submissions. Suggestion> This document describes a generic format for use in echo request/reply mechanisms, which can be used within an In situ Operations, Administration, and Maintenance (IOAM) domain, allowing the IOAM encapsulating node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node. The generic format is intended to be used with a variety of data planes such as IPv6, MPLS, Service Function Chain (SFC) and Bit Index Explicit Replication (BIER). [XM-2]>>> The abstract suggested by you looks good. Will use it. For the introduction, does the changes proposed by John Scudder as below work for you? OLD: This document describes an extension to the echo request/reply mechanisms used in IPv6 (including SRv6), MPLS (including SR-MPLS), SFC and BIER environments, which can be used within the IOAM domain, allowing the IOAM encapsulating node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node. NEW: This document specifies formats and objects that can be used in the extension of echo request/reply mechanisms used in IPv6 (including SRv6), MPLS (including SR-MPLS), SFC and BIER environments, which can be used within the IOAM domain, allowing the IOAM encapsulating node to discover the enabled IOAM capabilities of each IOAM transit and IOAM decapsulating node. OLD: Note that specification details for these different echo request/ reply protocols are outside the scope of this document. It is expected that each such protocol extension would be specified by an RFC and jointly designed by the working group that develops or maintains the echo request/reply protocol and the IETF IP Performance Measurement (IPPM) Working Group. NEW: It is expected that the specification of the instantiation of each of these extensions will be done in the form of an RFC jointly designed by the working group that develops or maintains the echo request/reply protocol and the IETF IP Performance Measurement (IPPM) Working Group. Thanks! Alvaro. > [XM]>>> As far as I can tell, the cross-wg review and communication can > always be improved. As to this case, the idea is that (like RFC9197) the = main > document defines a generic format that can be reused by some follow-on > documents, avoiding repetitive definition of the same format in multiple > documents. For IPv6 (including SRv6), draft-xiao-6man-icmpv6-ioam-conf-st= ate > has been submitted as the follow-on document, which was presented twice (= at > IETF 112 and 114) in 6man and some good discussions happened at the meeti= ng > and on the mailing list. For MPLS (including SR-MPLS), > draft-xiao-mpls-lsp-ping-ioam-conf-state has been submitted as the follow= -on > document, which is on the agenda for mpls@IETF-115. For SFC and BIER, the > follow-on documents are in the plan (note that one co-author of the main > document is also the primary author of SFC echo request/reply and a co-au= thor > of BIER echo request/reply). You're right we authors could have done more > consultations with the corresponding WGs, and I promise to make the > improvement in the future. > --0000000000006eeef905ec15ef0d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
Hi!<= /div>

Yes, those changes = work for me.

Thanks= !

=
Alvaro.=C2=A0

On October 27, 2022 at 10:22:46 PM, xiao.min2@zte.com.cn (xiao.min2@zte.com.cn) wrote:

Hi Alvaro,


Please check inline my responses.


Best Regards,

Xiao Min

Original
From:=C2= =A0AlvaroRetana <aretana.ietf@gmail.com>
<= strong>To:=C2=A0=E8=82=96=E6=95=8F10093570;
Cc:=C2=A0ippm@ietf.org <ippm@i= etf.org>;ippm-chairs@ietf.org <ippm-chairs@ietf.org>;marcus.ihlar@ericsson.com <marcus.ihlar@ericsson.com>;iesg@ietf.org <iesg@ietf.org<= /a>>;draft-ietf-ippm-ioam= -conf-state@ietf.org <draft-ietf-ippm-ioam-conf-state@ietf.org>;
Date:=C2=A02022=E5=B9=B410=E6=9C=88= 26=E6=97=A5 21:40
Subject:=C2=A0Re: Alvaro Retana's No Objection on draft-iet= f-ippm-ioam-conf-state-07: (with COMMENT)
On=C2=A0October=C2=A026,=C2=A02022=C2=A0at=C2= =A03:08:08=C2=A0AM,=C2=A0xiao.min2@= zte.com.cn=C2=A0wrote:


Xiao=C2=A0Min:

Hi!

=
....
>=C2=A0[XM]>>>=C2=A0OK.=C2=A0Combining=C2=A0your= =C2=A0comment=C2=A0and=C2=A0that=C2=A0one=C2=A0from=C2=A0Eric=C2=A0Vyncke= =C2=A0on=C2=A0the
>=C2=A0abstract,=C2=A0I=C2=A0propose=C2=A0to=C2=A0c= hange=C2=A0the=C2=A0abstract=C2=A0(and=C2=A0the=C2=A0corresponding=C2=A0tex= t=C2=A0in=C2=A0the
>=C2=A0introduction)=C2=A0as=C2=A0below.
> <= br>>=C2=A0NEW
>
>=C2=A0=C2=A0=C2=A0=C2=A0This=C2=A0document= =C2=A0describes=C2=A0a=C2=A0generic=C2=A0format=C2=A0for=C2=A0the=C2=A0echo= =C2=A0request/reply
>=C2=A0=C2=A0=C2=A0=C2=A0mechanisms=C2=A0used=C2= =A0in=C2=A0IPv6,=C2=A0MPLS,=C2=A0Service=C2=A0Function=C2=A0Chain=C2=A0(SFC= )=C2=A0and=C2=A0Bit
>=C2=A0=C2=A0=C2=A0=C2=A0Index=C2=A0Explicit=C2= =A0Replication=C2=A0(BIER)=C2=A0environments,=C2=A0which=C2=A0can=C2=A0be= =C2=A0used
>=C2=A0=C2=A0=C2=A0=C2=A0within=C2=A0the=C2=A0In=C2=A0situ= =C2=A0Operations,=C2=A0Administration,=C2=A0and=C2=A0Maintenance=C2=A0(IOAM= )
>=C2=A0=C2=A0=C2=A0=C2=A0domain,=C2=A0allowing=C2=A0the=C2=A0IOAM= =C2=A0encapsulating=C2=A0node=C2=A0to=C2=A0discover=C2=A0the=C2=A0enabled>=C2=A0=C2=A0=C2=A0=C2=A0IOAM=C2=A0capabilities=C2=A0of=C2=A0each=C2= =A0IOAM=C2=A0transit=C2=A0and=C2=A0IOAM=C2=A0decapsulating=C2=A0node.
<= br>This=C2=A0text=C2=A0still=C2=A0says=C2=A0that=C2=A0the=C2=A0"docume= nt=C2=A0describes=C2=A0a=C2=A0generic
format...used=C2=A0in=C2=A0IPv6,= =C2=A0MPLS,=C2=A0Service=C2=A0Function=C2=A0Chain=C2=A0(SFC)=C2=A0and=C2=A0= Bit
Index=C2=A0Explicit=C2=A0Replication=C2=A0(BIER)=C2=A0environments&q= uot;.

I=C2=A0think=C2=A0this=C2=A0is=C2=A0still=C2=A0misleading=C2= =A0because,=C2=A0as=C2=A0you=C2=A0point=C2=A0out=C2=A0below,=C2=A0the
wo= rk=C2=A0to=C2=A0make=C2=A0this=C2=A0generic=C2=A0format=C2=A0work=C2=A0in= =C2=A0IPV6,=C2=A0MPLS,=C2=A0etc.=C2=A0hasn't=C2=A0been
done.=C2=A0= =C2=A0In=C2=A0fact,=C2=A0all=C2=A0the=C2=A0drafts=C2=A0mentioned=C2=A0below= =C2=A0are=C2=A0individual
submissions.

Suggestion>

= =C2=A0=C2=A0=C2=A0This=C2=A0document=C2=A0describes=C2=A0a=C2=A0generic=C2= =A0format=C2=A0for=C2=A0use=C2=A0in=C2=A0echo
request/reply=C2=A0mechani= sms,=C2=A0which=C2=A0can=C2=A0be=C2=A0used=C2=A0within=C2=A0an=C2=A0In=C2= =A0situ
Operations,=C2=A0Administration,=C2=A0and=C2=A0Maintenance=C2=A0= (IOAM)=C2=A0domain,=C2=A0allowing
the=C2=A0IOAM=C2=A0encapsulating=C2=A0= node=C2=A0to=C2=A0discover=C2=A0the=C2=A0enabled=C2=A0IOAM=C2=A0capabilitie= s
of=C2=A0each=C2=A0IOAM=C2=A0transit=C2=A0and=C2=A0IOAM=C2=A0decapsulat= ing=C2=A0node.=C2=A0=C2=A0The=C2=A0generic=C2=A0format
is=C2=A0intended= =C2=A0to=C2=A0be=C2=A0used=C2=A0with=C2=A0a=C2=A0variety=C2=A0of=C2=A0data= =C2=A0planes=C2=A0such=C2=A0as=C2=A0IPv6,
MPLS,=C2=A0Service=C2=A0Functi= on=C2=A0Chain=C2=A0(SFC)
=C2=A0=C2=A0=C2=A0and=C2=A0Bit=C2=A0Index=C2=A0= Explicit=C2=A0Replication=C2=A0(BIER).

[XM-2]>>> The abstra= ct suggested by you looks good. Will use it. For the introduction, does the changes proposed by John=C2=A0Scudder=C2=A0as below work = for you?

OLD:
=C2=A0=C2=A0=C2=A0This=C2=A0document=C2=A0descri= bes=C2=A0an=C2=A0extension=C2=A0to=C2=A0the=C2=A0echo=C2=A0request/reply
=C2=A0=C2= =A0=C2=A0mechanisms=C2=A0used=C2=A0in=C2=A0IPv6=C2=A0(including=C2=A0SRv6),= =C2=A0MPLS=C2=A0(including=C2=A0SR-MPLS),
=C2=A0=C2=A0=C2=A0SFC=C2=A0and=C2=A0BIER= =C2=A0environments,=C2=A0which=C2=A0can=C2=A0be=C2=A0used=C2=A0within=C2=A0= the=C2=A0IOAM=C2=A0domain,
=C2=A0=C2=A0=C2=A0allowing=C2=A0the=C2=A0IOAM=C2=A0encaps= ulating=C2=A0node=C2=A0to=C2=A0discover=C2=A0the=C2=A0enabled=C2=A0IOAM
=C2=A0=C2=A0= =C2=A0capabilities=C2=A0of=C2=A0each=C2=A0IOAM=C2=A0transit=C2=A0and=C2=A0I= OAM=C2=A0decapsulating=C2=A0node.

NEW:
=C2=A0=C2=A0=C2=A0This=C2=A0document= =C2=A0specifies=C2=A0formats=C2=A0and=C2=A0objects=C2=A0that=C2=A0can=C2=A0= be=C2=A0used=C2=A0in=C2=A0the
=C2=A0=C2=A0=C2=A0extension=C2=A0of=C2=A0echo=C2=A0req= uest/reply=C2=A0mechanisms=C2=A0used=C2=A0in=C2=A0IPv6=C2=A0(including
=C2=A0=C2=A0= =C2=A0SRv6),=C2=A0MPLS=C2=A0(including=C2=A0SR-MPLS),=C2=A0SFC=C2=A0and=C2= =A0BIER=C2=A0environments,=C2=A0which=C2=A0can
=C2=A0=C2=A0=C2=A0be=C2=A0used=C2=A0w= ithin=C2=A0the=C2=A0IOAM=C2=A0domain,=C2=A0allowing=C2=A0the=C2=A0IOAM=C2= =A0encapsulating=C2=A0node
=C2=A0=C2=A0=C2=A0to=C2=A0discover=C2=A0the=C2=A0enabled= =C2=A0IOAM=C2=A0capabilities=C2=A0of=C2=A0each=C2=A0IOAM=C2=A0transit=C2=A0= and

=C2=A0=C2=A0= =C2=A0IOAM=C2=A0decapsulating=C2=A0node.


O= LD:
=C2= =A0=C2=A0=C2=A0Note=C2=A0that=C2=A0specification=C2=A0details=C2=A0for=C2= =A0these=C2=A0different=C2=A0echo=C2=A0request/
=C2=A0=C2=A0=C2=A0reply=C2=A0protoco= ls=C2=A0are=C2=A0outside=C2=A0the=C2=A0scope=C2=A0of=C2=A0this=C2=A0documen= t.=C2=A0=C2=A0It=C2=A0is
=C2=A0=C2=A0=C2=A0expected=C2=A0that=C2=A0each=C2=A0such=C2= =A0protocol=C2=A0extension=C2=A0would=C2=A0be=C2=A0specified=C2=A0by=C2=A0a= n
=C2=A0= =C2=A0=C2=A0RFC=C2=A0and=C2=A0jointly=C2=A0designed=C2=A0by=C2=A0the=C2=A0w= orking=C2=A0group=C2=A0that=C2=A0develops=C2=A0or
<= span style=3D"font-family:Arial,Helvetica,"Microsoft Yahei",sans-= serif;background-color:rgb(255,255,255)">=C2=A0=C2=A0=C2=A0maintains=C2=A0t= he=C2=A0echo=C2=A0request/reply=C2=A0protocol=C2=A0and=C2=A0the=C2=A0IETF= =C2=A0IP=C2=A0Performance
=C2=A0=C2=A0=C2=A0Measurement=C2=A0(IPPM)=C2=A0Working=C2= =A0Group.

NEW:
=C2=A0=C2=A0=C2=A0It=C2=A0is=C2=A0expected=C2=A0that=C2=A0th= e=C2=A0specification=C2=A0of=C2=A0the=C2=A0instantiation=C2=A0of=C2=A0each= =C2=A0of
= =C2=A0=C2=A0=C2=A0these=C2=A0extensions=C2=A0will=C2=A0be=C2=A0done=C2=A0in= =C2=A0the=C2=A0form=C2=A0of=C2=A0an=C2=A0RFC=C2=A0jointly=C2=A0designed
=C2=A0=C2=A0= =C2=A0by=C2=A0the=C2=A0working=C2=A0group=C2=A0that=C2=A0develops=C2=A0or= =C2=A0maintains=C2=A0the=C2=A0echo
=C2=A0=C2=A0=C2=A0request/reply=C2=A0protocol=C2= =A0and=C2=A0the=C2=A0IETF=C2=A0IP=C2=A0Performance=C2=A0Measurement=C2=A0(I= PPM)

=C2=A0=C2=A0=C2=A0Wo= rking=C2=A0Group.


Thanks!

Alvaro.



>=C2=A0[XM]>>>= =C2=A0As=C2=A0far=C2=A0as=C2=A0I=C2=A0can=C2=A0tell,=C2=A0the=C2=A0cross-wg= =C2=A0review=C2=A0and=C2=A0communication=C2=A0can
>=C2=A0always=C2=A0= be=C2=A0improved.=C2=A0As=C2=A0to=C2=A0this=C2=A0case,=C2=A0the=C2=A0idea= =C2=A0is=C2=A0that=C2=A0(like=C2=A0RFC9197)=C2=A0the=C2=A0main
>=C2= =A0document=C2=A0defines=C2=A0a=C2=A0generic=C2=A0format=C2=A0that=C2=A0can= =C2=A0be=C2=A0reused=C2=A0by=C2=A0some=C2=A0follow-on
>=C2=A0document= s,=C2=A0avoiding=C2=A0repetitive=C2=A0definition=C2=A0of=C2=A0the=C2=A0same= =C2=A0format=C2=A0in=C2=A0multiple
>=C2=A0documents.=C2=A0For=C2=A0IP= v6=C2=A0(including=C2=A0SRv6),=C2=A0draft-xiao-6man-icmpv6-ioam-conf-state<= br>>=C2=A0has=C2=A0been=C2=A0submitted=C2=A0as=C2=A0the=C2=A0follow-on= =C2=A0document,=C2=A0which=C2=A0was=C2=A0presented=C2=A0twice=C2=A0(at
&= gt;=C2=A0IETF=C2=A0112=C2=A0and=C2=A0114)=C2=A0in=C2=A06man=C2=A0and=C2=A0s= ome=C2=A0good=C2=A0discussions=C2=A0happened=C2=A0at=C2=A0the=C2=A0meeting<= br>>=C2=A0and=C2=A0on=C2=A0the=C2=A0mailing=C2=A0list.=C2=A0For=C2=A0MPL= S=C2=A0(including=C2=A0SR-MPLS),
>=C2=A0draft-xiao-mpls-lsp-ping-ioam= -conf-state=C2=A0has=C2=A0been=C2=A0submitted=C2=A0as=C2=A0the=C2=A0follow-= on
>=C2=A0document,=C2=A0which=C2=A0is=C2=A0on=C2=A0the=C2=A0agenda= =C2=A0for=C2=A0mpls@IETF-115.=C2=A0For=C2=A0SFC=C2=A0and=C2=A0BIER,=C2=A0th= e
>=C2=A0follow-on=C2=A0documents=C2=A0are=C2=A0in=C2=A0the=C2=A0plan= =C2=A0(note=C2=A0that=C2=A0one=C2=A0co-author=C2=A0of=C2=A0the=C2=A0main>=C2=A0document=C2=A0is=C2=A0also=C2=A0the=C2=A0primary=C2=A0author=C2= =A0of=C2=A0SFC=C2=A0echo=C2=A0request/reply=C2=A0and=C2=A0a=C2=A0co-author<= br>>=C2=A0of=C2=A0BIER=C2=A0echo=C2=A0request/reply).=C2=A0You're=C2= =A0right=C2=A0we=C2=A0authors=C2=A0could=C2=A0have=C2=A0done=C2=A0more
&= gt;=C2=A0consultations=C2=A0with=C2=A0the=C2=A0corresponding=C2=A0WGs,=C2= =A0and=C2=A0I=C2=A0promise=C2=A0to=C2=A0make=C2=A0the
>=C2=A0improvem= ent=C2=A0in=C2=A0the=C2=A0future.
>


--0000000000006eeef905ec15ef0d--