
From nobody Wed Feb  1 07:51:13 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BF0129496; Wed,  1 Feb 2017 07:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEJjS67jh5vu; Wed,  1 Feb 2017 07:51:05 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD2A5129407; Wed,  1 Feb 2017 07:51:04 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id 73so293203012otj.0; Wed, 01 Feb 2017 07:51:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=b3G7OGOneZnM3JvRhU4ENwTcuf/euk03EKHPNxlHN7U=; b=p6Oti7Kbsmc+bh4VUgysRNPIcq5k2LqaqiHkCqf7CJYw6whtX8S1t/z2SlB1y/sq49 8UB4xDuHU/VQDLdIMHBKlyZNu46KXnEkrw9UKMk3yqloBuwGWdYlKDb8WkOIcGmKzqcP t8rcS1QIERDQtw/KNri6XGQJ8MCI4jxiAErFXNE8WCilQT1PzgTcY08d/6VVZcaMClMC HhDJTcBmsQo2DGUaqd6V46Qtr7HyWxnqo7NyOzzhAoSf+uAciVD6WW+DZxRuUW+MopeK FWTdlEN4FAICjl9B1G2/UbB5STiOIgjvq79Q6YaEDYpYFymF7Z41iiguYu5NFa93EnWw yhwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=b3G7OGOneZnM3JvRhU4ENwTcuf/euk03EKHPNxlHN7U=; b=R3uDflmKRmcn0cArYtnx56uu8jp7nzgYATfvX3bnF3gwbFk29diYPkfJsMFPg0MSlq ND/3QdOcMXdrIAGwq/ToteP2lmz4zMp6U03JrHrChmdwd6MTRCk4pDCE2XnsY2KvdrTF YHb4MyimI/Iqy+cEFsTzy98yrRt1gHCdSLP88pJgY9eGkd0q4BA6uVYbYzJFskD9F1hI +ChnYm4gj6+NyPSQfnndJvGaZiyDP92dN96xNGlYz1bAgBO/9x9a+tBzqEvXGuUtCPiA Z3hyUY/xFMxk39C+PNu2pBVip2X00m3bbtQILUZgyzZABFYjR+A8IhjZmHc3tlgDwltN YFYQ==
X-Gm-Message-State: AMke39n9+0zkIMLt2GPq5KJAJQqzwOMPpeJOkQcEsGYPHQUlqx9V1jBinSqoR5W0TbCD61zkjv+xKR/FdB19Ew==
X-Received: by 10.157.52.253 with SMTP id t58mr1784906otd.161.1485964264194; Wed, 01 Feb 2017 07:51:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Wed, 1 Feb 2017 07:50:23 -0800 (PST)
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com>
From: tianxiang li <peter416733@gmail.com>
Date: Wed, 1 Feb 2017 23:50:23 +0800
Message-ID: <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
To: Roni Even <roni.even@huawei.com>
Content-Type: multipart/alternative; boundary=001a1140a4621dc8a505477a049b
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/c69WdzvcfFrN4AnU8AT0hoIAenk>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 15:51:07 -0000

--001a1140a4621dc8a505477a049b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Roni,

Thank you for the response, please see inline.

Cheers,
Tianxiang

2017-02-01 15:02 GMT+08:00 Roni Even <roni.even@huawei.com>:

> Hi,
>
> See inline
>
> Roni
>
>
>
> *From:* Gen-art [mailto:gen-art-bounces@ietf.org] *On Behalf Of *tianxian=
g
> li
> *Sent:* =D7=99=D7=95=D7=9D =D7=92 31 =D7=99=D7=A0=D7=95=D7=90=D7=A8 2017 =
17:59
> *To:* Roni Even
> *Cc:* dhcwg; gen-art@ietf.org; ietf@ietf.org;
> draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
> *Subject:* Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-l
> ength-hint-issue-05
>
>
>
> Dear Roni,
>
>
>
> Thank you for providing a thorough review of this document.
>
>
>
> I have a few questions regarding the comments, please see inline.
>
>
>
> Best regards,
>
> Tianxiang
>
>
>
> 2017-01-29 17:02 GMT+08:00 Roni Even <roni.even@mail01.huawei.com>:
>
> Reviewer: Roni Even
> Review result: Almost Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
> Reviewer: Roni Even
> Review Date: 2017-01-29
> IETF LC End Date: 2017-02-09
> IESG Telechat date: 2017-02-16
>
> Summary: This draft is almost ready for publication as a standard
> track RFC.
>
>
> Major issues:
>
> Minor issues:
>
> 1.      I think that this document updates RFC3633 and it should be
> mentioned in the title and abstract
>
>
>
> [Tianxiang] This document does not change any of the text in RFC 3633, bu=
t
> specifies the client and server behavior when using the "prefix-length
> hint", which was not explained in RFC3633. Would it be suitable to state
> "this document updates RFC3633"?
>
> *[Roni Even] Yes, this is what I meant and it needs to be written in  the
> title and abstract, it will also point people looking at RFC3633 to this
> document*
>
>
>
[Tianxiang2] Okay, we could add a sentence in the end of the abstract
saying "This document updates RFC3633".

For the title, we followed a similar name with RFC7550 which updated
RFC3315 and RFC3633. It was titled "Issues and Recommendations with
Multiple Stateful DHCPv6 Options". Do you have some recommendations on how
to change the document title?

> 2.      In section 3.1 reference RFC3315 for solicit message and 3.3 for
> advertise messge
>
>
>
> [Tianxiang] Okay, we'll add reference to RFC3315 in section 3.1 and 3.3
> when mentioning Solicit and Advertise messgae.
>
> *[Roni Even] OK*
>
>
>
> 3.      In section 3.1 solution last paragraph is the order of the two
> IAPREFIX options important?
>
>
>
> [Tianxiang] There is no strict requirement for the order of the two
> options. Would you prefer if we added a sentence to specify this?
>
> *[Roni Even] I assumed this was the case but it will better to clarify*
>
>
>
> 4.      In section 3.2 solution why are you suing SHOULD and not MUST in
> all recommendations?
>
>
>
> [Tianxiang] In this document, we used "MUST" for some of the client
> behaviors, as they are mandatory to avoid client failure and necessary if
> the client wanted to express its prefix-length requirement.
>
>
>
> For server behavior, we used "SHOULD" because this document specifies the
> desired server behavior if the server wants to consider the prefix-length
> hint, but the server could have its own behavioral policy (e.g. neglect t=
he
> prefix-length hint).
>
> *[Roni Even] This make sense, but it will be good to clarify why it is a
> SHOULD using your explanation*
>
>
>
> 5.      In section 3.2 solution, what should the server do if cannot
> provide any of the requests
>
>
>
> [Tianxiang] If the server could not provide the requested prefix or
> prefix-length, it should provide a prefix closest to the prefix-length
> hint, as stated in the last sentence of section 3.2.
>
>
>
> Are you referring to what the sever should do of it simply could not
> provide ANY prefixes to the client? In that case, we could add a sentence
> at the end of the section 3.2:
>
>
>
> "If the server will not assign any prefixes to any IA_PDs in a subsequent
> Request from the client, the server MUST send an Advertise message to the
> client as described in section 11.2 of RFC 3633."
>
> *[Roni Even] This sentence is what I was looking for.*
>
>
>
> 6.      In section 3.2 solution last paragraph =E2=80=9CSHOULD try to pro=
vide=E2=80=9D and
> in the first paragraph =E2=80=9CSHOULD provide=E2=80=9D should be the sam=
e in both.
>
>
>
> [Tianxiang] Thanks for pointing that out, we'll change it to "SHOULD
> provide".
>
>
>
> *[Roni Even] OK*
>
>
>
> 7.      In section 3.4 =E2=80=9CIf the client decided to use  the prefix =
provided
> by the server despite being longer than the  prefix-length hint=E2=80=9D =
yet I
> did not see in section 3.2 that the server can provide a longer
> prefix.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2:
>
>
>
> "If the requested prefix is not available in the server's prefix pool, an=
d
> the client also included a prefix-length hint in the same IA_PD option,
> then the server SHOULD try to provide a prefix matching the prefix-length
> value, or the prefix with the shortest length possible which is closest t=
o
> the prefix-length hint value."
>
> *[Roni Even] I understood from 3.2 that it should provide a shorter lengt=
h
> prefix  closer to the request maybe =E2=80=9C*or the prefix with the clos=
est
> possible length to the prefix-length hint value=E2=80=9D
>
>
>
[Tianxiang2] The original sentence was a bit confusing, perhaps we could
change it like this:

OLD: "If the requested prefix is not available in the server's prefix pool,
and the client also included a prefix-length hint in the same IA_PD option,
then the server SHOULD try to provide a prefix matching the prefix-length
value, or the prefix with the shortest length possible which is closest to
the prefix-length hint value."

NEW:"If the requested prefix is not available in the server's prefix pool,
and the client also included a prefix-length hint in the same IA_PD option,
then the server SHOULD provide a prefix matching the prefix-length hint, or
a prefix which is length is shorter and as close as possible to the
prefix-length hint. If the server could not provide a prefix which length
is shorter or equal to the prefix-length hint, the server SHOULD provide
the prefix which length is longer and as close as possible to the
prefix-length hint."

8.      In section 3.5 solution the document use =E2=80=9Cas close as possi=
ble=E2=80=9D and
> section 3.2 only talk about smaller.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2.
>
> *[Roni Even] See above to point 7*
>
>
>
> 9.     In section 3.5 solution why offer options 3 and 4. The draft
> says that option 3 will break client connections and 4 talks about =E2=80=
=9Ca
> short non-zero valid-lifetime=E2=80=9D which may cause the  client to los=
e
> connection if "too short for the client" since =E2=80=9Cshort=E2=80=9D is=
 not an exact
> value
>
>
>
> [Tianxiang] The idea was to list all the options, and discuss their
> consequences. And the server could decide which option to use depending o=
n
> its policy.
>
>
>
> Option 3 avoids the complexity of handling multiple delegated prefixes,
> despite of breaking up all connections. Option 4 allows to server to
> configure a valid-lifetime for the old prefix depending on actual
> requirements, rather than let the old prefix expire on its own.
>
> *[Roni Even] OK, still option 4 may have similar result to 3 since =E2=80=
=9Ca
> short non-zero=E2=80=9D may be too short. Why not add a recommended value=
?*
>
>
>
[Tianxiang2] Agree, as this may vary for different services, we could
change the text to say "a specific valid-lifetime depending on the actual
requirement".


>
>
>
> Nits/editorial comments:
>
>
>
>

--001a1140a4621dc8a505477a049b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Roni,<div><br></div><div>Thank you for the response, pl=
ease see inline.</div><div><br></div><div>Cheers,</div><div>Tianxiang</div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-02-01 15:02 =
GMT+08:00 Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:roni.even@huawe=
i.com" target=3D"_blank">roni.even@huawei.com</a>&gt;</span>:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmail-m_-49=
00649193753751102WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">See inline<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">Roni<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border-top:none;border-right:none;border-bottom:none;border-l=
eft:1.5pt solid blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10pt;font-family:tahoma,=
sans-serif">From:</span></b><span style=3D"font-size:10pt;font-family:tahom=
a,sans-serif"> Gen-art [mailto:<a href=3D"mailto:gen-art-bounces@ietf.org" =
target=3D"_blank">gen-art-bounces@ietf.o<wbr>rg</a>]
<b>On Behalf Of </b>tianxiang li<br>
<b>Sent:</b> <span lang=3D"HE" dir=3D"RTL">=D7=99=D7=95=D7=9D=C2=A0=D7=92 3=
1 =D7=99=D7=A0=D7=95=D7=90=D7=A8 2017 17:59</span><br>
<b>To:</b> Roni Even<br>
<b>Cc:</b> dhcwg; <a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen=
-art@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@=
ietf.org</a>; <a href=3D"mailto:draft-ietf-dhc-dhcpv6-prefix-length-hint-is=
sue.all@ietf.org" target=3D"_blank">draft-ietf-dhc-dhcpv6-prefix-l<wbr>engt=
h-hint-issue.all@ietf.org</a><br>
<b>Subject:</b> Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-l<wbr>=
ength-hint-issue-05<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div><div><div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246g=
mail-h5">
<p class=3D"MsoNormal">Dear Roni,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thank you for providing a thorough review of this do=
cument.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have a few questions regarding the comments, pleas=
e see inline.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Tianxiang<u></u><u></u></p>
</div>
</div></div><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div><div><div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246g=
mail-h5">
<p class=3D"MsoNormal">2017-01-29 17:02 GMT+08:00 Roni Even &lt;<a href=3D"=
mailto:roni.even@mail01.huawei.com" target=3D"_blank">roni.even@mail01.huaw=
ei.com</a>&gt;:<u></u><u></u></p>
<p class=3D"MsoNormal">Reviewer: Roni Even<br>
Review result: Almost Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_bl=
ank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
<br>
Document: draft-ietf-dhc-dhcpv6-prefix-l<wbr>ength-hint-issue-05<br>
Reviewer: Roni Even<br>
Review Date: 2017-01-29<br>
IETF LC End Date: 2017-02-09<br>
IESG Telechat date: 2017-02-16<br>
<br>
Summary: This draft is almost ready for publication as a standard<br>
track RFC.<br>
<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1.=C2=A0 =C2=A0 =C2=A0 I think that this document updates RFC3633 and it sh=
ould be<br>
mentioned in the title and abstract<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div><div><div><div class=3D"m_-6060726979536003119gmail-m_-65248021=
12207049246gmail-h5">
<p class=3D"MsoNormal">[Tianxiang] This document does not change any of the=
 text in RFC 3633, but specifies the client and server behavior when using =
the &quot;prefix-length hint&quot;, which was not explained in RFC3633. Wou=
ld it be suitable to state &quot;this document updates
 RFC3633&quot;?<u></u><u></u></p>
</div></div><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font=
-family:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] Yes, this is w=
hat I meant and it needs to be written in=C2=A0 the title and abstract, it =
will also point people looking at RFC3633 to this document</span></i></b><s=
pan style=3D"font-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,=
125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0</p></div></span></div></div></div></div></div=
></div></blockquote><div>[Tianxiang2] Okay, we could add a sentence in the =
end of the abstract saying &quot;This document updates RFC3633&quot;.</div>=
<div><br></div><div>For the title, we followed a similar name with RFC7550 =
which updated RFC3315 and RFC3633. It was titled &quot;Issues and Recommend=
ations with Multiple Stateful DHCPv6 Options&quot;. Do you have some recomm=
endations on how to change the document title?</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-60607269795=
36003119gmail-m_-6524802112207049246gmail-m_-4900649193753751102WordSection=
1"><div style=3D"border-top:none;border-right:none;border-bottom:none;borde=
r-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt"><div><div><div><span class=
=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmail-"><div><p class=
=3D"MsoNormal"><u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">2.=C2=A0 =C2=A0 =C2=A0 In section 3.1 reference RFC3=
315 for solicit message and 3.3 for<br>
advertise messge=C2=A0<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] Okay, we&#39;ll add reference to RFC3315=
 in section 3.1 and 3.3 when mentioning Solicit and Advertise messgae.<u></=
u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK</span></i></b><s=
pan style=3D"font-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,=
125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">3.=C2=A0 =C2=A0 =C2=A0 In section 3.1 solution last =
paragraph is the order of the two<br>
IAPREFIX options important?<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] There is no strict requirement for the o=
rder of the two options. Would you prefer if we added a sentence to specify=
 this?<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] I assumed this was =
the case but it will better to clarify</span></i></b><span style=3D"font-si=
ze:11pt;font-family:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u>=
</span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">4.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution why a=
re you suing SHOULD and not MUST in<br>
all recommendations?<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] In this document, we used &quot;MUST&quo=
t; for some of the client behaviors, as they are mandatory to avoid client =
failure and necessary if the client wanted to express its prefix-length req=
uirement.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">For server behavior, we used &quot;SHOULD&quot; beca=
use this document specifies the desired server behavior if the server wants=
 to consider the prefix-length hint, but the server could have its own beha=
vioral policy (e.g. neglect the prefix-length
 hint).<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] This make sense, bu=
t it will be good to clarify why it is a SHOULD using your explanation</spa=
n></i></b><span style=3D"font-size:11pt;font-family:calibri,sans-serif;colo=
r:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">5.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution, what=
 should the server do if cannot<br>
provide any of the requests<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] If the server could not provide the requ=
ested prefix or prefix-length, it should provide a prefix closest to the pr=
efix-length hint, as stated in the last sentence of section 3.2.<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Are you referring to what the sever should do of it =
simply could not provide ANY prefixes to the client? In that case, we could=
 add a sentence at the end of the section 3.2:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">&quot;If the server will not assign any prefixes to =
any IA_PDs in a subsequent Request from the client, the server MUST send an=
 Advertise message to the client as described in section 11.2 of RFC 3633.&=
quot;<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] This sentence is wh=
at I was looking for.</span></i></b><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">6.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution last =
paragraph =E2=80=9CSHOULD try to provide=E2=80=9D and<br>
in the first paragraph =E2=80=9CSHOULD provide=E2=80=9D should be the same =
in both.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] Thanks for pointing that out, we&#39;ll =
change it to &quot;SHOULD provide&quot;.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-family:cali=
bri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK<u></u><u></u></span></i=
></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">7.=C2=A0 =C2=A0 =C2=A0 In section 3.4 =E2=80=9CIf th=
e client decided to use=C2=A0 the prefix provided<br>
by the server despite being longer than the=C2=A0 prefix-length hint=E2=80=
=9D yet I<br>
did not see in section 3.2 that the server can provide a longer<br>
prefix.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">&quot;If the requested prefix is not available in th=
e server&#39;s prefix pool, and the client also included a prefix-length hi=
nt in the same IA_PD option, then the server SHOULD try to provide a prefix=
 matching the prefix-length value, or the prefix
 with the shortest length possible which is closest to the prefix-length hi=
nt value.&quot;<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] I understood from 3=
.2 that it should provide a shorter length prefix =C2=A0closer to the reque=
st maybe =E2=80=9C</span></i></b>or the prefix with the closest
 possible length to the prefix-length hint value=E2=80=9D<span style=3D"fon=
t-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u>=
</u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0</p></div></span></div></div></div></div></div=
></div></blockquote><div>[Tianxiang2] The original sentence was a bit confu=
sing, perhaps we could change it like this:</div><div><br></div><div>OLD:=
=C2=A0&quot;If the requested prefix is not available in the server&#39;s pr=
efix pool, and the client also included a prefix-length hint in the same IA=
_PD option, then the server SHOULD try to provide a prefix matching the pre=
fix-length value, or the prefix with the shortest length possible which is =
closest to the prefix-length hint value.&quot;</div><div><br></div><div>NEW=
:&quot;If the requested prefix is not available in the server&#39;s prefix =
pool, and the client also included a prefix-length hint in the same IA_PD o=
ption, then the server SHOULD provide a prefix matching the prefix-length h=
int, or a prefix which is length is shorter and as close as possible to the=
 prefix-length hint. If the server could not provide a prefix which length =
is shorter or equal to the prefix-length hint, the server SHOULD provide th=
e prefix which length is longer and as close as possible to the prefix-leng=
th hint.&quot;</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-6060726979536003119gmail-m_=
-6524802112207049246gmail-m_-4900649193753751102WordSection1"><div style=3D=
"border-top:none;border-right:none;border-bottom:none;border-left:1.5pt sol=
id blue;padding:0cm 0cm 0cm 4pt"><div><div><div><span class=3D"m_-606072697=
9536003119gmail-m_-6524802112207049246gmail-"><div><p class=3D"MsoNormal"><=
u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">8.=C2=A0 =C2=A0 =C2=A0 In section 3.5 solution the d=
ocument use =E2=80=9Cas close as possible=E2=80=9D and<br>
section 3.2 only talk about smaller.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2.=C2=A0<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] See above to point =
7</span></i></b><span style=3D"font-size:11pt;font-family:calibri,sans-seri=
f;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">9.=C2=A0 =C2=A0 =C2=A0In section 3.5 solution why of=
fer options 3 and 4. The draft<br>
says that option 3 will break client connections and 4 talks about =E2=80=
=9Ca<br>
short non-zero valid-lifetime=E2=80=9D which may cause the=C2=A0 client to =
lose<br>
connection if &quot;too short for the client&quot; since =E2=80=9Cshort=E2=
=80=9D is not an exact<br>
value=C2=A0<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] The idea was to list all the options, an=
d discuss their consequences. And the server could decide which option to u=
se depending on its policy.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">Option 3 avoids the complexity of handling multiple =
delegated prefixes, despite of breaking up all connections. Option 4 allows=
 to server to configure a valid-lifetime for the old prefix depending on ac=
tual requirements, rather than let
 the old prefix expire on its own.<span style=3D"color:rgb(31,73,125)"><u><=
/u><u></u></span></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK, still option 4 =
may have similar result to 3 since =E2=80=9Ca short non-zero=E2=80=9D may b=
e too short. Why not add a recommended value?<u></u><u></u></span></i></b><=
/p>
<p class=3D"MsoNormal">=C2=A0</p></div></div></div></div></div></div></div>=
</blockquote><div>[Tianxiang2] Agree, as this may vary for different servic=
es, we could change the text to say &quot;a specific valid-lifetime dependi=
ng on the actual requirement&quot;.=C2=A0</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-6=
060726979536003119gmail-m_-6524802112207049246gmail-m_-4900649193753751102W=
ordSection1"><div style=3D"border-top:none;border-right:none;border-bottom:=
none;border-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt"><div><div><div><=
div><p class=3D"MsoNormal"><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><br>
<br>
Nits/editorial comments:<br>
<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--001a1140a4621dc8a505477a049b--


From nobody Wed Feb  1 11:55:18 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49DA6129EAD for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 11:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 366EehPukdAw for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 11:55:15 -0800 (PST)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 735B3129562 for <gen-art@ietf.org>; Wed,  1 Feb 2017 11:47:29 -0800 (PST)
Received: by mail-pg0-x232.google.com with SMTP id 204so111710637pge.0 for <gen-art@ietf.org>; Wed, 01 Feb 2017 11:47:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=8+ONrldl/pWLuj8zB43k6/eXEedbo/QkyBlR2lSbGkY=; b=jGP+uYlawPHXxhe7hdoY37bFdEZZax5Sl7Zu7k+Y76zrb1h4fyqBVwDu96ij3fgYNA S9OJJ4eXBLQqhUYMAf+mDdftCOF97AgFqeM3GyhudES+YOu5pUCopwOvFnOCgj+29cFp +SGKfohUUvRiZ7H0O4ZKuGnrs4M0/jju1GyKI+06TgVhFS+BdxG8XW1iOh3qAtusDnMD B+P+CbinZCfYhG1fdsAEZMVZ3njRs2v3sXaSvI+2wNfkrN2lnst/Mcp21dpcb/ovhKBc p2kniE6ZzrJOEZNwC1puL70FuTWONDvIrBgDHo5hMj8ktauByaPBpI0e0QCdMBSFkYJf ihkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=8+ONrldl/pWLuj8zB43k6/eXEedbo/QkyBlR2lSbGkY=; b=CkfBA5uLw3M0Z3GAN8mL9yFt8UqDTxcumBf5/F1c++PKLT7qKgnGRKwmVkugRAJLMs JR8CiK2pD0zyx2giGMIpmD/f9mlNebsCDPDcNxxpkbHcLoelLqrWq96rXBAiHWa4P8W6 kYQd5nWbFm8UwxOr72or3jBWlosHujVO9pM4rraLyrGyaAM0LutKmhXvCZpnoQm8pWQO ymzpETsd4p5LgIgvZSoJNoStLxIA4nK1prBt8gFeLImMX32gRnv8q3EvfNiJB4eWF+pm R8viF7eyrY9W2tHIna8At89z8Tt6Arr/vDnylCQLErcsee/O6dlwnmQgxdQwyYYMvWGc Ng/g==
X-Gm-Message-State: AIkVDXKI8lnpYMeoFGr0aqILruMJ++dJ/BbnpYDITFiRv9UGQULD00INPdzHUzsm4Syn/Q==
X-Received: by 10.84.229.143 with SMTP id c15mr6794730plk.177.1485978448871; Wed, 01 Feb 2017 11:47:28 -0800 (PST)
Received: from [192.168.178.21] ([118.148.120.107]) by smtp.gmail.com with ESMTPSA id j7sm51707921pfe.84.2017.02.01.11.47.27 for <gen-art@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2017 11:47:28 -0800 (PST)
To: General Area Review Team <gen-art@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7de47509-0ecf-6526-d50e-2d3b52025574@gmail.com>
Date: Thu, 2 Feb 2017 08:47:30 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/NnTSI57FtraAOZeTTvpNvuFZ0z4>
Subject: [Gen-art] Bounce test, please ignore
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 19:55:16 -0000

This is a test to see if a bounce problem has been resolved.

Avri, if you get this via gen-art, but didn't get one from
tianxiang li <peter416733@gmail.com> the problem
has indeed been resolved.

    Brian


From nobody Wed Feb  1 11:57:15 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50ED6129570; Wed,  1 Feb 2017 11:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MDtoaBj6V2Ri; Wed,  1 Feb 2017 11:57:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 617FE12956B; Wed,  1 Feb 2017 11:57:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 563A02D299; Wed,  1 Feb 2017 21:57:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3eNLGNPoYc0; Wed,  1 Feb 2017 21:57:05 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 047FE2CC9B; Wed,  1 Feb 2017 21:57:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_DC383374-5AD8-4AF0-82AB-14124142BBDD"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <e1951f44-8698-54a2-0ef3-47dce3c69d8a@alum.mit.edu>
Date: Wed, 1 Feb 2017 20:57:02 +0100
Message-Id: <53FE5CAF-9E9B-4391-A46B-9AD0321DA51D@piuha.net>
References: <53ca0098-3b4c-3498-781a-667959e546b6@alum.mit.edu> <BN3PR03MB23556CDB0BC7424911CBBE21F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <b207491e-ca86-2c3c-c51b-a328e4c8d101@alum.mit.edu> <BN3PR03MB235584EA38F524E767BF8B97F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <e1951f44-8698-54a2-0ef3-47dce3c69d8a@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/GnvHPkI-IX1LFFtgdjqvwOFOm0E>
Cc: Mike Jones <Michael.Jones@microsoft.com>, "draft-ietf-oauth-amr-values.all@ietf.org" <draft-ietf-oauth-amr-values.all@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-amr-values-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 19:57:14 -0000

--Apple-Mail=_DC383374-5AD8-4AF0-82AB-14124142BBDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks for your review, Paul, and thanks for the discussion, Mike.

I think there=E2=80=99s text in 5226bis about it being possible to ask =
people to post things
to a mailing list.

Jari

On 26 Jan 2017, at 22:05, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 1/26/17 3:48 PM, Mike Jones wrote:
>> The designated experts are subscribed to the review mailing list.  =
Either IANA or individuals can send (or forward) requests to it.  There =
have been cases where IANA has directly received requests, which they =
have forwarded to the list for review, thereby also reaching the =
designated experts.  It works fine in practice and achieves the goals of =
RFC 5226, even if all the steps are not literally always done in the =
same order.
>>=20
>> The IESG has already approved this kind of procedure for .well-known =
URI registrations (using the wellknown-uri-review@ietf.org list, per RFC =
5785), for OAuth registrations (using the oauth-ext-review@ietf.org =
list, per RFC 6749 and RFC 7591), for JOSE registrations (using the =
jose-reg-review@ietf.org list, per RFC 7515, RFC 7517, and RFC 7518) and =
for JWT registrations (using the jwt-reg-review@ietf.org list, per RFC =
7519 and RFC 7800).  Given all this working existing practice, I don't =
see a sound reason for the IESG to reject using this same procedure for =
an additional kind of JWT registration.
>=20
> In that case the proper thing to do would be to revise RFC5226 to =
acknowledge this approach. But in the end, if IANA and the IESG are OK =
with this then so be it.
>=20
>> Please don't get me wrong - I do appreciate your detailed scrutiny of =
the spec bringing this up.  I think we agree that consistency matters.
>=20
> Thanks. IIUC that is the role of Gen-Art reviews.
>=20
> 	Thanks,
> 	Paul
>=20
>> 				-- Mike
>>=20
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> Sent: Thursday, January 26, 2017 12:28 PM
>> To: Mike Jones <Michael.Jones@microsoft.com>; =
draft-ietf-oauth-amr-values.all@ietf.org
>> Cc: General Area Review Team <gen-art@ietf.org>
>> Subject: Re: [Gen-art] Gen-ART Telechat review of =
draft-ietf-oauth-amr-values-05
>>=20
>> Mike,
>>=20
>> On 1/26/17 2:38 PM, Mike Jones wrote:
>>> Hi Paul,
>>>=20
>>> Per my earlier reply at =
https://www.ietf.org/mail-archive/web/gen-art/current/msg14212.html, the =
specified registration procedure is the standard IANA one, prefixed by a =
public review period.  JWT registrations, OAuth registrations, =
.well-known registrations, and others all already work this way.  It =
works well in practice.  Particularly since changing the registration =
procedure for this JWT claim would make it inconsistent with registering =
JWT claims, I believe that the working group would strongly oppose =
removing the public review period step.
>>>=20
>>> I would therefore ask that you withdraw your request to revise the =
registration procedure, on this basis.
>>=20
>> I'm sorry, but I can't see how what you call for is consistent with =
what
>> RFC5226 says about the role of IANA with repositories controlled by =
expert review.
>>=20
>> That document *explicitly* says
>>=20
>>    In many cases, some review of prospective allocations is =
appropriate,
>>    and the question becomes who should perform the review and what is
>>    the purpose of the review.  One might think that an IETF working
>>    group (WG) familiar with the namespace at hand should be =
consulted.
>>    In practice, however, WGs eventually disband, so they cannot be
>>    considered a permanent evaluator.  It is also possible for =
namespaces
>>    to be created through individual submission documents, for which =
no
>>    WG is ever formed.
>> ...
>>    While discussion on a mailing list can provide valuable technical
>>    feedback, opinions may vary and discussions may continue for some
>>    time without clear resolution.  In addition, IANA cannot =
participate
>>    in all of these mailing lists and cannot determine if or when such
>>    discussions reach consensus.  Therefore, IANA relies on a =
"designated
>>    expert" for advice regarding the specific question of whether an
>>    assignment should be made.  The designated expert is an individual
>>    who is responsible for carrying out an appropriate evaluation and
>>    returning a recommendation to IANA.
>> ...
>>    The designated expert is responsible for initiating and =
coordinating
>>    the appropriate review of an assignment request.  The review may =
be
>>    wide or narrow, depending on the situation and the judgment of the
>>    designated expert.  This may involve consultation with a set of
>>    technology experts, discussion on a public mailing list, =
consultation
>>    with a working group (or its mailing list if the working group has
>>    disbanded), etc.  Ideally, the designated expert follows specific
>>    review criteria as documented with the protocol that creates or =
uses
>>    the namespace.  (See the IANA Considerations sections of [RFC3748]
>>    and [RFC3575] for examples that have been done for specific
>>    namespaces.)
>> ...
>>    Designated experts are appointed by the IESG (normally upon
>>    recommendation by the relevant Area Director).  They are typically
>>    named at the time a document creating or updating a namespace is
>>    approved by the IESG, but as experts originally appointed may =
later
>>    become unavailable, the IESG will appoint replacements if =
necessary.
>> ...
>>    In registries where a pool of experts evaluates requests, the pool
>>    should have a single chair responsible for defining how requests =
are
>>    to be assigned to and reviewed by experts.  In some cases, the =
expert
>>    pool may consist of a primary and backups, with the backups =
involved
>>    only when the primary expert is unavailable.  In other cases, IANA
>>    might assign requests to individual members in sequential or
>>    approximate random order.  In the event that IANA finds itself =
having
>>    received conflicting advice from its experts, it is the
>>    responsibility of the pool's chair to resolve the issue and =
provide
>>    IANA with clear instructions.
>>=20
>> Meanwhile, your document says:
>>=20
>>    IANA must only accept registry updates from the Designated Experts
>>    and should direct all requests for registration to the review =
mailing
>>    list.
>>=20
>> So, as I read it, the process according to 5226 would be:
>>=20
>> 1) IANA receives a request;
>> 2) IANA asks the designated expert (or chairman of a group of =
experts)
>>    to review the request;
>> 3) expert reviews the request, possibly consulting a mailing list;
>> 4) expert replies to IANA with approval or disapproval;
>> 5) in the case of approval IANA updates the registry.
>>=20
>> While as I read it the process according to your document would be:
>>=20
>> 1) If IANA receives a request from a non-expert, it is to refuse it
>>    and refer the requester to the jwt-reg-review@ietf.org mailing =
list;
>> 2) the requester sends a request to the mailing list;
>> 3) after discussion, an expert forwards the request to IANA;
>> 4) IANA updates the registry.
>>=20
>> Hence I don't think that what you call out is consistent with expert =
review as defined in RFC5226.
>>=20
>> Ultimately it is up to the IESG and IANA to decide if they want to =
allow this variant procedure.
>>=20
>> 	Thank you,
>> 	Paul Kyzivat
>>=20
>>=20
>>> 				Thank you,
>>> 				-- Mike
>>>=20
>>> -----Original Message-----
>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>> Sent: Thursday, January 26, 2017 9:51 AM
>>> To: draft-ietf-oauth-amr-values.all@ietf.org
>>> Cc: General Area Review Team <gen-art@ietf.org>
>>> Subject: [Gen-art] Gen-ART Telechat review of
>>> draft-ietf-oauth-amr-values-05
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair. Please wait for direction from your document =
shepherd or AD before posting a new version of the draft. For more =
information, please see the FAQ at =
<=E2=80=8Bhttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Document: draft-ietf-oauth-amr-values-05
>>> Reviewer: Paul Kyzivat
>>> Review Date: 2017-01-26
>>> IETF LC End Date: 2016-12-13
>>> IESG Telechat date:2017-01-32
>>>=20
>>> Summary:
>>>=20
>>> This draft is on the right track but has open issues, described in =
the review.
>>>=20
>>> It is generally well written, with much better guidelines for expert =
reviewers than I typically see.
>>>=20
>>> Disclaimer:
>>>=20
>>> I'm not well versed in JSON Web Tokens, so I have not considered the =
pros/cons of having this registry or of the specific values being =
registered. I have focused on the mechanics of the draft.
>>>=20
>>> Issues:
>>>=20
>>> Major: 0
>>> Minor: 1
>>> Nits:  0
>>>=20
>>> (1) Minor:
>>>=20
>>> Section 6.1 says:
>>>=20
>>>     IANA must only accept registry updates from the Designated =
Experts
>>>     and should direct all requests for registration to the review
>>>     mailing list.
>>>=20
>>> This is inconsistent with the way IANA Expert Review works, as =
defined in section 3 of RFC5226. Requests go through some channel (e.g. =
IESG review for standards track RFCs) to the editor and then IANA =
actions requiring expert review are referred to a designated expert. The =
expert then approves or denies the request, and approved requests are =
acted upon by IANA.
>>>=20
>>> Direction of requests to a mailing list is not an IANA function, but =
could be done by the expert.
>>>=20
>>> Please revise the text and procedures to be consistent with the way =
Expert Review is intended to work.
>>>=20
>>> (Note: In my earlier last call review of this document I erroneously
>>> cited RFC5526 rather than RFC5226. I have corrected that above.)
>>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_DC383374-5AD8-4AF0-82AB-14124142BBDD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkj2OAAoJEM80gCTQU46qiXIQAKO6TtC96SVHR+eZ8zWBCJ8K
n3foU2+dw8n91JsFLFx+1jWzHve/fWtOdeAIdeI3YW/hPaan5YAVf+IH8Ydv95+g
3WlxUP/FnInK6fbCLWfKhp+xe+xuvw7fQj/Rlkpc8lJfgidUrTNeIiH3Rc7qobTd
reBG2bbcTQNL9kDh5VO7EuvRHKvMUvkhjgXBS+cCiANGy7oW0kKWSh/2kbGHXNhn
qzjK2OuqWY8qHujmg0qEm3yTo4NwssOlgTioC8gWMRDJfAbq3Mu6S825HC2UgDM9
oHWfZCmcTPxqUuM+QAc2PRkW1z6SKvYFe8OPGTbldoJyciYuj/I9/Hy2wtdEYomY
e3EH1/TQjjH4OCkinitcd2z+T/wOo50aGZpRccFwKyoM3KCQJSqqvbJd4x0VoQHl
RoUaGCjAybTmRkpZMyYCVSytdjlbAKPs4N8KLgR+qhjotMNoySrSgh6p5loaiWsh
INEoziimw4C6dB738SsGoSHu3zlIiowTu5wMRgTWs3yZiSKfJcMo/5l3GR2Uoh5O
AHZe/FOnfHsMPDd1xF++AJL/WNlJ0Rn0Yo8Y7IT+dKpC+OyFblZ3fka2TAWYw2KS
qTfpGr9Pg30NIZ/rfSpxOA6/4+fs6ReLJF2SlIoF7T8632aZ8zxqOKxlG8WgYffl
fotYlv4PIoasSh+XMAGv
=Bzs/
-----END PGP SIGNATURE-----

--Apple-Mail=_DC383374-5AD8-4AF0-82AB-14124142BBDD--


From nobody Wed Feb  1 12:02:04 2017
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1D531297BD; Wed,  1 Feb 2017 12:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iehWWqZAEusA; Wed,  1 Feb 2017 12:02:00 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0138.outbound.protection.outlook.com [104.47.36.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45FE01299D9; Wed,  1 Feb 2017 12:01:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=7iA44W6zea7S0RdirbPrkWHxInxEBG5T9Lt/mLiQpT0=; b=OqbazP5JoVq4Rea9SoyJLE5Wke2pZLSaAB85vnpL3LoE+VRmKC3OnGjCXwRg/k/xxkpk3Zi9fGuqUZOjHNvhlx5ZlX5dW5ynkQpKEgjMyhT4qs1v+Nqy0/gsIZMBLGak0lvA4qwVJK/XTSUNXsXwnFbtII47Wp+VMJ8rAf4Z05c=
Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2353.namprd03.prod.outlook.com (10.166.74.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Wed, 1 Feb 2017 20:01:36 +0000
Received: from BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) by BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) with mapi id 15.01.0874.021; Wed, 1 Feb 2017 20:01:36 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jari Arkko <jari.arkko@piuha.net>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-amr-values-05
Thread-Index: AQHSd/zHYNPaUrYrc0iRbBeROIksYKFLJhAAgAAPWYCAAAEFgIAACY2AgAlawACAAADEQA==
Date: Wed, 1 Feb 2017 20:01:35 +0000
Message-ID: <BN3PR03MB23552DC550E64CF7164B1F53F54D0@BN3PR03MB2355.namprd03.prod.outlook.com>
References: <53ca0098-3b4c-3498-781a-667959e546b6@alum.mit.edu> <BN3PR03MB23556CDB0BC7424911CBBE21F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <b207491e-ca86-2c3c-c51b-a328e4c8d101@alum.mit.edu> <BN3PR03MB235584EA38F524E767BF8B97F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <e1951f44-8698-54a2-0ef3-47dce3c69d8a@alum.mit.edu> <53FE5CAF-9E9B-4391-A46B-9AD0321DA51D@piuha.net>
In-Reply-To: <53FE5CAF-9E9B-4391-A46B-9AD0321DA51D@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com; 
x-originating-ip: [2001:4898:80e8:c::388]
x-ms-office365-filtering-correlation-id: c6377c01-d00a-4edd-0930-08d44add20a4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:BN3PR03MB2353; 
x-microsoft-exchange-diagnostics: 1; BN3PR03MB2353; 7:MjS2UpA3MVmyOud8+nHgZc420gjNohWT+up2jKybcEZBOzt9eo8Jnugrno7+kFtxNkdCpFTFEOWKiaaMTf/bakC9qq4gxtirtFtfSrUQNhUwGdoNIFbvxVJmzvRBN/11lXGpNWVoJ0KPKIJs/wq6djTQ5UEiHdKOQFYEQtF15PqYHS0B/LJuW1ngaJ4ooTjkc0FT75MAln0LkS67CsQOwTpn+Hrbhw48Xlzys1G856m86WvpJxEIZUZYnkTBB2gxNmwGjRpZY88Y1dDPEojPSpO7bJcEPFrYkO+6h3Ca7Y7yfnviC36Ljk78bQd9WDf1+oih+PRdT5e4OWeTT8qi4JA7oCY0YkcU8HJ+BWLGquUI9UxEt2pjU6C6DOO5dFm/dypF4NFfVaYq8qxEBWa5UxIWsgIQjXJio5r3j1OjWJqV57h3jfec4rV7Pz1SeCooZ0fhuIvmN01ITMrAVIjtqz9YxzFUfjSDMbmR08VGP+P06Fk6jqLJqOt/UP4bCu7uvdr4pirILUwjwFl0rFiTCil0K3OG6NENQTc1SG6Wr6h/x+0BLAExFp+dit9h9ltY
x-microsoft-antispam-prvs: <BN3PR03MB23535F2782CF59C3E391107FF54D0@BN3PR03MB2353.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123560025)(20161123564025)(20161123555025)(20161123558025)(6072148); SRVR:BN3PR03MB2353; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2353; 
x-forefront-prvs: 0205EDCD76
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(39840400002)(39850400002)(39860400002)(39410400002)(24454002)(199003)(51914003)(13464003)(377454003)(377424004)(189002)(2906002)(2900100001)(81156014)(2950100002)(4326007)(86612001)(53936002)(230783001)(76176999)(5001770100001)(7696004)(81166006)(86362001)(50986999)(5005710100001)(54356999)(92566002)(2171002)(4001150100001)(9686003)(122556002)(6306002)(5660300001)(97736004)(3280700002)(6116002)(102836003)(25786008)(3660700001)(77096006)(189998001)(55016002)(10090500001)(54906002)(99286003)(38730400001)(93886004)(8990500004)(229853002)(10290500002)(33656002)(101416001)(105586002)(8936002)(68736007)(6436002)(8676002)(74316002)(106356001)(6506006)(106116001)(7736002)(305945005); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2353; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2017 20:01:35.9229 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2353
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/keVblIQvCZd6PGdmJZiqoE1HDH0>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-oauth-amr-values.all@ietf.org" <draft-ietf-oauth-amr-values.all@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-amr-values-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 20:02:03 -0000

VGhhbmtzLCBKYXJpLiAgRnJvbSBteSBwZXJzcGVjdGl2ZSwgZ2l2ZW4gdGhhdCB0aGVyZSBhcmUg
bG90cyBvZiByZWdpc3RyYXRpb24gcHJvY2VkdXJlcyBmb3IgZXhpc3RpbmcgUkZDcyB0aGF0IGlu
Y29ycG9yYXRlIGEgcHVibGljIHJldmlldyBwZXJpb2Qgb24gYSBtYWlsaW5nIGxpc3QsIEkgdGhp
bmsgaXQgbWFrZXMgc2Vuc2UgdG8gZXhwbGljaXRseSBjYWxsIG91dCB0aGlzIHBvc3NpYmlsaXR5
IGluIDUyMjZiaXMuDQoNCgkJCQlCZXN0IHdpc2hlcywNCgkJCQktLSBNaWtlDQoNCi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBKYXJpIEFya2tvIFttYWlsdG86amFyaS5hcmtrb0Bw
aXVoYS5uZXRdIA0KU2VudDogV2VkbmVzZGF5LCBGZWJydWFyeSAxLCAyMDE3IDExOjU3IEFNDQpU
bzogUGF1bCBLeXppdmF0IDxwa3l6aXZhdEBhbHVtLm1pdC5lZHU+DQpDYzogTWlrZSBKb25lcyA8
TWljaGFlbC5Kb25lc0BtaWNyb3NvZnQuY29tPjsgZHJhZnQtaWV0Zi1vYXV0aC1hbXItdmFsdWVz
LmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIDxnZW4tYXJ0QGlldGYub3Jn
Pg0KU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBHZW4tQVJUIFRlbGVjaGF0IHJldmlldyBvZiBkcmFm
dC1pZXRmLW9hdXRoLWFtci12YWx1ZXMtMDUNCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldywgUGF1
bCwgYW5kIHRoYW5rcyBmb3IgdGhlIGRpc2N1c3Npb24sIE1pa2UuDQoNCkkgdGhpbmsgdGhlcmXi
gJlzIHRleHQgaW4gNTIyNmJpcyBhYm91dCBpdCBiZWluZyBwb3NzaWJsZSB0byBhc2sgcGVvcGxl
IHRvIHBvc3QgdGhpbmdzIHRvIGEgbWFpbGluZyBsaXN0Lg0KDQpKYXJpDQoNCk9uIDI2IEphbiAy
MDE3LCBhdCAyMjowNSwgUGF1bCBLeXppdmF0IDxwa3l6aXZhdEBhbHVtLm1pdC5lZHU+IHdyb3Rl
Og0KDQo+IE9uIDEvMjYvMTcgMzo0OCBQTSwgTWlrZSBKb25lcyB3cm90ZToNCj4+IFRoZSBkZXNp
Z25hdGVkIGV4cGVydHMgYXJlIHN1YnNjcmliZWQgdG8gdGhlIHJldmlldyBtYWlsaW5nIGxpc3Qu
ICBFaXRoZXIgSUFOQSBvciBpbmRpdmlkdWFscyBjYW4gc2VuZCAob3IgZm9yd2FyZCkgcmVxdWVz
dHMgdG8gaXQuICBUaGVyZSBoYXZlIGJlZW4gY2FzZXMgd2hlcmUgSUFOQSBoYXMgZGlyZWN0bHkg
cmVjZWl2ZWQgcmVxdWVzdHMsIHdoaWNoIHRoZXkgaGF2ZSBmb3J3YXJkZWQgdG8gdGhlIGxpc3Qg
Zm9yIHJldmlldywgdGhlcmVieSBhbHNvIHJlYWNoaW5nIHRoZSBkZXNpZ25hdGVkIGV4cGVydHMu
ICBJdCB3b3JrcyBmaW5lIGluIHByYWN0aWNlIGFuZCBhY2hpZXZlcyB0aGUgZ29hbHMgb2YgUkZD
IDUyMjYsIGV2ZW4gaWYgYWxsIHRoZSBzdGVwcyBhcmUgbm90IGxpdGVyYWxseSBhbHdheXMgZG9u
ZSBpbiB0aGUgc2FtZSBvcmRlci4NCj4+IA0KPj4gVGhlIElFU0cgaGFzIGFscmVhZHkgYXBwcm92
ZWQgdGhpcyBraW5kIG9mIHByb2NlZHVyZSBmb3IgLndlbGwta25vd24gVVJJIHJlZ2lzdHJhdGlv
bnMgKHVzaW5nIHRoZSB3ZWxsa25vd24tdXJpLXJldmlld0BpZXRmLm9yZyBsaXN0LCBwZXIgUkZD
IDU3ODUpLCBmb3IgT0F1dGggcmVnaXN0cmF0aW9ucyAodXNpbmcgdGhlIG9hdXRoLWV4dC1yZXZp
ZXdAaWV0Zi5vcmcgbGlzdCwgcGVyIFJGQyA2NzQ5IGFuZCBSRkMgNzU5MSksIGZvciBKT1NFIHJl
Z2lzdHJhdGlvbnMgKHVzaW5nIHRoZSBqb3NlLXJlZy1yZXZpZXdAaWV0Zi5vcmcgbGlzdCwgcGVy
IFJGQyA3NTE1LCBSRkMgNzUxNywgYW5kIFJGQyA3NTE4KSBhbmQgZm9yIEpXVCByZWdpc3RyYXRp
b25zICh1c2luZyB0aGUgand0LXJlZy1yZXZpZXdAaWV0Zi5vcmcgbGlzdCwgcGVyIFJGQyA3NTE5
IGFuZCBSRkMgNzgwMCkuICBHaXZlbiBhbGwgdGhpcyB3b3JraW5nIGV4aXN0aW5nIHByYWN0aWNl
LCBJIGRvbid0IHNlZSBhIHNvdW5kIHJlYXNvbiBmb3IgdGhlIElFU0cgdG8gcmVqZWN0IHVzaW5n
IHRoaXMgc2FtZSBwcm9jZWR1cmUgZm9yIGFuIGFkZGl0aW9uYWwga2luZCBvZiBKV1QgcmVnaXN0
cmF0aW9uLg0KPiANCj4gSW4gdGhhdCBjYXNlIHRoZSBwcm9wZXIgdGhpbmcgdG8gZG8gd291bGQg
YmUgdG8gcmV2aXNlIFJGQzUyMjYgdG8gYWNrbm93bGVkZ2UgdGhpcyBhcHByb2FjaC4gQnV0IGlu
IHRoZSBlbmQsIGlmIElBTkEgYW5kIHRoZSBJRVNHIGFyZSBPSyB3aXRoIHRoaXMgdGhlbiBzbyBi
ZSBpdC4NCj4gDQo+PiBQbGVhc2UgZG9uJ3QgZ2V0IG1lIHdyb25nIC0gSSBkbyBhcHByZWNpYXRl
IHlvdXIgZGV0YWlsZWQgc2NydXRpbnkgb2YgdGhlIHNwZWMgYnJpbmdpbmcgdGhpcyB1cC4gIEkg
dGhpbmsgd2UgYWdyZWUgdGhhdCBjb25zaXN0ZW5jeSBtYXR0ZXJzLg0KPiANCj4gVGhhbmtzLiBJ
SVVDIHRoYXQgaXMgdGhlIHJvbGUgb2YgR2VuLUFydCByZXZpZXdzLg0KPiANCj4gCVRoYW5rcywN
Cj4gCVBhdWwNCj4gDQo+PiAJCQkJLS0gTWlrZQ0KPj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPj4gRnJvbTogUGF1bCBLeXppdmF0IFttYWlsdG86cGt5eml2YXRAYWx1bS5taXQu
ZWR1XQ0KPj4gU2VudDogVGh1cnNkYXksIEphbnVhcnkgMjYsIDIwMTcgMTI6MjggUE0NCj4+IFRv
OiBNaWtlIEpvbmVzIDxNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb20+OyANCj4+IGRyYWZ0LWll
dGYtb2F1dGgtYW1yLXZhbHVlcy5hbGxAaWV0Zi5vcmcNCj4+IENjOiBHZW5lcmFsIEFyZWEgUmV2
aWV3IFRlYW0gPGdlbi1hcnRAaWV0Zi5vcmc+DQo+PiBTdWJqZWN0OiBSZTogW0dlbi1hcnRdIEdl
bi1BUlQgVGVsZWNoYXQgcmV2aWV3IG9mIA0KPj4gZHJhZnQtaWV0Zi1vYXV0aC1hbXItdmFsdWVz
LTA1DQo+PiANCj4+IE1pa2UsDQo+PiANCj4+IE9uIDEvMjYvMTcgMjozOCBQTSwgTWlrZSBKb25l
cyB3cm90ZToNCj4+PiBIaSBQYXVsLA0KPj4+IA0KPj4+IFBlciBteSBlYXJsaWVyIHJlcGx5IGF0
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvZ2VuLWFydC9jdXJyZW50L21z
ZzE0MjEyLmh0bWwsIHRoZSBzcGVjaWZpZWQgcmVnaXN0cmF0aW9uIHByb2NlZHVyZSBpcyB0aGUg
c3RhbmRhcmQgSUFOQSBvbmUsIHByZWZpeGVkIGJ5IGEgcHVibGljIHJldmlldyBwZXJpb2QuICBK
V1QgcmVnaXN0cmF0aW9ucywgT0F1dGggcmVnaXN0cmF0aW9ucywgLndlbGwta25vd24gcmVnaXN0
cmF0aW9ucywgYW5kIG90aGVycyBhbGwgYWxyZWFkeSB3b3JrIHRoaXMgd2F5LiAgSXQgd29ya3Mg
d2VsbCBpbiBwcmFjdGljZS4gIFBhcnRpY3VsYXJseSBzaW5jZSBjaGFuZ2luZyB0aGUgcmVnaXN0
cmF0aW9uIHByb2NlZHVyZSBmb3IgdGhpcyBKV1QgY2xhaW0gd291bGQgbWFrZSBpdCBpbmNvbnNp
c3RlbnQgd2l0aCByZWdpc3RlcmluZyBKV1QgY2xhaW1zLCBJIGJlbGlldmUgdGhhdCB0aGUgd29y
a2luZyBncm91cCB3b3VsZCBzdHJvbmdseSBvcHBvc2UgcmVtb3ZpbmcgdGhlIHB1YmxpYyByZXZp
ZXcgcGVyaW9kIHN0ZXAuDQo+Pj4gDQo+Pj4gSSB3b3VsZCB0aGVyZWZvcmUgYXNrIHRoYXQgeW91
IHdpdGhkcmF3IHlvdXIgcmVxdWVzdCB0byByZXZpc2UgdGhlIHJlZ2lzdHJhdGlvbiBwcm9jZWR1
cmUsIG9uIHRoaXMgYmFzaXMuDQo+PiANCj4+IEknbSBzb3JyeSwgYnV0IEkgY2FuJ3Qgc2VlIGhv
dyB3aGF0IHlvdSBjYWxsIGZvciBpcyBjb25zaXN0ZW50IHdpdGggDQo+PiB3aGF0DQo+PiBSRkM1
MjI2IHNheXMgYWJvdXQgdGhlIHJvbGUgb2YgSUFOQSB3aXRoIHJlcG9zaXRvcmllcyBjb250cm9s
bGVkIGJ5IGV4cGVydCByZXZpZXcuDQo+PiANCj4+IFRoYXQgZG9jdW1lbnQgKmV4cGxpY2l0bHkq
IHNheXMNCj4+IA0KPj4gICAgSW4gbWFueSBjYXNlcywgc29tZSByZXZpZXcgb2YgcHJvc3BlY3Rp
dmUgYWxsb2NhdGlvbnMgaXMgYXBwcm9wcmlhdGUsDQo+PiAgICBhbmQgdGhlIHF1ZXN0aW9uIGJl
Y29tZXMgd2hvIHNob3VsZCBwZXJmb3JtIHRoZSByZXZpZXcgYW5kIHdoYXQgaXMNCj4+ICAgIHRo
ZSBwdXJwb3NlIG9mIHRoZSByZXZpZXcuICBPbmUgbWlnaHQgdGhpbmsgdGhhdCBhbiBJRVRGIHdv
cmtpbmcNCj4+ICAgIGdyb3VwIChXRykgZmFtaWxpYXIgd2l0aCB0aGUgbmFtZXNwYWNlIGF0IGhh
bmQgc2hvdWxkIGJlIGNvbnN1bHRlZC4NCj4+ICAgIEluIHByYWN0aWNlLCBob3dldmVyLCBXR3Mg
ZXZlbnR1YWxseSBkaXNiYW5kLCBzbyB0aGV5IGNhbm5vdCBiZQ0KPj4gICAgY29uc2lkZXJlZCBh
IHBlcm1hbmVudCBldmFsdWF0b3IuICBJdCBpcyBhbHNvIHBvc3NpYmxlIGZvciBuYW1lc3BhY2Vz
DQo+PiAgICB0byBiZSBjcmVhdGVkIHRocm91Z2ggaW5kaXZpZHVhbCBzdWJtaXNzaW9uIGRvY3Vt
ZW50cywgZm9yIHdoaWNoIG5vDQo+PiAgICBXRyBpcyBldmVyIGZvcm1lZC4NCj4+IC4uLg0KPj4g
ICAgV2hpbGUgZGlzY3Vzc2lvbiBvbiBhIG1haWxpbmcgbGlzdCBjYW4gcHJvdmlkZSB2YWx1YWJs
ZSB0ZWNobmljYWwNCj4+ICAgIGZlZWRiYWNrLCBvcGluaW9ucyBtYXkgdmFyeSBhbmQgZGlzY3Vz
c2lvbnMgbWF5IGNvbnRpbnVlIGZvciBzb21lDQo+PiAgICB0aW1lIHdpdGhvdXQgY2xlYXIgcmVz
b2x1dGlvbi4gIEluIGFkZGl0aW9uLCBJQU5BIGNhbm5vdCBwYXJ0aWNpcGF0ZQ0KPj4gICAgaW4g
YWxsIG9mIHRoZXNlIG1haWxpbmcgbGlzdHMgYW5kIGNhbm5vdCBkZXRlcm1pbmUgaWYgb3Igd2hl
biBzdWNoDQo+PiAgICBkaXNjdXNzaW9ucyByZWFjaCBjb25zZW5zdXMuICBUaGVyZWZvcmUsIElB
TkEgcmVsaWVzIG9uIGEgImRlc2lnbmF0ZWQNCj4+ICAgIGV4cGVydCIgZm9yIGFkdmljZSByZWdh
cmRpbmcgdGhlIHNwZWNpZmljIHF1ZXN0aW9uIG9mIHdoZXRoZXIgYW4NCj4+ICAgIGFzc2lnbm1l
bnQgc2hvdWxkIGJlIG1hZGUuICBUaGUgZGVzaWduYXRlZCBleHBlcnQgaXMgYW4gaW5kaXZpZHVh
bA0KPj4gICAgd2hvIGlzIHJlc3BvbnNpYmxlIGZvciBjYXJyeWluZyBvdXQgYW4gYXBwcm9wcmlh
dGUgZXZhbHVhdGlvbiBhbmQNCj4+ICAgIHJldHVybmluZyBhIHJlY29tbWVuZGF0aW9uIHRvIElB
TkEuDQo+PiAuLi4NCj4+ICAgIFRoZSBkZXNpZ25hdGVkIGV4cGVydCBpcyByZXNwb25zaWJsZSBm
b3IgaW5pdGlhdGluZyBhbmQgY29vcmRpbmF0aW5nDQo+PiAgICB0aGUgYXBwcm9wcmlhdGUgcmV2
aWV3IG9mIGFuIGFzc2lnbm1lbnQgcmVxdWVzdC4gIFRoZSByZXZpZXcgbWF5IGJlDQo+PiAgICB3
aWRlIG9yIG5hcnJvdywgZGVwZW5kaW5nIG9uIHRoZSBzaXR1YXRpb24gYW5kIHRoZSBqdWRnbWVu
dCBvZiB0aGUNCj4+ICAgIGRlc2lnbmF0ZWQgZXhwZXJ0LiAgVGhpcyBtYXkgaW52b2x2ZSBjb25z
dWx0YXRpb24gd2l0aCBhIHNldCBvZg0KPj4gICAgdGVjaG5vbG9neSBleHBlcnRzLCBkaXNjdXNz
aW9uIG9uIGEgcHVibGljIG1haWxpbmcgbGlzdCwgY29uc3VsdGF0aW9uDQo+PiAgICB3aXRoIGEg
d29ya2luZyBncm91cCAob3IgaXRzIG1haWxpbmcgbGlzdCBpZiB0aGUgd29ya2luZyBncm91cCBo
YXMNCj4+ICAgIGRpc2JhbmRlZCksIGV0Yy4gIElkZWFsbHksIHRoZSBkZXNpZ25hdGVkIGV4cGVy
dCBmb2xsb3dzIHNwZWNpZmljDQo+PiAgICByZXZpZXcgY3JpdGVyaWEgYXMgZG9jdW1lbnRlZCB3
aXRoIHRoZSBwcm90b2NvbCB0aGF0IGNyZWF0ZXMgb3IgdXNlcw0KPj4gICAgdGhlIG5hbWVzcGFj
ZS4gIChTZWUgdGhlIElBTkEgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbnMgb2YgW1JGQzM3NDhdDQo+
PiAgICBhbmQgW1JGQzM1NzVdIGZvciBleGFtcGxlcyB0aGF0IGhhdmUgYmVlbiBkb25lIGZvciBz
cGVjaWZpYw0KPj4gICAgbmFtZXNwYWNlcy4pDQo+PiAuLi4NCj4+ICAgIERlc2lnbmF0ZWQgZXhw
ZXJ0cyBhcmUgYXBwb2ludGVkIGJ5IHRoZSBJRVNHIChub3JtYWxseSB1cG9uDQo+PiAgICByZWNv
bW1lbmRhdGlvbiBieSB0aGUgcmVsZXZhbnQgQXJlYSBEaXJlY3RvcikuICBUaGV5IGFyZSB0eXBp
Y2FsbHkNCj4+ICAgIG5hbWVkIGF0IHRoZSB0aW1lIGEgZG9jdW1lbnQgY3JlYXRpbmcgb3IgdXBk
YXRpbmcgYSBuYW1lc3BhY2UgaXMNCj4+ICAgIGFwcHJvdmVkIGJ5IHRoZSBJRVNHLCBidXQgYXMg
ZXhwZXJ0cyBvcmlnaW5hbGx5IGFwcG9pbnRlZCBtYXkgbGF0ZXINCj4+ICAgIGJlY29tZSB1bmF2
YWlsYWJsZSwgdGhlIElFU0cgd2lsbCBhcHBvaW50IHJlcGxhY2VtZW50cyBpZiBuZWNlc3Nhcnku
DQo+PiAuLi4NCj4+ICAgIEluIHJlZ2lzdHJpZXMgd2hlcmUgYSBwb29sIG9mIGV4cGVydHMgZXZh
bHVhdGVzIHJlcXVlc3RzLCB0aGUgcG9vbA0KPj4gICAgc2hvdWxkIGhhdmUgYSBzaW5nbGUgY2hh
aXIgcmVzcG9uc2libGUgZm9yIGRlZmluaW5nIGhvdyByZXF1ZXN0cyBhcmUNCj4+ICAgIHRvIGJl
IGFzc2lnbmVkIHRvIGFuZCByZXZpZXdlZCBieSBleHBlcnRzLiAgSW4gc29tZSBjYXNlcywgdGhl
IGV4cGVydA0KPj4gICAgcG9vbCBtYXkgY29uc2lzdCBvZiBhIHByaW1hcnkgYW5kIGJhY2t1cHMs
IHdpdGggdGhlIGJhY2t1cHMgaW52b2x2ZWQNCj4+ICAgIG9ubHkgd2hlbiB0aGUgcHJpbWFyeSBl
eHBlcnQgaXMgdW5hdmFpbGFibGUuICBJbiBvdGhlciBjYXNlcywgSUFOQQ0KPj4gICAgbWlnaHQg
YXNzaWduIHJlcXVlc3RzIHRvIGluZGl2aWR1YWwgbWVtYmVycyBpbiBzZXF1ZW50aWFsIG9yDQo+
PiAgICBhcHByb3hpbWF0ZSByYW5kb20gb3JkZXIuICBJbiB0aGUgZXZlbnQgdGhhdCBJQU5BIGZp
bmRzIGl0c2VsZiBoYXZpbmcNCj4+ICAgIHJlY2VpdmVkIGNvbmZsaWN0aW5nIGFkdmljZSBmcm9t
IGl0cyBleHBlcnRzLCBpdCBpcyB0aGUNCj4+ICAgIHJlc3BvbnNpYmlsaXR5IG9mIHRoZSBwb29s
J3MgY2hhaXIgdG8gcmVzb2x2ZSB0aGUgaXNzdWUgYW5kIHByb3ZpZGUNCj4+ICAgIElBTkEgd2l0
aCBjbGVhciBpbnN0cnVjdGlvbnMuDQo+PiANCj4+IE1lYW53aGlsZSwgeW91ciBkb2N1bWVudCBz
YXlzOg0KPj4gDQo+PiAgICBJQU5BIG11c3Qgb25seSBhY2NlcHQgcmVnaXN0cnkgdXBkYXRlcyBm
cm9tIHRoZSBEZXNpZ25hdGVkIEV4cGVydHMNCj4+ICAgIGFuZCBzaG91bGQgZGlyZWN0IGFsbCBy
ZXF1ZXN0cyBmb3IgcmVnaXN0cmF0aW9uIHRvIHRoZSByZXZpZXcgbWFpbGluZw0KPj4gICAgbGlz
dC4NCj4+IA0KPj4gU28sIGFzIEkgcmVhZCBpdCwgdGhlIHByb2Nlc3MgYWNjb3JkaW5nIHRvIDUy
MjYgd291bGQgYmU6DQo+PiANCj4+IDEpIElBTkEgcmVjZWl2ZXMgYSByZXF1ZXN0Ow0KPj4gMikg
SUFOQSBhc2tzIHRoZSBkZXNpZ25hdGVkIGV4cGVydCAob3IgY2hhaXJtYW4gb2YgYSBncm91cCBv
ZiBleHBlcnRzKQ0KPj4gICAgdG8gcmV2aWV3IHRoZSByZXF1ZXN0Ow0KPj4gMykgZXhwZXJ0IHJl
dmlld3MgdGhlIHJlcXVlc3QsIHBvc3NpYmx5IGNvbnN1bHRpbmcgYSBtYWlsaW5nIGxpc3Q7DQo+
PiA0KSBleHBlcnQgcmVwbGllcyB0byBJQU5BIHdpdGggYXBwcm92YWwgb3IgZGlzYXBwcm92YWw7
DQo+PiA1KSBpbiB0aGUgY2FzZSBvZiBhcHByb3ZhbCBJQU5BIHVwZGF0ZXMgdGhlIHJlZ2lzdHJ5
Lg0KPj4gDQo+PiBXaGlsZSBhcyBJIHJlYWQgaXQgdGhlIHByb2Nlc3MgYWNjb3JkaW5nIHRvIHlv
dXIgZG9jdW1lbnQgd291bGQgYmU6DQo+PiANCj4+IDEpIElmIElBTkEgcmVjZWl2ZXMgYSByZXF1
ZXN0IGZyb20gYSBub24tZXhwZXJ0LCBpdCBpcyB0byByZWZ1c2UgaXQNCj4+ICAgIGFuZCByZWZl
ciB0aGUgcmVxdWVzdGVyIHRvIHRoZSBqd3QtcmVnLXJldmlld0BpZXRmLm9yZyBtYWlsaW5nIA0K
Pj4gbGlzdDsNCj4+IDIpIHRoZSByZXF1ZXN0ZXIgc2VuZHMgYSByZXF1ZXN0IHRvIHRoZSBtYWls
aW5nIGxpc3Q7DQo+PiAzKSBhZnRlciBkaXNjdXNzaW9uLCBhbiBleHBlcnQgZm9yd2FyZHMgdGhl
IHJlcXVlc3QgdG8gSUFOQTsNCj4+IDQpIElBTkEgdXBkYXRlcyB0aGUgcmVnaXN0cnkuDQo+PiAN
Cj4+IEhlbmNlIEkgZG9uJ3QgdGhpbmsgdGhhdCB3aGF0IHlvdSBjYWxsIG91dCBpcyBjb25zaXN0
ZW50IHdpdGggZXhwZXJ0IHJldmlldyBhcyBkZWZpbmVkIGluIFJGQzUyMjYuDQo+PiANCj4+IFVs
dGltYXRlbHkgaXQgaXMgdXAgdG8gdGhlIElFU0cgYW5kIElBTkEgdG8gZGVjaWRlIGlmIHRoZXkg
d2FudCB0byBhbGxvdyB0aGlzIHZhcmlhbnQgcHJvY2VkdXJlLg0KPj4gDQo+PiAJVGhhbmsgeW91
LA0KPj4gCVBhdWwgS3l6aXZhdA0KPj4gDQo+PiANCj4+PiAJCQkJVGhhbmsgeW91LA0KPj4+IAkJ
CQktLSBNaWtlDQo+Pj4gDQo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+PiBGcm9t
OiBQYXVsIEt5eml2YXQgW21haWx0bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHVdDQo+Pj4gU2VudDog
VGh1cnNkYXksIEphbnVhcnkgMjYsIDIwMTcgOTo1MSBBTQ0KPj4+IFRvOiBkcmFmdC1pZXRmLW9h
dXRoLWFtci12YWx1ZXMuYWxsQGlldGYub3JnDQo+Pj4gQ2M6IEdlbmVyYWwgQXJlYSBSZXZpZXcg
VGVhbSA8Z2VuLWFydEBpZXRmLm9yZz4NCj4+PiBTdWJqZWN0OiBbR2VuLWFydF0gR2VuLUFSVCBU
ZWxlY2hhdCByZXZpZXcgb2YNCj4+PiBkcmFmdC1pZXRmLW9hdXRoLWFtci12YWx1ZXMtMDUNCj4+
PiANCj4+PiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0
LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRG
IGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWly
LiBQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZCBv
ciBBRCBiZWZvcmUgcG9zdGluZyBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdC4gRm9yIG1vcmUg
aW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdCA84oCLaHR0cDovL3dpa2kudG9vbHMu
aWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcT4uDQo+Pj4gDQo+Pj4gRG9jdW1l
bnQ6IGRyYWZ0LWlldGYtb2F1dGgtYW1yLXZhbHVlcy0wNQ0KPj4+IFJldmlld2VyOiBQYXVsIEt5
eml2YXQNCj4+PiBSZXZpZXcgRGF0ZTogMjAxNy0wMS0yNg0KPj4+IElFVEYgTEMgRW5kIERhdGU6
IDIwMTYtMTItMTMNCj4+PiBJRVNHIFRlbGVjaGF0IGRhdGU6MjAxNy0wMS0zMg0KPj4+IA0KPj4+
IFN1bW1hcnk6DQo+Pj4gDQo+Pj4gVGhpcyBkcmFmdCBpcyBvbiB0aGUgcmlnaHQgdHJhY2sgYnV0
IGhhcyBvcGVuIGlzc3VlcywgZGVzY3JpYmVkIGluIHRoZSByZXZpZXcuDQo+Pj4gDQo+Pj4gSXQg
aXMgZ2VuZXJhbGx5IHdlbGwgd3JpdHRlbiwgd2l0aCBtdWNoIGJldHRlciBndWlkZWxpbmVzIGZv
ciBleHBlcnQgcmV2aWV3ZXJzIHRoYW4gSSB0eXBpY2FsbHkgc2VlLg0KPj4+IA0KPj4+IERpc2Ns
YWltZXI6DQo+Pj4gDQo+Pj4gSSdtIG5vdCB3ZWxsIHZlcnNlZCBpbiBKU09OIFdlYiBUb2tlbnMs
IHNvIEkgaGF2ZSBub3QgY29uc2lkZXJlZCB0aGUgcHJvcy9jb25zIG9mIGhhdmluZyB0aGlzIHJl
Z2lzdHJ5IG9yIG9mIHRoZSBzcGVjaWZpYyB2YWx1ZXMgYmVpbmcgcmVnaXN0ZXJlZC4gSSBoYXZl
IGZvY3VzZWQgb24gdGhlIG1lY2hhbmljcyBvZiB0aGUgZHJhZnQuDQo+Pj4gDQo+Pj4gSXNzdWVz
Og0KPj4+IA0KPj4+IE1ham9yOiAwDQo+Pj4gTWlub3I6IDENCj4+PiBOaXRzOiAgMA0KPj4+IA0K
Pj4+ICgxKSBNaW5vcjoNCj4+PiANCj4+PiBTZWN0aW9uIDYuMSBzYXlzOg0KPj4+IA0KPj4+ICAg
ICBJQU5BIG11c3Qgb25seSBhY2NlcHQgcmVnaXN0cnkgdXBkYXRlcyBmcm9tIHRoZSBEZXNpZ25h
dGVkIEV4cGVydHMNCj4+PiAgICAgYW5kIHNob3VsZCBkaXJlY3QgYWxsIHJlcXVlc3RzIGZvciBy
ZWdpc3RyYXRpb24gdG8gdGhlIHJldmlldw0KPj4+ICAgICBtYWlsaW5nIGxpc3QuDQo+Pj4gDQo+
Pj4gVGhpcyBpcyBpbmNvbnNpc3RlbnQgd2l0aCB0aGUgd2F5IElBTkEgRXhwZXJ0IFJldmlldyB3
b3JrcywgYXMgZGVmaW5lZCBpbiBzZWN0aW9uIDMgb2YgUkZDNTIyNi4gUmVxdWVzdHMgZ28gdGhy
b3VnaCBzb21lIGNoYW5uZWwgKGUuZy4gSUVTRyByZXZpZXcgZm9yIHN0YW5kYXJkcyB0cmFjayBS
RkNzKSB0byB0aGUgZWRpdG9yIGFuZCB0aGVuIElBTkEgYWN0aW9ucyByZXF1aXJpbmcgZXhwZXJ0
IHJldmlldyBhcmUgcmVmZXJyZWQgdG8gYSBkZXNpZ25hdGVkIGV4cGVydC4gVGhlIGV4cGVydCB0
aGVuIGFwcHJvdmVzIG9yIGRlbmllcyB0aGUgcmVxdWVzdCwgYW5kIGFwcHJvdmVkIHJlcXVlc3Rz
IGFyZSBhY3RlZCB1cG9uIGJ5IElBTkEuDQo+Pj4gDQo+Pj4gRGlyZWN0aW9uIG9mIHJlcXVlc3Rz
IHRvIGEgbWFpbGluZyBsaXN0IGlzIG5vdCBhbiBJQU5BIGZ1bmN0aW9uLCBidXQgY291bGQgYmUg
ZG9uZSBieSB0aGUgZXhwZXJ0Lg0KPj4+IA0KPj4+IFBsZWFzZSByZXZpc2UgdGhlIHRleHQgYW5k
IHByb2NlZHVyZXMgdG8gYmUgY29uc2lzdGVudCB3aXRoIHRoZSB3YXkgRXhwZXJ0IFJldmlldyBp
cyBpbnRlbmRlZCB0byB3b3JrLg0KPj4+IA0KPj4+IChOb3RlOiBJbiBteSBlYXJsaWVyIGxhc3Qg
Y2FsbCByZXZpZXcgb2YgdGhpcyBkb2N1bWVudCBJIGVycm9uZW91c2x5IA0KPj4+IGNpdGVkIFJG
QzU1MjYgcmF0aGVyIHRoYW4gUkZDNTIyNi4gSSBoYXZlIGNvcnJlY3RlZCB0aGF0IGFib3ZlLikN
Cj4+PiANCj4+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4gR2VuLWFydEBpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCg0K


From nobody Wed Feb  1 12:13:49 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69C7129576; Wed,  1 Feb 2017 12:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS5ScprzbNlb; Wed,  1 Feb 2017 12:13:34 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 97C4212956E; Wed,  1 Feb 2017 12:13:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C3A942D299; Wed,  1 Feb 2017 22:13:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihT6ub-54zNH; Wed,  1 Feb 2017 22:13:32 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0C0EB2CC9B; Wed,  1 Feb 2017 22:13:31 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6491B041-B784-4239-BE81-8E6C16B38359"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148458513714.22450.5314587510279930489.idtracker@ietfa.amsl.com>
Date: Wed, 1 Feb 2017 21:13:06 +0100
Message-Id: <95043D9F-639E-4F39-A9F1-CE331000EAEE@piuha.net>
References: <148458513714.22450.5314587510279930489.idtracker@ietfa.amsl.com>
To: Dan Romascanu <dromasca@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/u_vcOZtH6f7C6YKQF32HLGZLEKs>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-teas-p2mp-loose-path-reopt.all@ietf.org, teas@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-teas-p2mp-loose-path-reopt-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 20:13:35 -0000

--Apple-Mail=_6491B041-B784-4239-BE81-8E6C16B38359
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Dan.

Jari


--Apple-Mail=_6491B041-B784-4239-BE81-8E6C16B38359
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkkFlAAoJEM80gCTQU46qxAUQAL7xCG140g1o5x9r7FYch9Gw
TtVnhOlheFZFONN0HL7qTb/vWXxjVac2XWhid+OUAjM0/NpL2HPosaA8HO8mB81L
YCUSVNHkUbtFRPtyr8C4PhMbe3bTIjeLiX5qPgaxzkZONCgQAavbi7b1axAT5j64
V83wGSra51m8qYgOxUvQc1KsWdr6Jt19IcZWHhJCJlN5wS+OlX8ajtaK8gW4lfHI
xU9qHA9Akz3Mj7pqUpnPj1qBkaY7ISQk29TF+vTkTf8uzzana9RlIxkfARQ6ljOE
NOC0tYwL31sV9kPdTYUC3RQsrUUVjx4+lRetDM+EAMgakQi0UOWS91VkN1PBmqrQ
ROobHE6y+jBNcBbXO7OykgRYWJgMS9IxlKPVvaOzPUG2/ukvNYR1n/zv/ynjXR48
lfGUjiVpmO8vdDrdwMuhD3xG/iHFvRH15jBIA3w+EIWPJhZsJNcD2tl7YY0iV9aT
UbUICbFbx5HDquTGC7nN8j7YJtR0ONJRXNSj9rdqaVuUeQbxHRhVDwz/FOkCEuhu
Oj4AuPg2btvgm+CnXnjtVUGwQaBsXg3MQUf1b+l9F6xkuq7WfZHguOAC97X/W5wu
7aZ/MNFaHea4M4Cu+T8w7Mew08qDMe+xOdPSPf+wlesTUZ1NRVCb9alo6tkun0oh
nnJCMpnfdEb74YmLCsG6
=Vgey
-----END PGP SIGNATURE-----

--Apple-Mail=_6491B041-B784-4239-BE81-8E6C16B38359--


From nobody Wed Feb  1 12:30:23 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2AD1299E9 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 12:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhW8kAGwq6c4 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 12:30:20 -0800 (PST)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A05A1299A3 for <gen-art@ietf.org>; Wed,  1 Feb 2017 12:30:20 -0800 (PST)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-12v.sys.comcast.net with SMTP id Z1XYctHPY6RInZ1Xnc2pai; Wed, 01 Feb 2017 20:30:19 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-20v.sys.comcast.net with SMTP id Z1XmcBFELqiCcZ1XmcNvnx; Wed, 01 Feb 2017 20:30:19 +0000
To: Jari Arkko <jari.arkko@piuha.net>
References: <53ca0098-3b4c-3498-781a-667959e546b6@alum.mit.edu> <BN3PR03MB23556CDB0BC7424911CBBE21F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <b207491e-ca86-2c3c-c51b-a328e4c8d101@alum.mit.edu> <BN3PR03MB235584EA38F524E767BF8B97F5770@BN3PR03MB2355.namprd03.prod.outlook.com> <e1951f44-8698-54a2-0ef3-47dce3c69d8a@alum.mit.edu> <53FE5CAF-9E9B-4391-A46B-9AD0321DA51D@piuha.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9fbc4069-f899-35ee-fb59-2aebe36099d2@alum.mit.edu>
Date: Wed, 1 Feb 2017 15:30:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <53FE5CAF-9E9B-4391-A46B-9AD0321DA51D@piuha.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfHO4jto4Csc/trOeBglAcf6Wo+ss0Djdl5I77bj3sxbK6r1u2EyT21wSa8PUs2o5OVy6Nyx10Brb91RwkqwyKaaQ6HejSGnf5ZadxpCzVxsyvYxD3p3Q 00UJLKSVkEqV/KQ6ZFqUcEG4DHbopUP2AC8tO49FroZfdvMe8acYIVFs/XBSBSV0v/NfZpjRwY/ze8fyP4hLseqhSzN2o9Q1Jv9KNeEfb7BbqIw68so/m8Ne LVXQqp4X5rqDDLV64OpXXmCX5mAecilRXKCzWxrMySkqg3XHRnnF4+9lDYkt7K9hPXPh/wF9kyO9Luo0KzABKQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/diHeAWydx6bqyJJpe0Fx5fIDCOw>
Cc: Mike Jones <Michael.Jones@microsoft.com>, "draft-ietf-oauth-amr-values.all@ietf.org" <draft-ietf-oauth-amr-values.all@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-amr-values-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 20:30:22 -0000

Jari,

On 2/1/17 2:57 PM, Jari Arkko wrote:
> Thanks for your review, Paul, and thanks for the discussion, Mike.
>
> I think there’s text in 5226bis about it being possible to ask people to post things
> to a mailing list.

I just checked rfc5226bis. As best I can tell, it has not substantially 
changed from rfc5226 wrt expert review.

IIUC, both of those documents mention that the *expert* can go to a list 
for advice, but that IANA just wants to deal with an expert.

I realize it isn't too much of a stretch for IANA to ask non-experts who 
are submitting to go to a list to find their own expert. But that 
process doesn't seem to be covered by either rfc5226 or rfc5226bis. If 
it is a practice that is desired, then perhaps it should be added to 
5226bis.

But at the end of the day this is not for me to decide - it is up to the 
IESG and IANA.

	Thanks,
	Paul

> Jari
>
> On 26 Jan 2017, at 22:05, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> On 1/26/17 3:48 PM, Mike Jones wrote:
>>> The designated experts are subscribed to the review mailing list.  Either IANA or individuals can send (or forward) requests to it.  There have been cases where IANA has directly received requests, which they have forwarded to the list for review, thereby also reaching the designated experts.  It works fine in practice and achieves the goals of RFC 5226, even if all the steps are not literally always done in the same order.
>>>
>>> The IESG has already approved this kind of procedure for .well-known URI registrations (using the wellknown-uri-review@ietf.org list, per RFC 5785), for OAuth registrations (using the oauth-ext-review@ietf.org list, per RFC 6749 and RFC 7591), for JOSE registrations (using the jose-reg-review@ietf.org list, per RFC 7515, RFC 7517, and RFC 7518) and for JWT registrations (using the jwt-reg-review@ietf.org list, per RFC 7519 and RFC 7800).  Given all this working existing practice, I don't see a sound reason for the IESG to reject using this same procedure for an additional kind of JWT registration.
>>
>> In that case the proper thing to do would be to revise RFC5226 to acknowledge this approach. But in the end, if IANA and the IESG are OK with this then so be it.
>>
>>> Please don't get me wrong - I do appreciate your detailed scrutiny of the spec bringing this up.  I think we agree that consistency matters.
>>
>> Thanks. IIUC that is the role of Gen-Art reviews.
>>
>> 	Thanks,
>> 	Paul
>>
>>> 				-- Mike
>>>
>>> -----Original Message-----
>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>> Sent: Thursday, January 26, 2017 12:28 PM
>>> To: Mike Jones <Michael.Jones@microsoft.com>; draft-ietf-oauth-amr-values.all@ietf.org
>>> Cc: General Area Review Team <gen-art@ietf.org>
>>> Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-amr-values-05
>>>
>>> Mike,
>>>
>>> On 1/26/17 2:38 PM, Mike Jones wrote:
>>>> Hi Paul,
>>>>
>>>> Per my earlier reply at https://www.ietf.org/mail-archive/web/gen-art/current/msg14212.html, the specified registration procedure is the standard IANA one, prefixed by a public review period.  JWT registrations, OAuth registrations, .well-known registrations, and others all already work this way.  It works well in practice.  Particularly since changing the registration procedure for this JWT claim would make it inconsistent with registering JWT claims, I believe that the working group would strongly oppose removing the public review period step.
>>>>
>>>> I would therefore ask that you withdraw your request to revise the registration procedure, on this basis.
>>>
>>> I'm sorry, but I can't see how what you call for is consistent with what
>>> RFC5226 says about the role of IANA with repositories controlled by expert review.
>>>
>>> That document *explicitly* says
>>>
>>>    In many cases, some review of prospective allocations is appropriate,
>>>    and the question becomes who should perform the review and what is
>>>    the purpose of the review.  One might think that an IETF working
>>>    group (WG) familiar with the namespace at hand should be consulted.
>>>    In practice, however, WGs eventually disband, so they cannot be
>>>    considered a permanent evaluator.  It is also possible for namespaces
>>>    to be created through individual submission documents, for which no
>>>    WG is ever formed.
>>> ...
>>>    While discussion on a mailing list can provide valuable technical
>>>    feedback, opinions may vary and discussions may continue for some
>>>    time without clear resolution.  In addition, IANA cannot participate
>>>    in all of these mailing lists and cannot determine if or when such
>>>    discussions reach consensus.  Therefore, IANA relies on a "designated
>>>    expert" for advice regarding the specific question of whether an
>>>    assignment should be made.  The designated expert is an individual
>>>    who is responsible for carrying out an appropriate evaluation and
>>>    returning a recommendation to IANA.
>>> ...
>>>    The designated expert is responsible for initiating and coordinating
>>>    the appropriate review of an assignment request.  The review may be
>>>    wide or narrow, depending on the situation and the judgment of the
>>>    designated expert.  This may involve consultation with a set of
>>>    technology experts, discussion on a public mailing list, consultation
>>>    with a working group (or its mailing list if the working group has
>>>    disbanded), etc.  Ideally, the designated expert follows specific
>>>    review criteria as documented with the protocol that creates or uses
>>>    the namespace.  (See the IANA Considerations sections of [RFC3748]
>>>    and [RFC3575] for examples that have been done for specific
>>>    namespaces.)
>>> ...
>>>    Designated experts are appointed by the IESG (normally upon
>>>    recommendation by the relevant Area Director).  They are typically
>>>    named at the time a document creating or updating a namespace is
>>>    approved by the IESG, but as experts originally appointed may later
>>>    become unavailable, the IESG will appoint replacements if necessary.
>>> ...
>>>    In registries where a pool of experts evaluates requests, the pool
>>>    should have a single chair responsible for defining how requests are
>>>    to be assigned to and reviewed by experts.  In some cases, the expert
>>>    pool may consist of a primary and backups, with the backups involved
>>>    only when the primary expert is unavailable.  In other cases, IANA
>>>    might assign requests to individual members in sequential or
>>>    approximate random order.  In the event that IANA finds itself having
>>>    received conflicting advice from its experts, it is the
>>>    responsibility of the pool's chair to resolve the issue and provide
>>>    IANA with clear instructions.
>>>
>>> Meanwhile, your document says:
>>>
>>>    IANA must only accept registry updates from the Designated Experts
>>>    and should direct all requests for registration to the review mailing
>>>    list.
>>>
>>> So, as I read it, the process according to 5226 would be:
>>>
>>> 1) IANA receives a request;
>>> 2) IANA asks the designated expert (or chairman of a group of experts)
>>>    to review the request;
>>> 3) expert reviews the request, possibly consulting a mailing list;
>>> 4) expert replies to IANA with approval or disapproval;
>>> 5) in the case of approval IANA updates the registry.
>>>
>>> While as I read it the process according to your document would be:
>>>
>>> 1) If IANA receives a request from a non-expert, it is to refuse it
>>>    and refer the requester to the jwt-reg-review@ietf.org mailing list;
>>> 2) the requester sends a request to the mailing list;
>>> 3) after discussion, an expert forwards the request to IANA;
>>> 4) IANA updates the registry.
>>>
>>> Hence I don't think that what you call out is consistent with expert review as defined in RFC5226.
>>>
>>> Ultimately it is up to the IESG and IANA to decide if they want to allow this variant procedure.
>>>
>>> 	Thank you,
>>> 	Paul Kyzivat
>>>
>>>
>>>> 				Thank you,
>>>> 				-- Mike
>>>>
>>>> -----Original Message-----
>>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>>> Sent: Thursday, January 26, 2017 9:51 AM
>>>> To: draft-ietf-oauth-amr-values.all@ietf.org
>>>> Cc: General Area Review Team <gen-art@ietf.org>
>>>> Subject: [Gen-art] Gen-ART Telechat review of
>>>> draft-ietf-oauth-amr-values-05
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft. For more information, please see the FAQ at <​http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Document: draft-ietf-oauth-amr-values-05
>>>> Reviewer: Paul Kyzivat
>>>> Review Date: 2017-01-26
>>>> IETF LC End Date: 2016-12-13
>>>> IESG Telechat date:2017-01-32
>>>>
>>>> Summary:
>>>>
>>>> This draft is on the right track but has open issues, described in the review.
>>>>
>>>> It is generally well written, with much better guidelines for expert reviewers than I typically see.
>>>>
>>>> Disclaimer:
>>>>
>>>> I'm not well versed in JSON Web Tokens, so I have not considered the pros/cons of having this registry or of the specific values being registered. I have focused on the mechanics of the draft.
>>>>
>>>> Issues:
>>>>
>>>> Major: 0
>>>> Minor: 1
>>>> Nits:  0
>>>>
>>>> (1) Minor:
>>>>
>>>> Section 6.1 says:
>>>>
>>>>     IANA must only accept registry updates from the Designated Experts
>>>>     and should direct all requests for registration to the review
>>>>     mailing list.
>>>>
>>>> This is inconsistent with the way IANA Expert Review works, as defined in section 3 of RFC5226. Requests go through some channel (e.g. IESG review for standards track RFCs) to the editor and then IANA actions requiring expert review are referred to a designated expert. The expert then approves or denies the request, and approved requests are acted upon by IANA.
>>>>
>>>> Direction of requests to a mailing list is not an IANA function, but could be done by the expert.
>>>>
>>>> Please revise the text and procedures to be consistent with the way Expert Review is intended to work.
>>>>
>>>> (Note: In my earlier last call review of this document I erroneously
>>>> cited RFC5526 rather than RFC5226. I have corrected that above.)
>>>>
>>>
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>


From nobody Wed Feb  1 12:57:49 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46D0F1299D8 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 12:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4Kn2ACJ_4jv for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 12:57:46 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5077129525 for <gen-art@ietf.org>; Wed,  1 Feb 2017 12:57:44 -0800 (PST)
X-AuditID: c1b4fb25-5ba3c980000036c9-c2-58924bc60e11
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by  (Symantec Mail Security) with SMTP id B9.50.14025.6CB42985; Wed,  1 Feb 2017 21:57:43 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 21:57:01 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
Thread-Index: AdJ8ysFOq+nkh2z8R/yqSz6QRbIwJQ==
Date: Wed, 1 Feb 2017 20:57:00 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BFD8F92ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM2K7uu5x70kRBlMvM1mc3DCPzeLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGzyl/2AsaQit+PljE2sD4y6OLkZNDQsBE YsfRrWxdjFwcQgLrGCUezn/NCJIQEljEKPFgo1wXIwcHm4CFRPc/bZAaEYEVjBJH218zg9QI C7hKfLvczg5iiwh4Sax6vYoZwtaTePDhCNgcFgEVif/3mlhAbF4BX4ntjy+B1TMKiEl8P7WG CcRmFhCXuPVkPhPEQQISS/acZ4awRSVePv7HCmErSTQuecIKcg+zQL7E6z9qECMFJU7OfMIy gVFwFpJJsxCqZiGpgijRkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxihanFiflphsZ66UW ZSYXF+fn6eWllmxiBMbCwS2/VXcwXn7jeIhRgINRiYfXwGBShBBrYllxZe4hRgkOZiURXmV3 oBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFes5X3w4UE0hNLUrNTUwtSi2CyTBycUg2MyjPl9k0o Dd3EvoFb7iJPgLlhj/bi+ysYwx+YSqbuU3ywZMrTLN2WT2XMRvuYZJfe233TQmvfC4fz8z3a zrfdnrDZ5+GcyXIRERbP18ldC52xo5Td9qXmRbkil8U8nl8ufGL6cWTypay/hxbP4bHc1Tfr pEPiMybZOUlr4xU/PtJ+/LtDeNa5ZUosxRmJhlrMRcWJAIyf7T2BAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zkvJ-RsKi0UwKm47bz98kdcCfMw>
Subject: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 20:57:48 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BFD8F92ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.



For more information, please see the FAQ at



<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.



Document:                                      draft-ietf-dhc-dhcpv6-failov=
er-protocol-04.txt

Reviewer:                                        Christer Holmberg

Review Date:                                  01.02.2017

IETF LC End Date:                          19.01.2017

IESG Telechat date: (if known)    02.02.2017



Summary:                                       The document is almost ready=
 for publication, but there are some editorial nits that I'd like the autho=
rs to address.



Major issues:                                 None



Minor issues:                                 None



Nits/editorial comments:



INTRODUCTION:



Q1:        In the first sentence of the Introduction, I suggest to say:



"The failover protocol defined in this document provides..."



Otherwise it's a little unclear what failover protocol you are talking abou=
t.



Q2:        In the Introduction, before the first sentence, shouldn't there =
be some background text, including some information about the problem that =
the document solves. I know there is something in the Abstract, but I think=
 there should also be something in the Introduction, before jumping into th=
e solution.



Q3:        In the Introduction, I suggest adding a reference to the first o=
ccurrences of "DHCP service" and "DHCP server".



Q4:        In the Introduction, you switch between "This protocol" and "The=
 failover protocol". Please use consistent terminology. This applies to the=
 document in general.



SECTION 4:



Q5:        In the Abstract and Introduction it is said that DHCPv6 does not=
 provide server redundancy. Then section 4 talks about failover concepts an=
d mechanism.



Are those concepts something used for DHCPv6 today, but for some reason do =
not fulfil the failover protocol requirements?



OR, are these general concepts that will be supported by implementing the f=
ailover protocol?



I think it would be good to have an introduction statement clarifying that.





--_000_7594FB04B1934943A5C02806D1A2204B4BFD8F92ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. The General Area Review Team (Gen-ART) reviews all IETF documents being p=
rocessed by the IESG for the IETF Chair.&nbsp; Please treat these comments =
just like any other last call comments.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For more information, please see the FAQ at<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"https://trac.ietf.org/trac/gen/wik=
i/GenArtfaq">https://trac.ietf.org/trac/gen/wiki/GenArtfaq</a>&gt;.<o:p></o=
:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-dhc-dhcpv6-failover-protocol-04.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date:&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; 01.02.2017<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 19.01.2017<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: (if known)&nbsp;&nbsp; &nbsp;=
02.02.2017<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The document is almost ready for publ=
ication, but there are some editorial nits that I&#8217;d like the authors =
to address.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">INTRODUCTION:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
the first sentence of the Introduction, I suggest to say:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&#8220;The failover protocol defined in this docu=
ment provides&#8230;&#8221;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Otherwise it&#8217;s a little unclear what failov=
er protocol you are talking about.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q2:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
the Introduction, before the first sentence, shouldn&#8217;t there be some =
background text, including some information about the problem that the docu=
ment solves. I know there is something in the Abstract, but I think there s=
hould
 also be something in the Introduction, before jumping into the solution.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q3:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
the Introduction, I suggest adding a reference to the first occurrences of =
&#8220;DHCP service&#8221; and &#8220;DHCP server&#8221;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q4:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
the Introduction, you switch between &#8220;This protocol&#8221; and &#8220=
;The failover protocol&#8221;. Please use consistent terminology. This appl=
ies to the document in general.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">SECTION 4:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Q5:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
the Abstract and Introduction it is said that DHCPv6 does not provide serve=
r redundancy. Then section 4 talks about failover concepts and mechanism.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Are those concepts something used for DHCPv6 toda=
y, but for some reason do not fulfil the failover protocol requirements?<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">OR, are these general concepts that will be suppo=
rted by implementing the failover protocol?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I think it would be good to have an introduction =
statement clarifying that.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BFD8F92ESESSMB209erics_--


From nobody Wed Feb  1 13:19:06 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E17B129A2A for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HA-X4uSDEx5F for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:19:03 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57D73129A24 for <gen-art@ietf.org>; Wed,  1 Feb 2017 13:19:03 -0800 (PST)
X-AuditID: c1b4fb25-5ba3c980000036c9-99-589250c5deb7
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by  (Symantec Mail Security) with SMTP id 04.82.14025.5C052985; Wed,  1 Feb 2017 22:19:01 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 22:18:37 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dnsop-edns-key-tag.all@tools.ietf.org" <draft-ietf-dnsop-edns-key-tag.all@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-dnsop-edns-key-tag-04
Thread-Index: AdJ80DqmdjN/EU+sSJeTrG7IA8tAHw==
Date: Wed, 1 Feb 2017 21:18:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFD8FEF@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BFD8FEFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+Jvje7RgEkRBtu+a1lse3qOyeLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGg63/mQp61SrO7DjA1sDYpNjFyMEhIWAi MfMkfxcjF4eQwHpGiYOtt9khnEWMEj0PTzODFLEJWEh0/9MGiYsITGGUONF+nq2LkZNDWMBa 4sr9V6wgtoiAg8TZK0vA6kUE9CQ27/MFCbMIqEjcPzwfrIRXwFfi9PffjCA2o4CYxPdTa5hA bGYBcYlbT+aD2RICAhJL9pxnhrBFJV4+/scKYStJNC55wgpRny/x4fMyqJmCEidnPmGZwCg4 C8moWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsYRYtTi5Ny042M9VKLMpOL i/Pz9PJSSzYxAqPh4JbfqjsYL79xPMQowMGoxMNrYDApQog1say4MvcQowQHs5IIr7I7UIg3 JbGyKrUoP76oNCe1+BCjNAeLkjiv2cr74UIC6YklqdmpqQWpRTBZJg5OqQbGOOkdeg35fp9D mk43puVXtb/4edr+9pfs7B1Gn2pkZRar1L5m/ij3javmc7B6NWub9qzZ5cvEmp04z06SCrOY m+oaJ8lePke9on3xkya3g7x+LN451hX/WrdX1kxrzlt4PGml4nNWf/kJep9mOumvEWTz/Xet P8d/xq4Vz6eKXwlLeNBx1EiJpTgj0VCLuag4EQCywXQMggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PXVKBm8Wled42ExlrVSa47OpoI0>
Subject: [Gen-art] Gen-ART review of draft-ietf-dnsop-edns-key-tag-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:19:05 -0000

--_000_7594FB04B1934943A5C02806D1A2204B4BFD8FEFESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>



Document:                       draft-ietf-dnsop-edns-key-tag-04.txt

Reviewer:                         Christer Holmberg

Review Date:                   1 February 2017

IETF LC End Date:           14 February 2017

IETF Telechat Date:        16 February 2017



Summary: My comments on a previous version (-03) of the document have been =
addressed, and the document is now ready for publication.

Major Issues: None



Minor Issues: None



Editorial Issues: None




--_000_7594FB04B1934943A5C02806D1A2204B4BFD8FEFESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; draft-ietf-dnsop-edns-key-tag-04.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Christer Holmberg <o:p>
</o:p></p>
<p class=3D"MsoPlainText">Review Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; 1 February 2017 <o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; 14 February 2017 <o:p></o:p></p>
<p class=3D"MsoPlainText">IETF Telechat Date: &nbsp; &nbsp; &nbsp; &nbsp;16=
 February 2017<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: My comments on a previous version (-03) =
of the document have been addressed, and the document is now ready for publ=
ication.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Major Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Editorial Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B4BFD8FEFESESSMB209erics_--


From nobody Wed Feb  1 13:35:34 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11C412958C for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxAlsDrjZvGN for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:35:30 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 460A7129590 for <gen-art@ietf.org>; Wed,  1 Feb 2017 13:35:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3218A2D299; Wed,  1 Feb 2017 23:35:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tlV7HCb8eSrj; Wed,  1 Feb 2017 23:35:28 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 723EB2CC9B; Wed,  1 Feb 2017 23:35:26 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7BF200E0-D884-47AD-BBD6-CAC4632B0577"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148500494903.32307.2573469477065261807.idtracker@ietfa.amsl.com>
Date: Wed, 1 Feb 2017 22:35:24 +0100
Message-Id: <B78C8958-5A4D-4326-99DF-11E18E9729E3@piuha.net>
References: <148500494903.32307.2573469477065261807.idtracker@ietfa.amsl.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/7F_5j8SYYnTMADIsxWRObyMQjoE>
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-softwire-dslite-multicast-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:35:33 -0000

--Apple-Mail=_7BF200E0-D884-47AD-BBD6-CAC4632B0577
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review(s) Francis!

On 21 Jan 2017, at 14:22, Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> Reviewer: Francis Dupont
> Review result: Ready
> 
> draft-ietf-softwire-dslite-multicast-14 already reviewed for Last Call
> and the few nits were addressed in newer versions.
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_7BF200E0-D884-47AD-BBD6-CAC4632B0577
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklScAAoJEM80gCTQU46qCcYP+QFkxSGUcAiI7NUtecS6i5Qw
HA3WWnLEjkUfT7xQn3oxyEeJwoQpfc8SCxxv2s0RoxMjAPVTXg3Rfbv/axLeLfFi
HfrPtcKlsy0/VxM8k6h/gOD1qM6GpXn1L5mzY7+rwTcpehItAGJ/Prb4I4tvblvH
eCEDFyij5mP5Nr9iyqcVWLWOC8daGJFwszi90PuYlQ+Y1x4xwIf+SqLS957HSVXy
YOiHGcLpvvk0+E2fNagk4EVYKZ5kVDKms2PKhZlFGBFVwSRJgi4R99jsRKs1wcmR
dWGq0c7waV+vcjo17XmeeAu7zfgbwpSvYcXc1s8ePL7OTSKhk3SfkXfEoVri/UaN
jo44tUDGJ3tW8mtDwpxWIY2tk/9MmpYsE7Cs5rcd6JDQmhKD8KJDRCg1mRHgiLPP
B8KpOZKc4Q1UH6ht8+Y0oc00/UVwd7AbSP+fO3dMEYSNtgAUwemEKjxaTIDNSMuq
pfW6ybregBOWNTNkHZ0QBqAIZ9W/mINdZRUDP4HmPPnKX//lxM5GWGPA+vak4YSt
Th4XLzjNixOMUJS63/a2ZmvBWlIUNQ6s39bMLVeMCCa9/ph0B5RiFG84VV9xTBev
mbWmHEW9p3fVdj+DjNABNNT5y62DMI1FZHCocmSoEs7AwHA5djvTv0+dMWFQBcI+
gcfzEbqo/fe3vLR8IO2E
=uBhS
-----END PGP SIGNATURE-----

--Apple-Mail=_7BF200E0-D884-47AD-BBD6-CAC4632B0577--


From nobody Wed Feb  1 13:36:37 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783E312943D for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iv6DTZ1dqB2G for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 13:36:35 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id C886A1293F0 for <gen-art@ietf.org>; Wed,  1 Feb 2017 13:36:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2B5552D299; Wed,  1 Feb 2017 23:36:34 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2QIzs6WiULe; Wed,  1 Feb 2017 23:36:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id CE2D72CC9B; Wed,  1 Feb 2017 23:36:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_9B6DE29C-C45C-4A24-84E0-F5901D08CAEB"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
Date: Wed, 1 Feb 2017 22:36:25 +0100
Message-Id: <2D095247-E389-42C9-879E-72370E89C138@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9jIUVeWlhBQcZq7kI902j7qZOZo>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:36:36 -0000

--Apple-Mail=_9B6DE29C-C45C-4A24-84E0-F5901D08CAEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for your review, Christer!

Authors, can you make a note of the editorials?

Jari

On 01 Feb 2017, at 21:57, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document:                                      =
draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
> Reviewer:                                        Christer Holmberg
> Review Date:                                  01.02.2017
> IETF LC End Date:                          19.01.2017
> IESG Telechat date: (if known)    02.02.2017
>=20
> Summary:                                       The document is almost =
ready for publication, but there are some editorial nits that I=92d like =
the authors to address.
>=20
> Major issues:                                 None
>=20
> Minor issues:                                 None
>=20
> Nits/editorial comments:
>=20
> INTRODUCTION:
>=20
> Q1:        In the first sentence of the Introduction, I suggest to =
say:
>=20
> =93The failover protocol defined in this document provides=85=94
>=20
> Otherwise it=92s a little unclear what failover protocol you are =
talking about.
>=20
> Q2:        In the Introduction, before the first sentence, shouldn=92t =
there be some background text, including some information about the =
problem that the document solves. I know there is something in the =
Abstract, but I think there should also be something in the =
Introduction, before jumping into the solution.
>=20
> Q3:        In the Introduction, I suggest adding a reference to the =
first occurrences of =93DHCP service=94 and =93DHCP server=94.
>=20
> Q4:        In the Introduction, you switch between =93This protocol=94 =
and =93The failover protocol=94. Please use consistent terminology. This =
applies to the document in general.
>=20
> SECTION 4:
>=20
> Q5:        In the Abstract and Introduction it is said that DHCPv6 =
does not provide server redundancy. Then section 4 talks about failover =
concepts and mechanism.
>=20
> Are those concepts something used for DHCPv6 today, but for some =
reason do not fulfil the failover protocol requirements?
>=20
> OR, are these general concepts that will be supported by implementing =
the failover protocol?
>=20
> I think it would be good to have an introduction statement clarifying =
that.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_9B6DE29C-C45C-4A24-84E0-F5901D08CAEB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklTZAAoJEM80gCTQU46q+4oQAJrTrX+dympiw/nv3rtxdtrV
H7nYhGEhUDCDhC5xh5avEzqTW/UmeUzc8Otl/Y8O1cZ8vAEm7Z7cAZkABrdJ2Xx9
qvbYiXkwD60bLfwUa3KmMLfvlCX8+JGcwO4x2rD2FR6ptfeCEpBhZJvRDCfd1ht7
suXrpUoLNBvuOrerOKBdB1duH5l6R+hgDmvrNSSrgWMKBWzWttWSdezAUkmK8p0b
zuavxwuuMyZy76o+GRulirWyPGM4/zRblR32WS6wx/ApjapDURBkxQyaAfhVGEn1
ufnyvl5AfnlUVE5R7aINdyR2Xis5MNPrf6Pa7t5b91IZp4dYtnHYpSq7+JnD5gnU
3Bj6KGaWryvEd5VYNCWEega0MM1HPw2UzykymtLT0mgB4XN+XtvQ+PWTeN4ksDF9
Ab5er3wdC77kU58kPGTFJYX6nQWbMjd9n1Ry6ZgFrQQrIxT87N0RCQbycO7q1mXZ
X5Pff02IQ1asf4VN1sapvV7vWFpFDevsBOZf//sdiwdpQz92MZMci8zdq/08ZnNC
lkV8GpFVJMp0EIckOfjNxluGOoSbT7FZnlVqDu4iYGFSAYC6+oqNdqfF36OP7siL
50u7MLA/jXnYaxH7hmuA89mW2KQ4jaSXgxOQan/tkckSxEnn7+jOD/AvLeVweXJ1
MifD+mnNcZiZUj7K7bkW
=/461
-----END PGP SIGNATURE-----

--Apple-Mail=_9B6DE29C-C45C-4A24-84E0-F5901D08CAEB--


From nobody Wed Feb  1 13:38:08 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B11312957E; Wed,  1 Feb 2017 13:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, TVD_SPACE_RATIO=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIL_3OM5G0lj; Wed,  1 Feb 2017 13:38:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 18B06129446; Wed,  1 Feb 2017 13:38:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 66ED82D299; Wed,  1 Feb 2017 23:37:35 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtqrGp0vHaqv; Wed,  1 Feb 2017 23:37:35 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 71F5E2CC9B; Wed,  1 Feb 2017 23:37:34 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148567501912.18000.17622999056704343003.idtracker@ietfa.amsl.com>
Date: Wed, 1 Feb 2017 22:37:31 +0100
Message-Id: <BFC2E000-BF81-4029-ABD0-748EFCFA789E@piuha.net>
References: <148567501912.18000.17622999056704343003.idtracker@ietfa.amsl.com>
To: Roni Even <roni.even@mail01.huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/xzlbimABpfMKeh39Z-J5fGKYqAU>
Cc: softwires@ietf.org, gen-art@ietf.org, ietf@ietf.org, draft-ietf-softwire-multicast-prefix-option.all@ietf.org
Subject: Re: [Gen-art] [Softwires] Review of draft-ietf-softwire-multicast-prefix-option-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:38:07 -0000

--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks!

Jari


--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklUbAAoJEM80gCTQU46qyxkQAJaGUF11NdmDCY7VO184trEg
ny44h4w9sVSkqj7Az63K89Ke5KmR3iIFJ/b0wNcgQqQ3qOtUNjZMKMl7h11WtW1i
0ef0ENUsycc7jfmYfCctAtcXA74Fp+VTufNWE1p6SZ3nodGTTXOAnMi0bt4Y5XhQ
N4e85H6PMPlgvtTRVSKfsspQsuDV6w4qex3cdv4sbAGMgRbpYxCpzAdk7Riv0Psp
GVsfyJw/loM+bKHPBhfEluu7EAQG0wfTAyh/iHj0j+9imLyV4ArXe8AGeb/CvM51
4xMKUJ/9b9XFD7CNlU/tzcUiWJh34tVfRvZzw4KC2fcDAS0l4FyNONZpZnkj5QF4
oLCXKZaooR7zg/QRrHMFgCsOKjWXfAsg0KUnMh62edDGVhYZ5J6sVqnxLEbfcK7o
Imudwaii8r5KMBnuCzXRB8xFaKefeLEFx8MpMLMQY6cUpeVj1HswQairWUtZPAvI
KujlX67Hnrl3OMMz5XHwUy4WEUHEeq5y1rE3t73wA5AfFuRhsT0TRaJXY7Jog3/J
D2wS8SddJwWL1d3CaslDSMRVvatNSmXnVDWUlQHSilGEx47D1zfgaq1wtBuNt9Rf
Ecfmq+p4MAswZKW3Y6MihUNHkvcHID/ldEClezdK1kr1DgMevwyQ2fbnRNVzKZm/
sScz9Q9ebkDrpFBulIi5
=Mv3/
-----END PGP SIGNATURE-----

--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155--


From nobody Wed Feb  1 13:38:29 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 049CE129587; Wed,  1 Feb 2017 13:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iUi99vWV_ann; Wed,  1 Feb 2017 13:38:27 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3401293F0; Wed,  1 Feb 2017 13:38:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D70802D299; Wed,  1 Feb 2017 23:38:20 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAsJj3BkdcWn; Wed,  1 Feb 2017 23:38:20 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C30552CC9B; Wed,  1 Feb 2017 23:38:19 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3ACC8A36-E135-43DB-835D-27D75C666387"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148554481599.17958.3587723480023793936.idtracker@ietfa.amsl.com>
Date: Wed, 1 Feb 2017 22:38:19 +0100
Message-Id: <F3DF1332-1739-4060-877F-CFCC637EC22F@piuha.net>
References: <148554481599.17958.3587723480023793936.idtracker@ietfa.amsl.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/2WuoMbhHokJmj_vBY2n1doJxUWE>
Cc: draft-ietf-payload-melpe.all@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-payload-melpe-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:38:29 -0000

--Apple-Mail=_3ACC8A36-E135-43DB-835D-27D75C666387
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks!

On 27 Jan 2017, at 20:20, Brian Carpenter <brian.e.carpenter@gmail.com> =
wrote:

> Reviewer: Brian Carpenter
> Review result: Ready
>=20
> Gen-ART telechat review of draft-ietf-payload-melpe-05
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-payload-melpe-05.txt
> Reviewer: Brian Carpenter
> Review Date: 2017-01-27
> IETF LC End Date: 2017-01-13
> IESG Telechat date: 2017-02-02
>=20
> Summary: Ready
> --------
>=20
> Comment:
> --------
>=20
> Thanks for handling my Last Call comments.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_3ACC8A36-E135-43DB-835D-27D75C666387
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklVLAAoJEM80gCTQU46qeTUQAJ0M1VqKhqOMyhMMpii0fC3c
FmK3Ai3szIlpYnhEL0IouhhY03eHNNDRZuvq6MU6QO7N9znmFcfo1kw5j8W7TxTZ
84/BL0qCBjRhHtUdRJx1HbwLNUnBF+y67xJ8Rk/gP4BcqUEvNxTZM9EPUp/saFkP
6BIDP1TS/zD7Uhn+4Tip7SwIT//yZdoHL2Urc1wTHZ6tC2SqpPVUS8gpKO2OiIz/
t/EQO9acjJ7Mzk0ROhFWDdl97KSWd+Mii3xzjucrv79kxxKr7d5LKv1X4yRjVJIc
FymIGwTqkYutYIMmqrdnEd7XO9F3BD0ZrfIcAtYgQA476/VH6h5TrxlP4YA7Zse3
QQl8fyG5tsSRLvNsTvuuQn8D1SNIypmhqzUPEatAGwZnbzmRwF7re5dQUKFRf87i
pEnhyaogWvlcsOCYRcbZ1VnnAllESNVySBs5PXd/Co76S1USr3bPCkRwP8h2ulrn
1N0+LZ1IsKRwgN3o5xpz+j3m22OEir4siiGKARHgqEL40C6eHFwUvWOd7coXh+3g
Z5lDuqM/23GQIh823S1rLw0M+U0YWpcgNH6i65MR8B6A3PJp7SFkkMdqyrOlo3pa
iEBA4BFAxPyxupK2MOil17qJSUm2E9LS3tLDkv8oyhUIC7oiVvPLc6chRE8cJOIe
bDuLdWDI9D27KHbIqIy8
=kiII
-----END PGP SIGNATURE-----

--Apple-Mail=_3ACC8A36-E135-43DB-835D-27D75C666387--


From nobody Wed Feb  1 13:42:53 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D8B129A64; Wed,  1 Feb 2017 13:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lGCh0irRjyjK; Wed,  1 Feb 2017 13:42:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 03DD11295DC; Wed,  1 Feb 2017 13:42:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 56AC32D299; Wed,  1 Feb 2017 23:42:33 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmnQlkihM_DQ; Wed,  1 Feb 2017 23:42:32 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7D5642CC9B; Wed,  1 Feb 2017 23:42:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20161225182404.GN8460@kduck.kaduk.org>
Date: Wed, 1 Feb 2017 22:42:32 +0100
Message-Id: <98EA1299-05B2-4AE2-A3AE-B88544CA4AE5@piuha.net>
References: <148243567232.26011.10783984451734200377.idtracker@ietfa.amsl.com> <20161225182404.GN8460@kduck.kaduk.org>
To: Benjamin Kaduk <kaduk@MIT.EDU>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/i2Bcd_VixD4NvIJhs_9O6EYdUsE>
Cc: kitten@ietf.org, gen-art@ietf.org, draft-ietf-kitten-krb-auth-indicator.all@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-kitten-krb-auth-indicator-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:42:48 -0000

--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Many thanks for the review, Robert. These reviews are much appreciated,
and at least from my perspective, improve the quality of the RFCs. Happy
to hear from Benjamin that he=92s considering the editorial issues =
Robert
found in this case.

Jari


--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklZIAAoJEM80gCTQU46qGYsP/R6Iut6xUmWprcpZlSx8AoJ+
7MoZaw510bodje5COhRoFSH0dkqNlV0XE/LWlGytHx44TJlFxIWgasXo/hCvhQSr
KG4NS3Wi/ue12EkZPd5yDOw46oyHiKJ57c6ug/lkbcEDFKVG5B3tSIfJaKEwogDR
bByE+MMxriAf8wLSnJiS67eOJowoOSpVktzRQFPBLc08gG3Bep1uYFAqYY2x42PV
xmPmaV8OgaE+FGq3JLLDHcfL0IzkAKz3pJjiR05rXfV6onRGDhk9MDzbcg0kJyAM
SO5IcjLZDzkS37mL7aK370I5JRbrExng1+4muTMb+4rcn7fmGEDeNwcIWlwkwVjU
y9OV5luFfo00/H+oNEUo/iIrCtvv4PTbdbPXOsFEHG4UNAn+4FC3zir/IVKHviGo
9r1G++sA4Yd1AMVoYqtl8I0/ThsCQerpchyMf+ryCJLMMFviHTgaEyvX24QTzzwN
k9jUgVZ3dB+mV09nDBfHxKRskJ/P81PCWtQxJuYUEjjDlKfTQBndX200CpxSzz72
wFxQ9ypdNcmP1USuFaydbWXt40fleYtTMeLu2/fdsgkP9N1wZXrjaUF99SWghbzU
LOsrkXsf68puoGx9C+kqNdN/enuUAF4zCE/P0QZlbn3RzvLa/65NZ2x6/WpS7V1J
+V/O12NZQBr3nWZQOHJ5
=Sjy0
-----END PGP SIGNATURE-----

--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684--


From nobody Wed Feb  1 13:46:50 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EDC712957E; Wed,  1 Feb 2017 13:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhfR941azJBF; Wed,  1 Feb 2017 13:46:34 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 960591295AA; Wed,  1 Feb 2017 13:46:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 065242D299; Wed,  1 Feb 2017 23:46:28 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpgY86z-195W; Wed,  1 Feb 2017 23:46:27 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 14B8A2CC9B; Wed,  1 Feb 2017 23:46:27 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFC08AC@ESESSMB209.ericsson.se>
Date: Wed, 1 Feb 2017 22:46:25 +0100
Message-Id: <80FA28DD-1CEE-44B0-B14C-AA991B5AB4CE@piuha.net>
References: <s9ubcupjutekv1baydfw2bpi.1485353373053@email.android.com> <7594FB04B1934943A5C02806D1A2204B4BFC08AC@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aWyias67w1J_PO80lV66_ZfH0Js>
Cc: "draft-ietf-mmusic-4572-update.all@ietf.org" <draft-ietf-mmusic-4572-update.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-4572-update-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:46:40 -0000

--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Elwyn, Christer =97 many thanks for the in-depth review and updates.

I have posted a =93no objection=94 position for this document for =
tomorrow=92s
IESG telechat.

Jari


--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYklcxAAoJEM80gCTQU46qCecQAKTTljd03QyNy67KotiAfIvD
yyaAnNThfefM4/XhMpxXvYrHPEcHwBVJ87mWPOr0RAiIqAYJEhCgNyH1MXGT1Bkw
LZ+2m4xrxoX2U0e1WliLdCJIRgev5i/YIefJ3Q7XnESZfqSgUzzZhyLtTCoqPjf8
19YNuc+/0c/RqeOna8kPyGXB1+HkS/zF2v8or211eQUwuoqHBK9IYji2w3ZvRl1B
QeKLvmUmOUecvYtzZK4i1M6FHsj7atsKBfa3+JTgfjBXwqnFr84bKl9IimhGXKVr
yCzDhAb+qJwUhRAQC2v4fuVGsfazfL83eJ0ajBj3MLWv3WjNzIkenZWmUoVIxKP8
Osc0HAu5K2/uuzwFxibTuAeV/D+9BBIbQ3OrUimowp1i645cFusOwJNNgsTixAAf
EuywN1QeBh6MHr8xbwUZ69lL7uJ2LDSB0+pCB5HDDyp84UK0TkYq8qHx3PUT4g2W
QbQ1DZgT2IHj1nBPwHbyxdWeoneyBY60l/YLveGUHSvvJIK2kyAxKorvupbHEXAT
mEDBmg+uSIpjjuL5J+sCv3xUU++9IuDOU010w4UmMsVyg2ka+WYeb2JD+BPLBWrQ
bAY6noNNn05Zl4APYG64lPiHbrwA6ZPrWZMRtV5HPsMFdhilJkJZdCEnjQLNav+M
YbfKInfJ2sSJwWDi5W8s
=jIAc
-----END PGP SIGNATURE-----

--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052--


From nobody Wed Feb  1 14:41:27 2017
Return-Path: <kkinnear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC7A1295CB for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level: 
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yml5y1OFHuln for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:41:25 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 156D912953B for <gen-art@ietf.org>; Wed,  1 Feb 2017 14:41:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4768; q=dns/txt; s=iport; t=1485988884; x=1487198484; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=bbfAN/qYEkkHPK1uOGrZdkq088k174735XqZVxgCTqA=; b=XRZTzoZf/sJqeV2+rUen/I0PIXluPsD8Zv29SYpsVyh3MJYsluDUErLy gdyFjYsk4/OpLUvOXUgLo2t5WaDaWgPF90bAiwkUsJtMC3NNTlv+kGQQi 6NOv51WjexCnTg9Iaw1JkXnJ7Cbo1gf/VBMvfXL5sLGUK2hAtPfS9REZJ 8=;
X-IronPort-AV: E=Sophos;i="5.33,322,1477958400"; d="scan'208";a="201320222"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Feb 2017 22:41:24 +0000
Received: from bxb-kkinnear-8814.cisco.com (bxb-kkinnear-8814.cisco.com [10.98.10.245]) (authenticated bits=0) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v11MfNZJ015833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 22:41:24 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: kkinnear <kkinnear@cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
Date: Wed, 1 Feb 2017 17:41:23 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-Authenticated-User: kkinnear@cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aLSrlBN3H4yT-HwWL9uio2CiTMM>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 22:41:26 -0000

Christer,

Thanks for your review.

I will make all of the changes that you suggest, and have offered
details (indented) below.  Note that while I'm willing to make the
change you have discussed in Q3, I don't actually understand what you
would like us to do.

More below...


> On Feb 1, 2017, at 3:57 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
> =20
> For more information, please see the FAQ at
> =20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> =20
> Document:                                      =
draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
> Reviewer:                                        Christer Holmberg
> Review Date:                                  01.02.2017
> IETF LC End Date:                          19.01.2017
> IESG Telechat date: (if known)    02.02.2017
> =20
> Summary:                                       The document is almost =
ready for publication, but there are some editorial nits that I=E2=80=99d =
like the authors to address.
> =20
> Major issues:                                 None
> =20
> Minor issues:                                 None
> =20
> Nits/editorial comments:=20
> =20
> INTRODUCTION:
> =20
> Q1:        In the first sentence of the Introduction, I suggest to =
say:
> =20
> =E2=80=9CThe failover protocol defined in this document provides=E2=80=A6=
=E2=80=9D
> =20
> Otherwise it=E2=80=99s a little unclear what failover protocol you are =
talking about.

	Sure, good idea.  See Q2, immediately below.
> =20
> Q2:        In the Introduction, before the first sentence, shouldn=E2=80=
=99t there be some background text, including some information about the =
problem that the document solves. I know there is something in the =
Abstract, but I think there should also be something in the =
Introduction, before jumping into the solution.

	I've been chastised for repeating the abstract in the
	introduction, so I was trying to not do that.  How about we
	start the introduction with:


	"The DHCPv6 protocol [RFC3315] does not provide for server
	redundancy.  The failover protocol defined in this document
	provides a means for cooperating DHCP servers to work together
	to provide a DHCP service with availability that is increased
	beyond that which could be provided by a single DHCP server
	operating alone. ..."


	Note that the last sentence of the Introduction already points
	to the DHCPv6 failover requirements RFC, which has a lot more
	to say about this.

> =20
> Q3:        In the Introduction, I suggest adding a reference to the =
first occurrences of =E2=80=9CDHCP service=E2=80=9D and =E2=80=9CDHCP =
server=E2=80=9D.


	While I'm more than happy to do this, I don't actually know
	what you would like me to reference?  We haven't defined
	either "DHCP service" or "DHCP server" in the glossary since
	we felt they were reasonably apparent from the context of this
	document.  Are you thinking that we should reference RFC3315
	on the first occurrence of "DHCP service" and "DHCP server"?

> =20
> Q4:        In the Introduction, you switch between =E2=80=9CThis =
protocol=E2=80=9D and =E2=80=9CThe failover protocol=E2=80=9D. Please =
use consistent terminology. This applies to the document in general.

	Ok, we'll go with "The failover protocol" since it appears=20
	more times so far.  I will make this global change when I
	next update the document. =20
> =20
> SECTION 4:
> =20
> Q5:        In the Abstract and Introduction it is said that DHCPv6 =
does not provide server redundancy. Then section 4 talks about failover =
concepts and mechanism.
> =20
> Are those concepts something used for DHCPv6 today, but for some =
reason do not fulfil the failover protocol requirements?
> =20
> OR, are these general concepts that will be supported by implementing =
the failover protocol?
> =20
> I think it would be good to have an introduction statement clarifying =
that.


	The concepts and mechanisms discussed in Section 4 relate to
	the failover protocol, they aren't present in the regular
	RFC3315(et. al.) DHCPv6 protocol.  I will add the following to
	Section 4 to clarify that:

	"4.  Failover Concepts and Mechanisms

	The following concepts and mechanisms are necessary to the =
operation
	of the failover protocol, and they are not currently employed by
	the DHCPv6 protocol [RFC3315].

	4.1. Required Server Configuration

	..."

Again, thanks for the review.

Kim






From nobody Wed Feb  1 14:43:20 2017
Return-Path: <kkinnear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F57129636 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level: 
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDqyk16iDy81 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:43:15 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B04F41299DA for <gen-art@ietf.org>; Wed,  1 Feb 2017 14:43:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3102; q=dns/txt; s=iport; t=1485988995; x=1487198595; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=i9zj2hT3wdeIdqV+T7wuClNJlhOxhHV4yJwzflCGYIQ=; b=E0K8c6y1PbKX5SwcylnxYx+utk3nh+num48CJPWttCAg1k57RiBNlCsg /lRYMXySZLwz8kLUTWz3/I3luMO8542lqMLdSIDAryTMN0HNhNNS75dLk LyWvKWb6LHVAg+R+zMZAWeUeiMznwKPhNq56muTGFhggWrjQGK7f0Rz14 8=;
X-IronPort-AV: E=Sophos;i="5.33,322,1477958400"; d="scan'208";a="379506561"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2017 22:43:15 +0000
Received: from bxb-kkinnear-8814.cisco.com (bxb-kkinnear-8814.cisco.com [10.98.10.245]) (authenticated bits=0) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v11MhD56020368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 22:43:14 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: kkinnear <kkinnear@cisco.com>
In-Reply-To: <2D095247-E389-42C9-879E-72370E89C138@piuha.net>
Date: Wed, 1 Feb 2017 17:43:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE0F8FC1-365D-4D1F-B065-734D92693D11@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <2D095247-E389-42C9-879E-72370E89C138@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3124)
X-Authenticated-User: kkinnear@cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/3moitIdWqSwbDAMLUe1SRMT4Ndg>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 22:43:17 -0000

> On Feb 1, 2017, at 4:36 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> Thanks for your review, Christer!
>=20
> Authors, can you make a note of the editorials?

	Yes, I have agreed to make all of the changes
	suggested by Christer.=20

	Thanks -- Kim
>=20
> Jari
>=20
> On 01 Feb 2017, at 21:57, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
>>=20
>> For more information, please see the FAQ at
>>=20
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>=20
>> Document:                                      =
draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
>> Reviewer:                                        Christer Holmberg
>> Review Date:                                  01.02.2017
>> IETF LC End Date:                          19.01.2017
>> IESG Telechat date: (if known)    02.02.2017
>>=20
>> Summary:                                       The document is almost =
ready for publication, but there are some editorial nits that I=92d like =
the authors to address.
>>=20
>> Major issues:                                 None
>>=20
>> Minor issues:                                 None
>>=20
>> Nits/editorial comments:
>>=20
>> INTRODUCTION:
>>=20
>> Q1:        In the first sentence of the Introduction, I suggest to =
say:
>>=20
>> =93The failover protocol defined in this document provides=85=94
>>=20
>> Otherwise it=92s a little unclear what failover protocol you are =
talking about.
>>=20
>> Q2:        In the Introduction, before the first sentence, shouldn=92t =
there be some background text, including some information about the =
problem that the document solves. I know there is something in the =
Abstract, but I think there should also be something in the =
Introduction, before jumping into the solution.
>>=20
>> Q3:        In the Introduction, I suggest adding a reference to the =
first occurrences of =93DHCP service=94 and =93DHCP server=94.
>>=20
>> Q4:        In the Introduction, you switch between =93This protocol=94 =
and =93The failover protocol=94. Please use consistent terminology. This =
applies to the document in general.
>>=20
>> SECTION 4:
>>=20
>> Q5:        In the Abstract and Introduction it is said that DHCPv6 =
does not provide server redundancy. Then section 4 talks about failover =
concepts and mechanism.
>>=20
>> Are those concepts something used for DHCPv6 today, but for some =
reason do not fulfil the failover protocol requirements?
>>=20
>> OR, are these general concepts that will be supported by implementing =
the failover protocol?
>>=20
>> I think it would be good to have an introduction statement clarifying =
that.
>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20


From nobody Wed Feb  1 14:45:16 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B801129A47 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cdp49bZ77aWQ for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:45:13 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EF3E12960D for <gen-art@ietf.org>; Wed,  1 Feb 2017 14:45:13 -0800 (PST)
X-AuditID: c618062d-e8e5698000007359-c0-58926c38d62a
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id E4.2C.29529.83C62985; Thu,  2 Feb 2017 00:16:09 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 17:45:09 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: kkinnear <kkinnear@cisco.com>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
Thread-Index: AQHSfNNHF9ajYNTtAEGi4C4M3ASMNaFVE06AgAAAigA=
Date: Wed, 1 Feb 2017 22:45:09 +0000
Message-ID: <29857F91-007A-49A6-A7D9-808E66A1AA41@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <2D095247-E389-42C9-879E-72370E89C138@piuha.net> <CE0F8FC1-365D-4D1F-B065-734D92693D11@cisco.com>
In-Reply-To: <CE0F8FC1-365D-4D1F-B065-734D92693D11@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_1B9D0513-C136-4A95-B30E-81BEDE90C6F1"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsUyuXRPuK5lzqQIgx03+S1ObpjHZnH11WcW ixn7VrBZbGv4zOTA4jHl90ZWjyVLfjJ5bF0ync3jy+XPbAEsUVw2Kak5mWWpRfp2CVwZZ1ae Zix47VmxY1cXWwPjXccuRg4OCQETia9vHboYuTiEBNYzSuw5d48FwlnGKPFyzgnGLkZODjag og07PzOB2CICihJ/f99nByliFrjLKDFvxSIWkISwQKjE9vuP2CCKwiQWzJ/LDGFbSZz+9gms hkVAReJ4wy2wOK+AvcTG6/1gtpDAZkaJZy8qQGxOAVuJXZ/7wOoZBcQkvp9aA7aYWUBc4taT +WC2hICIxMOLp9kgbFGJl4//sULYShJzXl9jhjhuCqPEzpudUMsEJU7OfMIygVFkFpJZs5DV zUJSB1GkLbFs4WtmCFtTYn/3cqi4qcTrox8ZIWxriRm/DrJB2IoSU7ofsi9g5FjFyFFaXJCT m25ksIkRGIPHJNh0dzDen+55iFGAg1GJh9fAYFKEEGtiWXFl7iFGFaDWRxtWX2CUYsnLz0tV EuEtSAZK86YkVlalFuXHF5XmpBYfYpTmYFES541bfT9cSCA9sSQ1OzW1ILUIJsvEwSnVwNhz wfGgn8Pz4D98TRf0dkoIdQs90Jo1577jlOe969UEtYN5o4/bmuf1puhY1gra3dCLnrpSJYtt k91mB4NrjxZPePFi193X0z1z34bOVWfY5rTyhps7X2r8ZaUj226rq+XPiox7Xpga5vKrz19g u8/3hlcTlNuvN/0t2xn/msEt5GdwQJDlPCWW4oxEQy3mouJEADQ2rinJAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dsKS8VGoZIKIDjtm7YNZlb02QY0>
Cc: "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>, Gen art <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 22:45:15 -0000

--Apple-Mail=_1B9D0513-C136-4A95-B30E-81BEDE90C6F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks for the review Christer. And thanks for taking care of this =
quickly Kim.

Regards
Suresh

> On Feb 1, 2017, at 11:43 PM, kkinnear <kkinnear@cisco.com> wrote:
>=20
>=20
>> On Feb 1, 2017, at 4:36 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>>=20
>> Thanks for your review, Christer!
>>=20
>> Authors, can you make a note of the editorials?
>=20
> 	Yes, I have agreed to make all of the changes
> 	suggested by Christer.=20
>=20
> 	Thanks -- Kim
>>=20
>> Jari
>>=20
>> On 01 Feb 2017, at 21:57, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>>=20
>>> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
>>>=20
>>> For more information, please see the FAQ at
>>>=20
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>=20
>>> Document:                                      =
draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
>>> Reviewer:                                        Christer Holmberg
>>> Review Date:                                  01.02.2017
>>> IETF LC End Date:                          19.01.2017
>>> IESG Telechat date: (if known)    02.02.2017
>>>=20
>>> Summary:                                       The document is =
almost ready for publication, but there are some editorial nits that =
I=E2=80=99d like the authors to address.
>>>=20
>>> Major issues:                                 None
>>>=20
>>> Minor issues:                                 None
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> INTRODUCTION:
>>>=20
>>> Q1:        In the first sentence of the Introduction, I suggest to =
say:
>>>=20
>>> =E2=80=9CThe failover protocol defined in this document =
provides=E2=80=A6=E2=80=9D
>>>=20
>>> Otherwise it=E2=80=99s a little unclear what failover protocol you =
are talking about.
>>>=20
>>> Q2:        In the Introduction, before the first sentence, =
shouldn=E2=80=99t there be some background text, including some =
information about the problem that the document solves. I know there is =
something in the Abstract, but I think there should also be something in =
the Introduction, before jumping into the solution.
>>>=20
>>> Q3:        In the Introduction, I suggest adding a reference to the =
first occurrences of =E2=80=9CDHCP service=E2=80=9D and =E2=80=9CDHCP =
server=E2=80=9D.
>>>=20
>>> Q4:        In the Introduction, you switch between =E2=80=9CThis =
protocol=E2=80=9D and =E2=80=9CThe failover protocol=E2=80=9D. Please =
use consistent terminology. This applies to the document in general.
>>>=20
>>> SECTION 4:
>>>=20
>>> Q5:        In the Abstract and Introduction it is said that DHCPv6 =
does not provide server redundancy. Then section 4 talks about failover =
concepts and mechanism.
>>>=20
>>> Are those concepts something used for DHCPv6 today, but for some =
reason do not fulfil the failover protocol requirements?
>>>=20
>>> OR, are these general concepts that will be supported by =
implementing the failover protocol?
>>>=20
>>> I think it would be good to have an introduction statement =
clarifying that.
>>>=20
>>>=20
>>> _______________________________________________
>>> Gen-art mailing list
>>> Gen-art@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gen-art
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_1B9D0513-C136-4A95-B30E-81BEDE90C6F1
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjAxMjI0NTA5WjAjBgkqhkiG9w0B
CQQxFgQUzio2snAz/8CYX/LlsBHRMOxAYOEwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBz7EZAVK0miOOKE1+zMPaQubeeaHny8sOo7ililWibDF5AdYEx6dTF8scF5T0i
a3Wy6/lhhKBbpF55qSLjI8cFs6jlpkCRrFOVA0wrPGqBHfR4EdcKv+zIzNqT8cp+GXZxuuFTV6GH
2ojLzFrQVOJtCfUj6x6LggH2MEPnfwxsLKq0I/BTFaLOiAFo4HMyAuLXLdm9vCEN3w2o4SCuVbQz
egHFe3pS504usM73m6D2Seu/WwskwsHonuMIyjmXqNXdUbxZWfOPU72JoN/vjSEJC5KucutlaUtn
XjP8JnUHtHGPCTdaBjc26ksNml6/3z9QmkPx/HW6lB2Q1ru2ClFOAAAAAAAA

--Apple-Mail=_1B9D0513-C136-4A95-B30E-81BEDE90C6F1--


From nobody Wed Feb  1 14:58:17 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD9C1295EB for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cB26_S1zSeyK for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 14:58:14 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5920D129577 for <gen-art@ietf.org>; Wed,  1 Feb 2017 14:58:14 -0800 (PST)
X-AuditID: c1b4fb3a-12eaf98000004068-1e-58926804c0f9
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by  (Symantec Mail Security) with SMTP id 1E.9B.16488.40862985; Wed,  1 Feb 2017 23:58:12 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0319.002; Wed, 1 Feb 2017 23:57:39 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: kkinnear <kkinnear@cisco.com>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
Thread-Index: AdJ8ysFOq+nkh2z8R/yqSz6QRbIwJQACS1KAAAJnoyA=
Date: Wed, 1 Feb 2017 22:57:39 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com>
In-Reply-To: <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGbE9SpclY1KEwfwXqhYnN8xjs7j66jOL xbaGz0wOzB5Tfm9k9Viy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mtqm3WQpaNCo+P58IlsD 4x+1LkZODgkBE4mVTX3MILaQwDpGiRut/l2MXED2IkaJU7N7mLoYOTjYBCwkuv9pg9SICChK /P19nx2khllgBaPEsa0P2UESwgKeEus63zNBFHlJrHq9ihnCtpKYumg+mM0ioCJx8f0kRhCb V8BX4nLXNGaIZQ2MEmtadoM1cwrYSmze3QBWxCggJvH91BqwOLOAuMStJ/OZIK4WkFiy5zwz hC0q8fLxP1YIW0li0e3PYEczC2hKrN+lD9GqKDGlG+JOXgFBiZMzn7BMYBSdhWTqLISOWUg6 ZiHpWMDIsopRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMHIObvlttYPx4HPHQ4wCHIxKPLwG BpMihFgTy4orcw8xSnAwK4nwFiQDhXhTEiurUovy44tKc1KLDzFKc7AoifOarbwfLiSQnliS mp2aWpBaBJNl4uCUamBsbUmYdODEDI7vUVxWV1aHfpQ0YtpVXPFzAotWWYKwm+fr8pzMS9sk mtJrltw6cXyiUgGbvbn9frGl07K3uJ2bENsg+W2m+7+SNJlYPeblhnPY04tyP6ndOLPk++ng 870pDjM/7juxWju8YN7aJBULZ2bLI/PXb5xhvFy+RXWeweY3nBUsM34osRRnJBpqMRcVJwIA CgrzC5gCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Lz1pZfn0Rji297hcwdJL01Z3IGk>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 22:58:15 -0000

SGksDQoNCj5JIHdpbGwgbWFrZSBhbGwgb2YgdGhlIGNoYW5nZXMgdGhhdCB5b3Ugc3VnZ2VzdCwg
YW5kIGhhdmUgb2ZmZXJlZCBkZXRhaWxzIChpbmRlbnRlZCkgYmVsb3cuICBOb3RlIHRoYXQgd2hp
bGUgSSdtIHdpbGxpbmcgdG8gbWFrZSB0aGUgY2hhbmdlIHlvdSBoYXZlIGRpc2N1c3NlZCBpbiBR
MywgSSBkb24ndCA+YWN0dWFsbHkgdW5kZXJzdGFuZCB3aGF0IHlvdSB3b3VsZCBsaWtlIHVzIHRv
IGRvLg0KPg0KPk1vcmUgYmVsb3cuLi4NCg0KSU5UUk9EVUNUSU9OOg0KICANCj4+IFExOiAgICAg
ICAgSW4gdGhlIGZpcnN0IHNlbnRlbmNlIG9mIHRoZSBJbnRyb2R1Y3Rpb24sIEkgc3VnZ2VzdCB0
byBzYXk6DQo+PiAgDQo+PiDigJxUaGUgZmFpbG92ZXIgcHJvdG9jb2wgZGVmaW5lZCBpbiB0aGlz
IGRvY3VtZW50IHByb3ZpZGVz4oCm4oCdDQo+PiAgDQo+PiBPdGhlcndpc2UgaXTigJlzIGEgbGl0
dGxlIHVuY2xlYXIgd2hhdCBmYWlsb3ZlciBwcm90b2NvbCB5b3UgYXJlIHRhbGtpbmcgYWJvdXQu
DQo+DQo+CVN1cmUsIGdvb2QgaWRlYS4gIFNlZSBRMiwgaW1tZWRpYXRlbHkgYmVsb3cuDQo+ICAN
Cj4+IFEyOiAgICAgICAgSW4gdGhlIEludHJvZHVjdGlvbiwgYmVmb3JlIHRoZSBmaXJzdCBzZW50
ZW5jZSwgc2hvdWxkbuKAmXQgdGhlcmUgYmUgc29tZSBiYWNrZ3JvdW5kIHRleHQsIGluY2x1ZGlu
ZyBzb21lIGluZm9ybWF0aW9uIA0KPj5hYm91dCB0aGUgcHJvYmxlbSB0aGF0IHRoZSBkb2N1bWVu
dCBzb2x2ZXMuIEkga25vdyB0aGVyZSBpcyBzb21ldGhpbmcgaW4gdGhlIEFic3RyYWN0LCBidXQg
SSB0aGluayB0aGVyZSBzaG91bGQgYWxzbyBiZSBzb21ldGhpbmcgDQo+PmluIHRoZSBJbnRyb2R1
Y3Rpb24sIGJlZm9yZSBqdW1waW5nIGludG8gdGhlIHNvbHV0aW9uLg0KPg0KPglJJ3ZlIGJlZW4g
Y2hhc3Rpc2VkIGZvciByZXBlYXRpbmcgdGhlIGFic3RyYWN0IGluIHRoZQ0KPglpbnRyb2R1Y3Rp
b24sIHNvIEkgd2FzIHRyeWluZyB0byBub3QgZG8gdGhhdC4gIEhvdyBhYm91dCB3ZQ0KPglzdGFy
dCB0aGUgaW50cm9kdWN0aW9uIHdpdGg6DQo+DQo+CSJUaGUgREhDUHY2IHByb3RvY29sIFtSRkMz
MzE1XSBkb2VzIG5vdCBwcm92aWRlIGZvciBzZXJ2ZXINCj4JcmVkdW5kYW5jeS4gIFRoZSBmYWls
b3ZlciBwcm90b2NvbCBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQNCj4JcHJvdmlkZXMgYSBtZWFu
cyBmb3IgY29vcGVyYXRpbmcgREhDUCBzZXJ2ZXJzIHRvIHdvcmsgdG9nZXRoZXINCj4JdG8gcHJv
dmlkZSBhIERIQ1Agc2VydmljZSB3aXRoIGF2YWlsYWJpbGl0eSB0aGF0IGlzIGluY3JlYXNlZA0K
PgliZXlvbmQgdGhhdCB3aGljaCBjb3VsZCBiZSBwcm92aWRlZCBieSBhIHNpbmdsZSBESENQIHNl
cnZlcg0KPglvcGVyYXRpbmcgYWxvbmUuIC4uLiINCg0KTG9va3MgdmVyeSBnb29kLg0KDQpJIGtu
b3cgc29tZSBwZW9wbGUgZG9uJ3Qgd2FudCB0byByZXBlYXQgQWJzdHJhY3QgdGV4dCBpbiB0aGUg
SW50cm9kdWN0aW9uLCBidXQgSSBzdGlsbCB0aGluayB0aGUgSW50cm9kdWN0aW9uIHNob3VsZCBw
cm92aWRlIGFuIGludHJvZHVjdGlvbiB0byB0aGUgcHJvYmxlbSA6KQ0KDQo+CU5vdGUgdGhhdCB0
aGUgbGFzdCBzZW50ZW5jZSBvZiB0aGUgSW50cm9kdWN0aW9uIGFscmVhZHkgcG9pbnRzDQo+CXRv
IHRoZSBESENQdjYgZmFpbG92ZXIgcmVxdWlyZW1lbnRzIFJGQywgd2hpY2ggaGFzIGEgbG90IG1v
cmUNCj4JdG8gc2F5IGFib3V0IHRoaXMuDQo+ICANCj4+IFEzOiAgICAgICAgSW4gdGhlIEludHJv
ZHVjdGlvbiwgSSBzdWdnZXN0IGFkZGluZyBhIHJlZmVyZW5jZSB0byB0aGUgZmlyc3Qgb2NjdXJy
ZW5jZXMgb2Yg4oCcREhDUCBzZXJ2aWNl4oCdIGFuZCDigJxESENQIHNlcnZlcuKAnS4NCj4NCj4J
V2hpbGUgSSdtIG1vcmUgdGhhbiBoYXBweSB0byBkbyB0aGlzLCBJIGRvbid0IGFjdHVhbGx5IGtu
b3cNCj4Jd2hhdCB5b3Ugd291bGQgbGlrZSBtZSB0byByZWZlcmVuY2U/ICBXZSBoYXZlbid0IGRl
ZmluZWQNCj4JZWl0aGVyICJESENQIHNlcnZpY2UiIG9yICJESENQIHNlcnZlciIgaW4gdGhlIGds
b3NzYXJ5IHNpbmNlDQo+CXdlIGZlbHQgdGhleSB3ZXJlIHJlYXNvbmFibHkgYXBwYXJlbnQgZnJv
bSB0aGUgY29udGV4dCBvZiB0aGlzDQo+CWRvY3VtZW50LiAgQXJlIHlvdSB0aGlua2luZyB0aGF0
IHdlIHNob3VsZCByZWZlcmVuY2UgUkZDMzMxNQ0KPglvbiB0aGUgZmlyc3Qgb2NjdXJyZW5jZSBv
ZiAiREhDUCBzZXJ2aWNlIiBhbmQgIkRIQ1Agc2VydmVyIj8NCg0KWWVzLg0KDQoNCj4+IFE0OiAg
ICAgICAgSW4gdGhlIEludHJvZHVjdGlvbiwgeW91IHN3aXRjaCBiZXR3ZWVuIOKAnFRoaXMgcHJv
dG9jb2zigJ0gYW5kIOKAnFRoZSBmYWlsb3ZlciBwcm90b2NvbOKAnS4gUGxlYXNlIHVzZSBjb25z
aXN0ZW50IHRlcm1pbm9sb2d5LiBUaGlzIGFwcGxpZXMgdG8gdGhlIGRvY3VtZW50IGluIGdlbmVy
YWwuDQo+DQo+CU9rLCB3ZSdsbCBnbyB3aXRoICJUaGUgZmFpbG92ZXIgcHJvdG9jb2wiIHNpbmNl
IGl0IGFwcGVhcnMgDQo+CW1vcmUgdGltZXMgc28gZmFyLiAgSSB3aWxsIG1ha2UgdGhpcyBnbG9i
YWwgY2hhbmdlIHdoZW4gSQ0KPgluZXh0IHVwZGF0ZSB0aGUgZG9jdW1lbnQuICANCg0KU291bmRz
IGdvb2QuDQoNCiAgDQo+PiBTRUNUSU9OIDQ6DQo+PiAgDQo+PiBRNTogICAgICAgIEluIHRoZSBB
YnN0cmFjdCBhbmQgSW50cm9kdWN0aW9uIGl0IGlzIHNhaWQgdGhhdCBESENQdjYgZG9lcyBub3Qg
cHJvdmlkZSBzZXJ2ZXIgcmVkdW5kYW5jeS4gVGhlbiBzZWN0aW9uIDQgdGFsa3MgYWJvdXQgZmFp
bG92ZXIgY29uY2VwdHMgYW5kIG1lY2hhbmlzbS4NCj4+ICANCj4+IEFyZSB0aG9zZSBjb25jZXB0
cyBzb21ldGhpbmcgdXNlZCBmb3IgREhDUHY2IHRvZGF5LCBidXQgZm9yIHNvbWUgcmVhc29uIGRv
IG5vdCBmdWxmaWwgdGhlIGZhaWxvdmVyIHByb3RvY29sIHJlcXVpcmVtZW50cz8NCj4+ICANCj4+
IE9SLCBhcmUgdGhlc2UgZ2VuZXJhbCBjb25jZXB0cyB0aGF0IHdpbGwgYmUgc3VwcG9ydGVkIGJ5
IGltcGxlbWVudGluZyB0aGUgZmFpbG92ZXIgcHJvdG9jb2w/DQo+PiAgDQo+PiBJIHRoaW5rIGl0
IHdvdWxkIGJlIGdvb2QgdG8gaGF2ZSBhbiBpbnRyb2R1Y3Rpb24gc3RhdGVtZW50IGNsYXJpZnlp
bmcgdGhhdC4NCj4NCj4JVGhlIGNvbmNlcHRzIGFuZCBtZWNoYW5pc21zIGRpc2N1c3NlZCBpbiBT
ZWN0aW9uIDQgcmVsYXRlIHRvDQo+CXRoZSBmYWlsb3ZlciBwcm90b2NvbCwgdGhleSBhcmVuJ3Qg
cHJlc2VudCBpbiB0aGUgcmVndWxhcg0KPglSRkMzMzE1KGV0LiBhbC4pIERIQ1B2NiBwcm90b2Nv
bC4gIEkgd2lsbCBhZGQgdGhlIGZvbGxvd2luZyB0bw0KPglTZWN0aW9uIDQgdG8gY2xhcmlmeSB0
aGF0Og0KPg0KPgkiNC4gIEZhaWxvdmVyIENvbmNlcHRzIGFuZCBNZWNoYW5pc21zDQo+DQo+CVRo
ZSBmb2xsb3dpbmcgY29uY2VwdHMgYW5kIG1lY2hhbmlzbXMgYXJlIG5lY2Vzc2FyeSB0byB0aGUg
b3BlcmF0aW9uDQo+CW9mIHRoZSBmYWlsb3ZlciBwcm90b2NvbCwgYW5kIHRoZXkgYXJlIG5vdCBj
dXJyZW50bHkgZW1wbG95ZWQgYnkNCj4JdGhlIERIQ1B2NiBwcm90b2NvbCBbUkZDMzMxNV0uDQoN
ClRoYXQncyBiZXR0ZXIuIEJ1dCwgd2lsbCB0aGUgZmFpbG92ZXIgcHJvdG9jb2wgcHJvdmlkZSBz
dXBwb3J0IGZvciB0aG9zZSBjb25jZXB0cz8gSWYgc28sIHBsZWFzZSBpbmRpY2F0ZSBpdC4NCg0K
VGhhbmtzIQ0KIA0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Wed Feb  1 15:07:04 2017
Return-Path: <kkinnear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE681129545 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level: 
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQGhSHiS8yTi for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:07:01 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E6CA129411 for <gen-art@ietf.org>; Wed,  1 Feb 2017 15:07:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2342; q=dns/txt; s=iport; t=1485990421; x=1487200021; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=RSiyJPzfsjc4ZqK/8hl8Pzfgqji3I7XaVV60ObH4VqE=; b=ec1qAov5X2GzMXtN4KyjCKK2xoIWOm5HJOKjDgP4LLM1ORCUq/jNrx6Z 1p9EXhJExbi5grHHnGt5B7xAJawlUkgxQkA2/Kvp+LQjXmEfF+j1/9uXv +C+WMrPChvfy8UHRFFTOXf9SO5zzZ2yESfAz7HOgJ/CSWS4Xk4850XcRL g=;
X-IronPort-AV: E=Sophos;i="5.33,322,1477958400"; d="scan'208";a="203452558"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2017 23:07:00 +0000
Received: from bxb-kkinnear-8814.cisco.com (bxb-kkinnear-8814.cisco.com [10.98.10.245]) (authenticated bits=0) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v11N6xkf007617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 23:07:00 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: kkinnear <kkinnear@cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se>
Date: Wed, 1 Feb 2017 18:06:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <49C6D51E-A1C4-44BB-BC73-0752195D8F41@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com> <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-Authenticated-User: kkinnear@cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zRcgBcM65sOMN82zT-_LHq_NZt4>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:07:03 -0000

Christer,

I have deleted the issues not under discussion.

More comments, indented, below...

> On Feb 1, 2017, at 5:57 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
>>=20
>>> Q3:        In the Introduction, I suggest adding a reference to the =
first occurrences of =E2=80=9CDHCP service=E2=80=9D and =E2=80=9CDHCP =
server=E2=80=9D.
>>=20
>> 	While I'm more than happy to do this, I don't actually know
>> 	what you would like me to reference?  We haven't defined
>> 	either "DHCP service" or "DHCP server" in the glossary since
>> 	we felt they were reasonably apparent from the context of this
>> 	document.  Are you thinking that we should reference RFC3315
>> 	on the first occurrence of "DHCP service" and "DHCP server"?
>=20
> Yes.

	Ok, I will do so in the next update.
>=20
>>> SECTION 4:
>>>=20
>>> Q5:        In the Abstract and Introduction it is said that DHCPv6 =
does not provide server redundancy. Then section 4 talks about failover =
concepts and mechanism.
>>>=20
>>> Are those concepts something used for DHCPv6 today, but for some =
reason do not fulfil the failover protocol requirements?
>>>=20
>>> OR, are these general concepts that will be supported by =
implementing the failover protocol?
>>>=20
>>> I think it would be good to have an introduction statement =
clarifying that.
>>=20
>> 	The concepts and mechanisms discussed in Section 4 relate to
>> 	the failover protocol, they aren't present in the regular
>> 	RFC3315(et. al.) DHCPv6 protocol.  I will add the following to
>> 	Section 4 to clarify that:
>>=20
>> 	"4.  Failover Concepts and Mechanisms
>>=20
>> 	The following concepts and mechanisms are necessary to the =
operation
>> 	of the failover protocol, and they are not currently employed by
>> 	the DHCPv6 protocol [RFC3315].
>=20
> That's better. But, will the failover protocol provide support for =
those concepts? If so, please indicate it.
>=20

	How about this:

	"4.  Failover Concepts and Mechanisms

	The following concepts and mechanisms are necessary to the =
operation
	of the failover protocol, and they are not currently employed by
	the DHCPv6 protocol [RFC3315].  The failover protocol provides
        support for all of these concepts and mechanisms.

	..."

Thanks -- Kim





From nobody Wed Feb  1 15:09:01 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4AEF1295EB for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tocjFlgjnACL for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:08:58 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E61912956C for <gen-art@ietf.org>; Wed,  1 Feb 2017 15:08:58 -0800 (PST)
X-AuditID: c1b4fb25-1cbff700000036c9-07-58926a870d65
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id 92.1C.14025.78A62985; Thu,  2 Feb 2017 00:08:56 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0319.002; Thu, 2 Feb 2017 00:08:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: kkinnear <kkinnear@cisco.com>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
Thread-Index: AdJ8ysFOq+nkh2z8R/yqSz6QRbIwJQACS1KAAAJnoyD///PoAP//7vNQ
Date: Wed, 1 Feb 2017 23:08:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFD9272@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <F5C2B9B7-F35D-4E92-829E-05100DDFBDA5@cisco.com> <7594FB04B1934943A5C02806D1A2204B4BFD921A@ESESSMB209.ericsson.se> <49C6D51E-A1C4-44BB-BC73-0752195D8F41@cisco.com>
In-Reply-To: <49C6D51E-A1C4-44BB-BC73-0752195D8F41@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbHdRrcja1KEwdLLihYnN8xjs7j66jOL xbaGz0wOzB5Tfm9k9Viy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mk7t+89U0CBbcfPeDZYG xgUyXYycHBICJhIvOrawdjFycQgJrGOU+LdjEiOEs4hRYvaH+yxdjBwcbAIWEt3/tEEaRAQU Jf7+vs8OUsMssIJR4tjWh+wgCWEBT4l1ne+ZIIq8JFa9XsUMYbtJTLkxEcxmEVCRODR3NwuI zSvgK7H28nZ2iGXfGSX6jmxlA0lwCthKbF/VwwhiMwqISXw/tQZsKLOAuMStJ/OZIM4WkFiy 5zwzhC0q8fLxP1YIW0li0e3PTCBHMwtoSqzfpQ/RqigxpRviTl4BQYmTM5+wTGAUnYVk6iyE jllIOmYh6VjAyLKKUbQ4tTgpN93IWC+1KDO5uDg/Ty8vtWQTIzB2Dm75rbqD8fIbx0OMAhyM Sjy8BgaTIoRYE8uKK3MPMUpwMCuJ8BYkA4V4UxIrq1KL8uOLSnNSiw8xSnOwKInzmq28Hy4k kJ5YkpqdmlqQWgSTZeLglGpgVDky8Uug/sy01BdnL7rxuoidrZgtOkNiQd6J/JeHHBqij0uZ lLRmMr7Unbj77KnJD2cw/QpdrquoFj3RcfrZK1PPhUwODXkhcLl+o0T3feGnb4/1vkgq/Pfk 5MXHay5kr58Xd+bx44orR/e7upSvj5pw/IHS7KKNGkuY+A69EPCTUrx3cuqpaZZKLMUZiYZa zEXFiQB0vRxmmQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/reJ46M1A2iiXXSNPQimXOc8YbmE>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:09:00 -0000

SGksDQoNCllvdSBzdWdnZXN0aW9ucyBsb29rIGdvb2QsIGFuZCBJIGFtIGhhcHB5IHdpdGggeW91
ciByZXBseSA6KQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbToga2tpbm5lYXIgW21haWx0bzpra2lubmVhckBjaXNjby5jb21dIA0KU2Vu
dDogMDIgRmVicnVhcnkgMjAxNyAwMTowNw0KVG86IENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rl
ci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+DQpDYzogS2ltIEtpbm5lYXIgPGtraW5uZWFyQGNpc2Nv
LmNvbT47IGdlbi1hcnRAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtZGhjLWRoY3B2Ni1mYWlsb3Zlci1w
cm90b2NvbC5hbGxAdG9vbHMuaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBHZW4tQVJUIHJldmlldyBv
ZiBkcmFmdC1pZXRmLWRoYy1kaGNwdjYtZmFpbG92ZXItcHJvdG9jb2wtMDQNCg0KQ2hyaXN0ZXIs
DQoNCkkgaGF2ZSBkZWxldGVkIHRoZSBpc3N1ZXMgbm90IHVuZGVyIGRpc2N1c3Npb24uDQoNCk1v
cmUgY29tbWVudHMsIGluZGVudGVkLCBiZWxvdy4uLg0KDQo+IE9uIEZlYiAxLCAyMDE3LCBhdCA1
OjU3IFBNLCBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
PiB3cm90ZToNCj4gDQo+IEhpLA0KPiANCj4+IA0KPj4+IFEzOiAgICAgICAgSW4gdGhlIEludHJv
ZHVjdGlvbiwgSSBzdWdnZXN0IGFkZGluZyBhIHJlZmVyZW5jZSB0byB0aGUgZmlyc3Qgb2NjdXJy
ZW5jZXMgb2Yg4oCcREhDUCBzZXJ2aWNl4oCdIGFuZCDigJxESENQIHNlcnZlcuKAnS4NCj4+IA0K
Pj4gCVdoaWxlIEknbSBtb3JlIHRoYW4gaGFwcHkgdG8gZG8gdGhpcywgSSBkb24ndCBhY3R1YWxs
eSBrbm93DQo+PiAJd2hhdCB5b3Ugd291bGQgbGlrZSBtZSB0byByZWZlcmVuY2U/ICBXZSBoYXZl
bid0IGRlZmluZWQNCj4+IAllaXRoZXIgIkRIQ1Agc2VydmljZSIgb3IgIkRIQ1Agc2VydmVyIiBp
biB0aGUgZ2xvc3Nhcnkgc2luY2UNCj4+IAl3ZSBmZWx0IHRoZXkgd2VyZSByZWFzb25hYmx5IGFw
cGFyZW50IGZyb20gdGhlIGNvbnRleHQgb2YgdGhpcw0KPj4gCWRvY3VtZW50LiAgQXJlIHlvdSB0
aGlua2luZyB0aGF0IHdlIHNob3VsZCByZWZlcmVuY2UgUkZDMzMxNQ0KPj4gCW9uIHRoZSBmaXJz
dCBvY2N1cnJlbmNlIG9mICJESENQIHNlcnZpY2UiIGFuZCAiREhDUCBzZXJ2ZXIiPw0KPiANCj4g
WWVzLg0KDQoJT2ssIEkgd2lsbCBkbyBzbyBpbiB0aGUgbmV4dCB1cGRhdGUuDQo+IA0KPj4+IFNF
Q1RJT04gNDoNCj4+PiANCj4+PiBRNTogICAgICAgIEluIHRoZSBBYnN0cmFjdCBhbmQgSW50cm9k
dWN0aW9uIGl0IGlzIHNhaWQgdGhhdCBESENQdjYgZG9lcyBub3QgcHJvdmlkZSBzZXJ2ZXIgcmVk
dW5kYW5jeS4gVGhlbiBzZWN0aW9uIDQgdGFsa3MgYWJvdXQgZmFpbG92ZXIgY29uY2VwdHMgYW5k
IG1lY2hhbmlzbS4NCj4+PiANCj4+PiBBcmUgdGhvc2UgY29uY2VwdHMgc29tZXRoaW5nIHVzZWQg
Zm9yIERIQ1B2NiB0b2RheSwgYnV0IGZvciBzb21lIHJlYXNvbiBkbyBub3QgZnVsZmlsIHRoZSBm
YWlsb3ZlciBwcm90b2NvbCByZXF1aXJlbWVudHM/DQo+Pj4gDQo+Pj4gT1IsIGFyZSB0aGVzZSBn
ZW5lcmFsIGNvbmNlcHRzIHRoYXQgd2lsbCBiZSBzdXBwb3J0ZWQgYnkgaW1wbGVtZW50aW5nIHRo
ZSBmYWlsb3ZlciBwcm90b2NvbD8NCj4+PiANCj4+PiBJIHRoaW5rIGl0IHdvdWxkIGJlIGdvb2Qg
dG8gaGF2ZSBhbiBpbnRyb2R1Y3Rpb24gc3RhdGVtZW50IGNsYXJpZnlpbmcgdGhhdC4NCj4+IA0K
Pj4gCVRoZSBjb25jZXB0cyBhbmQgbWVjaGFuaXNtcyBkaXNjdXNzZWQgaW4gU2VjdGlvbiA0IHJl
bGF0ZSB0bw0KPj4gCXRoZSBmYWlsb3ZlciBwcm90b2NvbCwgdGhleSBhcmVuJ3QgcHJlc2VudCBp
biB0aGUgcmVndWxhcg0KPj4gCVJGQzMzMTUoZXQuIGFsLikgREhDUHY2IHByb3RvY29sLiAgSSB3
aWxsIGFkZCB0aGUgZm9sbG93aW5nIHRvDQo+PiAJU2VjdGlvbiA0IHRvIGNsYXJpZnkgdGhhdDoN
Cj4+IA0KPj4gCSI0LiAgRmFpbG92ZXIgQ29uY2VwdHMgYW5kIE1lY2hhbmlzbXMNCj4+IA0KPj4g
CVRoZSBmb2xsb3dpbmcgY29uY2VwdHMgYW5kIG1lY2hhbmlzbXMgYXJlIG5lY2Vzc2FyeSB0byB0
aGUgb3BlcmF0aW9uDQo+PiAJb2YgdGhlIGZhaWxvdmVyIHByb3RvY29sLCBhbmQgdGhleSBhcmUg
bm90IGN1cnJlbnRseSBlbXBsb3llZCBieQ0KPj4gCXRoZSBESENQdjYgcHJvdG9jb2wgW1JGQzMz
MTVdLg0KPiANCj4gVGhhdCdzIGJldHRlci4gQnV0LCB3aWxsIHRoZSBmYWlsb3ZlciBwcm90b2Nv
bCBwcm92aWRlIHN1cHBvcnQgZm9yIHRob3NlIGNvbmNlcHRzPyBJZiBzbywgcGxlYXNlIGluZGlj
YXRlIGl0Lg0KPiANCg0KCUhvdyBhYm91dCB0aGlzOg0KDQoJIjQuICBGYWlsb3ZlciBDb25jZXB0
cyBhbmQgTWVjaGFuaXNtcw0KDQoJVGhlIGZvbGxvd2luZyBjb25jZXB0cyBhbmQgbWVjaGFuaXNt
cyBhcmUgbmVjZXNzYXJ5IHRvIHRoZSBvcGVyYXRpb24NCglvZiB0aGUgZmFpbG92ZXIgcHJvdG9j
b2wsIGFuZCB0aGV5IGFyZSBub3QgY3VycmVudGx5IGVtcGxveWVkIGJ5DQoJdGhlIERIQ1B2NiBw
cm90b2NvbCBbUkZDMzMxNV0uICBUaGUgZmFpbG92ZXIgcHJvdG9jb2wgcHJvdmlkZXMNCiAgICAg
ICAgc3VwcG9ydCBmb3IgYWxsIG9mIHRoZXNlIGNvbmNlcHRzIGFuZCBtZWNoYW5pc21zLg0KDQoJ
Li4uIg0KDQpUaGFua3MgLS0gS2ltDQoNCg0KDQoNCg==


From nobody Wed Feb  1 15:13:45 2017
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3EB12956C for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vTFXe69LpX2h for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:13:41 -0800 (PST)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F9C7129577 for <gen-art@ietf.org>; Wed,  1 Feb 2017 15:13:41 -0800 (PST)
Received: by mail-lf0-x232.google.com with SMTP id v186so236821837lfa.1 for <gen-art@ietf.org>; Wed, 01 Feb 2017 15:13:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=XcArzFBOwhsHRqf3j+9nDShzm+u4h1TD+3serpsau/o=; b=HpPY/FIE663gh9WTbOAOLzy9cyxuC7OJHOKPHEG/ulccse224eBgUsFeSjD8lHOV6L W/TV3ZkMFlgzA+k4M0XWcKSGIpOoQKWYD/esbFDPue/Gu4EPkavBU2jyW2PWNlg/gQFw noDTCD5wN+i45ZfWP/agEgg0ZHJ8Mm+DfjCSd3o3/9OoEXxf0dXHHESYRUTzGUXdRN45 qOkU60UWwX7VkUosyHniEk0aCIgOXyGszudcuQxtgZoti4iwjG+8kdrqmakTOFiKO7dK o9tFKwi2t++SJdM4DK/nGqpXez0iH7swctg2UpX6rFNPpWsa5+p9iB0JWg5ktOeo7K0k tS7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=XcArzFBOwhsHRqf3j+9nDShzm+u4h1TD+3serpsau/o=; b=Mae2bbZe+MvaBWrS5tsCt8AHV8Au1LpSGm92Qlh/LH1ET5qkPb2naZpCqiKhg87UTN ynRsPMRyQXkD3l6YvoWFnL6QNBXqlgOB899JK+3kQHOKYAZOOMm6ZRWIIWFG7+pt5LgQ Z3hFVs8Pqaf2TsK8wnwnS2krCXzO2/nNwdZtvCyrasYrgZt+E34eoyYTAMTWQoEkEb6f FObuJMkVj0iqLUBxGRuwV3IUjDO+mheqUHHsaM6V4m6D9lpagJI9Rqj8o86sn1Ahm7ic 6E3iyuV506Vk0EZb//OzpAyx7V+hO4SfqzchNOvvZKFQG2ksqqFXChm9WuWLpNwqXsg+ E8Yg==
X-Gm-Message-State: AIkVDXKC6h4ONKLu+ua+/wbC68FdYEjXUa8b6fkQ2CIlUmVkD1FupiPloiqcthpVJhlDmQ==
X-Received: by 10.25.18.102 with SMTP id h99mr1607144lfi.63.1485990819449; Wed, 01 Feb 2017 15:13:39 -0800 (PST)
Received: from [192.168.0.9] (109241207033.gdansk.vectranet.pl. [109.241.207.33]) by smtp.googlemail.com with ESMTPSA id h13sm6178397ljh.5.2017.02.01.15.13.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2017 15:13:38 -0800 (PST)
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
Message-ID: <8f859c36-0cf6-e2d8-7609-41c47ff1e226@gmail.com>
Date: Thu, 2 Feb 2017 00:13:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/clczLrB52zFpysGdFHEjhT2FLh4>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:13:44 -0000

W dniu 01.02.2017 o 21:57, Christer Holmberg pisze:
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed by
> the IESG for the IETF Chair.  Please treat these comments just like
> any other last call comments.
>
Hi Christer!
Thanks a lot for your review. See my responses below.
>
> =20
>
> For more information, please see the FAQ at
>
> =20
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> =20
>
> Document:                                    =20
> draft-ietf-dhc-dhcpv6-failover-protocol-04.txt
>
> Reviewer:                                        Christer Holmberg
>
> Review Date:                                  01.02.2017
>
> IETF LC End Date:                          19.01.2017
>
> IESG Telechat date: (if known)    02.02.2017
>
> =20
>
> Summary:                                       The document is almost
> ready for publication, but there are some editorial nits that I=92d lik=
e
> the authors to address.
>
> =20
>
> Major issues:                                 None
>
> =20
>
> Minor issues:                                 None
>
> =20
>
> Nits/editorial comments:
>
> =20
>
> INTRODUCTION:
>
> =20
>
> Q1:        In the first sentence of the Introduction, I suggest to say:=

>
> =20
>
> =93The failover protocol defined in this document provides=85=94
>
Sure, will update as suggested.
>
> =20
>
> Otherwise it=92s a little unclear what failover protocol you are talkin=
g
> about.
>
> =20
>
> Q2:        In the Introduction, before the first sentence, shouldn=92t
> there be some background text, including some information about the
> problem that the document solves. I know there is something in the
> Abstract, but I think there should also be something in the
> Introduction, before jumping into the solution.
>
There's a whole RFC about it: RFC7031. It was intended as a gentle
introduction to the DHCP failover problem: what is in and outside of
scope, when failover is useful and when it may not be the best tool. The
DHC WG decided to split it into separate document, because there are
lots of things to explain and the core document is already obscenely
large. This RFC is clearly linked at the end of Introduction section.
Perhaps it would be more useful to move this reference to the front and
add a sentence or two of explanation? How about this text added as a
first paragraph?

This document defines a DHCPv6 failover protocol, which is a mechanism
for running two DHCPv6 servers with the capability for either server to
take over clients' leases in case of server failure or network
partition. For a general overview of the DHCPv6 failover problems, use
cases, benefits and shortcomings, see RFC7031."
>
> =20
>
> Q3:        In the Introduction, I suggest adding a reference to the
> first occurrences of =93DHCP service=94 and =93DHCP server=94.
>
DHCP service is not a formal term. It was intended as a general
description of the DHCP server availability. How about we replace "or
provide a DHCP service" with "to provide service to DHCP clients"?
>
> =20
>
> Q4:        In the Introduction, you switch between =93This protocol=94 =
and
> =93The failover protocol=94. Please use consistent terminology. This
> applies to the document in general.
>
There are 8 instances of "this protocol" and 20 of "the failover
protocol". We will go with the latter, ok?
>
> =20
>
> SECTION 4:
>
> =20
>
> Q5:        In the Abstract and Introduction it is said that DHCPv6
> does not provide server redundancy. Then section 4 talks about
> failover concepts and mechanism.
>
> =20
>
> Are those concepts something used for DHCPv6 today, but for some
> reason do not fulfil the failover protocol requirements?
>
> =20
>
> OR, are these general concepts that will be supported by implementing
> the failover protocol?
>
> =20
>
> I think it would be good to have an introduction statement clarifying
> that.
>
These are not being used by any non-failover DHCPv6 today. There is one
implementation of this draft that uses them. Most of those mechanisms
are required by any sane failover design (e.g. any kind of failover-like
solution has to use lazy updates or it would be undeployable due to
performance), but some are specific to this particular failover design
(e.g. the allocation algorithms). Would the following text added at the
beginning of Section 4 be sufficient?

"The following section describes core concepts that are a foundation of
this failover protocol. Allocation strategies described in Section 4.2
are specific to this particular failover design, while the concept of
Lazy updates (Section 4.3) and MCLT (Section 4.4) seem to be necessary
for any failover design."

Also, if you think it's useful, we can repeat a 7031 reference there,
possibly to Section 5.2 that discusses lazy updates
(update-after-response) and its alternative (update-before-response).

Thanks again for your review,
Tomek



From nobody Wed Feb  1 15:17:32 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B83812956C; Wed,  1 Feb 2017 15:17:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHANsUzu2KZq; Wed,  1 Feb 2017 15:17:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id E5A231295E7; Wed,  1 Feb 2017 15:17:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4162F2D299; Thu,  2 Feb 2017 01:17:28 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Npuk2tSN6trl; Thu,  2 Feb 2017 01:17:27 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 563AD2CC9B; Thu,  2 Feb 2017 01:17:27 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_95C404B6-D821-4E02-842F-A97B2091DB8E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <2A345AB1-1064-4546-87B1-F54F8EEB2EB1@gmail.com>
Date: Thu, 2 Feb 2017 00:17:28 +0100
Message-Id: <68781A75-A25A-4B33-85C4-6510814989B6@piuha.net>
References: <148090444981.5523.17374875997079514429.idtracker@ietfa.amsl.com> <337ddd16-232b-6fee-d910-eb3d35a0e874@trigofacile.com> <2A345AB1-1064-4546-87B1-F54F8EEB2EB1@gmail.com>
To: "jouni.nospam" <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/SohqQ7yjhiaitf_thpF2637XD9k>
Cc: draft-elie-nntp-tls-recommendations.all@ietf.org, "General Area Review Team \(Gen-ART\)" <gen-art@ietf.org>, =?iso-8859-1?Q?Julien_=C9LIE?= <julien@trigofacile.com>
Subject: Re: [Gen-art] Review of draft-elie-nntp-tls-recommendations-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:17:30 -0000

--Apple-Mail=_95C404B6-D821-4E02-842F-A97B2091DB8E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Jouni.

Jari


--Apple-Mail=_95C404B6-D821-4E02-842F-A97B2091DB8E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkmyIAAoJEM80gCTQU46qR9cQAINfuS9TZy7cyy1vkulupWUF
AWGfSLZOIOdXJ2NiRTuOO96GW/mQeAkx7Fwvug3ttUA1rPojCek6VQlpQ3WbK+Wb
wEzG0u1Xk4v5B+44BG5+1yaow2KytDxeQ+BPrWp2Ud+D07QgUye5Cvwj5m67JWir
jfM6Up1gqqfvtZeeNKYLBxwQ9OhWypiPeWfXRFO/lPXKQO5RKHpckoTAzeOOLru9
wrb1YbaHYpSHP2xYE3JtUJ6jW+U+RRxMj+zb24sxVBcnuMSlTYwcmqgI5dO/eKHM
AzHmvwNEODLoOQla9BT5c+d/Ek0ItcSTSUehRCEp+X6lrj9E5EAxrUhI9kEwYeTB
oghnX7xT4CcLpzUWH1zXgmsMccHz0erRc4+nZIFEJGs7DB7z7WJwI9T+D2OmoBUU
K3d521C/rfxv5xyE6EG8EHqTdvOZdzRefi2VmgKbkEL8YakwWBwRdsxklaUt23AW
ARUHW9vvN6ubIOK8pVM2z1PXhq0Jx7Hjq8CHkaIfXTAcvH7GG9ofeu9xum1OOiJR
oknZTBapU10mCqXn7GYaVaVO87YTrPZ0WVNf+c7aOH8D70jtl0ltxdbouI1z/0iP
i03oRaLEcyYSo31oQUAXIYl934uf2u0nm0kBSrpvLW5A1pOKhbRU465WV7TsLr9Z
l4KH5Wa/9iWj0uWmZSV7
=qLpn
-----END PGP SIGNATURE-----

--Apple-Mail=_95C404B6-D821-4E02-842F-A97B2091DB8E--


From nobody Wed Feb  1 15:18:34 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A03C129577; Wed,  1 Feb 2017 15:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TALQtNXRfVbx; Wed,  1 Feb 2017 15:18:31 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 454DF12956C; Wed,  1 Feb 2017 15:18:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 976D52D299; Thu,  2 Feb 2017 01:18:30 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZZECUP5Aidm; Thu,  2 Feb 2017 01:18:30 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D07F72CC9B; Thu,  2 Feb 2017 01:18:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_FE187BA9-1083-451C-9D5C-081B3C247D5F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148567513024.18009.8111685197507656381.idtracker@ietfa.amsl.com>
Date: Thu, 2 Feb 2017 00:18:30 +0100
Message-Id: <EC6D393C-185C-46BC-A629-49111238D1CA@piuha.net>
References: <148567513024.18009.8111685197507656381.idtracker@ietfa.amsl.com>
To: Roni Even <roni.even@mail01.huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ML2ho_R8d-zvAEQGyZralgQKJis>
Cc: "General Area Review Team \(Gen-ART\)" <gen-art@ietf.org>, draft-ietf-intarea-hostname-practice.all@ietf.org, int-area@ietf.org
Subject: Re: [Gen-art] [Int-area] Review of draft-ietf-intarea-hostname-practice-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:18:32 -0000

--Apple-Mail=_FE187BA9-1083-451C-9D5C-081B3C247D5F
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Roni: Thanks for your review!

Jari


--Apple-Mail=_FE187BA9-1083-451C-9D5C-081B3C247D5F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkmzGAAoJEM80gCTQU46qdRcQAL4PhUEnF+YUGqCA+LkFvo55
GkSBIo34wdnYdsDQWBuVFBCq4ZMmglLatccfbU2rn0p4F1A3Z8AjFnm61kXKIrv7
7/aA3r2cyRyAAZxzgY3t5dJNtykr0mrKb9knmJ3YFDGHOOpq68tY/In9ihEDTbEx
JLz2cWdPGGQwxxU8YAjM1eh/NhbBzAY9WPjLb1P8MMeOghBwlcKief1UyiVvkTyM
PbxmqJy/4ha59u5WMZchHLGTRC4CaR79x6qMSVBgj8d5k1V1Tx1wzQRmQW6s8Z/A
WgoQoep2UDCVbGZN+RnqQJ71cGDIbBSrzUipJjXUApkJkrPYp4YT5qerNXRmimaq
g7GjFNA7zpbii8P91GlB2XxeYrZlwsmx31ePRc7BebF+nBpJZqWJYNfIiWp/icmv
kjCE4PJrO3jPjqXPIkfmE5BKfY5ojAbHSDO5ttX4gzmhbckz15rAHb7IiBJFiQWH
s17aTXnYIEprv61eONSpgNzxJ6vml1jKe+y08/6JOhyisfstzXA0GOQp8B8gngBS
H4e0ohTAf9h5WtUzxiPUR1kKkeYmaLiXStlg7bjObjMpyUvbyJaDBXxfZWgg0t4S
L5GjPXy/OsiIcmFX60BUYOZaVsxtd0qlSEok3u9q2f9Spkeg+vchONcKHMHzOhap
ZUMC1qztE5ylVg3B5Aim
=NRQN
-----END PGP SIGNATURE-----

--Apple-Mail=_FE187BA9-1083-451C-9D5C-081B3C247D5F--


From nobody Wed Feb  1 15:23:44 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9821295E7; Wed,  1 Feb 2017 15:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SyWPXTl7iKqC; Wed,  1 Feb 2017 15:23:39 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2ED129577; Wed,  1 Feb 2017 15:23:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 90EA12D299; Thu,  2 Feb 2017 01:23:38 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyyvfGSRK1FM; Thu,  2 Feb 2017 01:23:38 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id CA8F42CC9B; Thu,  2 Feb 2017 01:23:37 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_688E80DB-0F2C-409F-8274-3E95C6D02918"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148559646171.17936.13169778377127397507.idtracker@ietfa.amsl.com>
Date: Thu, 2 Feb 2017 00:23:39 +0100
Message-Id: <EFFC3F14-A35B-4796-B6D9-A6946928FA8B@piuha.net>
References: <148559646171.17936.13169778377127397507.idtracker@ietfa.amsl.com>
To: Stewart Bryant <stewart@g3ysx.org.uk>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0uu4TT7CzfYd6hWoENguNsJ5kfc>
Cc: "General Area Review Team \(Gen-ART\)" <gen-art@ietf.org>, insipid@ietf.org, draft-ietf-insipid-logme-reqs.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-insipid-logme-reqs-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:23:41 -0000

--Apple-Mail=_688E80DB-0F2C-409F-8274-3E95C6D02918
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for your review, Stewart. I set the my position to =93No =
objection=94 for this document in the upcoming IESG telechat.

Jari


--Apple-Mail=_688E80DB-0F2C-409F-8274-3E95C6D02918
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkm37AAoJEM80gCTQU46qeRkP/01jSpF4qPRuOR3GRRJiayUJ
WBLTcpyXJVkzf/R736AYVoY5rZFmi6jR7NuaOo2DgMZsWpO3B/ITNpMcVUnBCmWT
PY6vR2DGEEA1A+jRLK0jZACHWufg8VI1Jp0SEMF3RhqqqX0x1o+IXGigzp1zLP6C
Ujbhkrz4sGls9z8fXsviG4HRuI9s+ZLEKWIsEikyRctokI0/PmtRaRxFsYWIdTTL
lDz6nhnvVOy1RNQokBwsHzbeZNTyV38A5b8iNYER2Q4qsR53IxMnZ7qCpdWTddCY
rCvxpp6+oFl7ccl3vjUL5gUm7HJ8ijAjhrjYOM97Mq2JKt9ecY2xfwOuyZ4s6YIi
ap8fFCE9LdxQtqIKeLOur5b/i/CBfr35LD03kQThbWlChjRJnl11Vc08OhG9zNXp
eC3q+zZ3/Lg6xN7jEqymha15vJR+e+pN4J+qFztrCHvuILbP9I45EJ/olRMF4Ltp
mbnsp8OprwWIaQTaixUZpxu/P9dTGWQbC58ZBaHEglE14a8geYTEbtRZZmCFl0Ex
cjnecHnjEgPJS+MJX9+zn0tcPuFALykXRHcSdqJIwZ+csaS8DzJ17w9fdOQ8EA14
sUF+eK0/0iRtmfYTzMrcBd2tqkVXggscTinsN/8bLONafwfGKcESOdmYzZutRBT7
yBL3zfqeTwiMpTx14d00
=EOJy
-----END PGP SIGNATURE-----

--Apple-Mail=_688E80DB-0F2C-409F-8274-3E95C6D02918--


From nobody Wed Feb  1 15:24:30 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7BB21295F8; Wed,  1 Feb 2017 15:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, TVD_SPACE_RATIO=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwzxad5gnEPq; Wed,  1 Feb 2017 15:24:26 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 6AEA51295F2; Wed,  1 Feb 2017 15:24:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C1F3F2D299; Thu,  2 Feb 2017 01:24:25 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-uFes8YZpQ5; Thu,  2 Feb 2017 01:24:25 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 1C5C22CC9B; Thu,  2 Feb 2017 01:24:25 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_AC6D7C3A-547D-4B83-8B5D-1B932DD775C6"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148570720282.789.15709879423808499905.idtracker@ietfa.amsl.com>
Date: Thu, 2 Feb 2017 00:24:26 +0100
Message-Id: <07A92176-F865-4BFF-90E3-8474FCF09A7D@piuha.net>
References: <148570720282.789.15709879423808499905.idtracker@ietfa.amsl.com>
To: Dale Worley <worley@ariadne.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gXsT2IM_IxoyxPB2k7hW_s-FXHA>
Cc: "General Area Review Team \(Gen-ART\)" <gen-art@ietf.org>, teas@ietf.org, draft-ietf-teas-gmpls-resource-sharing-proc.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-teas-gmpls-resource-sharing-proc-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:24:28 -0000

--Apple-Mail=_AC6D7C3A-547D-4B83-8B5D-1B932DD775C6
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks!

Jari


--Apple-Mail=_AC6D7C3A-547D-4B83-8B5D-1B932DD775C6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkm4qAAoJEM80gCTQU46qnKcQAKB7w56RcVN2yQ/9y0FbDj7R
FNfYVGuyarDA7kZ3SqW/P94Fx+aOX0Teocjw9Tn4k9aCxEkQ1+8k0B9pL6pa5bHW
BfrUWYx5dZJiez9FDEOkG/r0xPGKo4jV0blAVCgWi7Id8Mq1BYc0WJHmJa0rwwyb
euTNksDEDvVbJbVLN8gnGsFwxD0rBOw3odntXrYyjoVnKGnjiFeAoSLmEj6cUFA2
EOUoeHew8pr4wIYcsNpt3mDy33ImgiZssEjIV6Q/v9ZFdSHKjN8GYWm5R/oZLpmB
VSTnwMkM/h5O2J+UkWek2sqK3H2Bfr8pQEje731CYUI6WnoL4C5LWhrlA7+0xxUc
T5dsr25ELRXS7zPa5tHyxyGlCAERPkxxZQcoUb9BgsPFNVkGrmS48YQmRpRedzzj
WLhRRib6JyUWdldTaBnDBuU3bnnWpR9y4O50yNZ02uNerLSkdk4pc4k9p3ZIQaxx
D+huj14/EnmmgFQtgX4vPN4lpDsybkFgkz1PvgKBTx7SQCg7REZisJUSm5iYPR2l
m1VwWcFKLKuFsYU/chyFT7z7MqRaEqpUHVEmrGlevAm7zD5Wt83Ctf2+0PznDnQS
IISoRQi4aZCyGqkDksRbzn2eJRhjDOIqRsiDnDUo6djKk6TI6fcqgzSJhQ9hCk3z
Rz5mH1xx8OnWRQ1ZhtnJ
=kz76
-----END PGP SIGNATURE-----

--Apple-Mail=_AC6D7C3A-547D-4B83-8B5D-1B932DD775C6--


From nobody Wed Feb  1 15:30:25 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6C5129577 for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjvHzuak23Iv for <gen-art@ietfa.amsl.com>; Wed,  1 Feb 2017 15:30:23 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B26612956C for <gen-art@ietf.org>; Wed,  1 Feb 2017 15:30:22 -0800 (PST)
X-AuditID: c1b4fb30-13a0498000007085-80-58926f8cd31c
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id E6.1F.28805.C8F62985; Thu,  2 Feb 2017 00:30:21 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Thu, 2 Feb 2017 00:30:18 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-failover-protocol.all@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
Thread-Index: AdJ8ysFOq+nkh2z8R/yqSz6QRbIwJQADa1wAAAJ5SOA=
Date: Wed, 1 Feb 2017 23:30:17 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFD92E7@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8F92@ESESSMB209.ericsson.se> <8f859c36-0cf6-e2d8-7609-41c47ff1e226@gmail.com>
In-Reply-To: <8f859c36-0cf6-e2d8-7609-41c47ff1e226@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7tG5v/qQIg1mHBS1ObpjHZnH11WcW i/3XFjA5MHvsnHWX3WPJkp9MHl8uf2YLYI7isklJzcksSy3St0vgyliw0b5goVxF99EtTA2M /RJdjJwcEgImEp9n/2bvYuTiEBJYxyjx4+5LNghnEaPEvQtLWboYOTjYBCwkuv9pg8RFBG4w Svy+N58dpFtYwFNiXed7JhBbRMBLYtXrVcwQtpXEgaZ/YDaLgIrE3m2tYDavgK/E4RNPobY1 MErcOg3RwClgK/Hl+mM2EJtRQEzi+6k1YEOZBcQlbj2ZzwRxqoDEkj3nmSFsUYmXj/+xQthK Eotuf4aq15FYsPsTG4StLbFs4WuoxYISJ2c+YZnAKDILydhZSFpmIWmZhaRlASPLKkbR4tTi pNx0IyO91KLM5OLi/Dy9vNSSTYzAKDm45bfBDsaXzx0PMQpwMCrx8BoYTIoQYk0sK67MPcQo wcGsJMJ7LQcoxJuSWFmVWpQfX1Sak1p8iFGag0VJnNds5f1wIYH0xJLU7NTUgtQimCwTB6dU A6NWsRef/bob33MntmaWHVf2nBZ5K/hkZ4HYn3qrnUbyv2I0Rd/mCfgsfj7t+KuHfsKTC3JY 6nu932eueK/b8zasco7ULjmmPquYuD1nYtb9qA+r7gz1LE5g+P7IICRG8OUPm+V1h5ha10su aWN5tWRR9kv9A5uDRD7VRB5TYD2cycWnn+7EqsRSnJFoqMVcVJwIAOEvtiaOAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/E6TT3x750DVn7S-TWhFrJEyBqlA>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-failover-protocol-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:30:24 -0000

Hi,

INTRODUCTION:


>> Q2:        In the Introduction, before the first sentence, shouldn't
>> there be some background text, including some information about the=20
>> problem that the document solves. I know there is something in the=20
>> Abstract, but I think there should also be something in the=20
>> Introduction, before jumping into the solution.
>>
>There's a whole RFC about it: RFC7031. It was intended as a gentle introdu=
ction to the DHCP failover problem: what is in and outside of scope, when f=
ailover is useful and >when it may not be the best tool. The DHC WG decided=
 to split it into separate document, because there are lots of things to ex=
plain and the core document is already >obscenely large. This RFC is clearl=
y linked at the end of Introduction section.
>Perhaps it would be more useful to move this reference to the front and ad=
d a sentence or two of explanation? How about this text added as a first pa=
ragraph?
>
>This document defines a DHCPv6 failover protocol, which is a mechanism for=
 running two DHCPv6 servers with the capability for either server to take o=
ver clients' leases in >case of server failure or network partition. For a =
general overview of the DHCPv6 failover problems, use cases, benefits and s=
hortcomings, see RFC7031."

Works for me.

>> Q3:        In the Introduction, I suggest adding a reference to the
>> first occurrences of "DHCP service" and "DHCP server".
>>
>DHCP service is not a formal term. It was intended as a general descriptio=
n of the DHCP server availability. How about we replace "or provide a DHCP =
service" with "to >provide service to DHCP clients"?

Works for me.

>> Q4:        In the Introduction, you switch between "This protocol" and
>> "The failover protocol". Please use consistent terminology. This=20
>> applies to the document in general.
>>
> There are 8 instances of "this protocol" and 20 of "the failover protocol=
". We will go with the latter, ok?

I can live with both, but the latter would be my preference too.

SECTION 4:

>> Q5:        In the Abstract and Introduction it is said that DHCPv6
>> does not provide server redundancy. Then section 4 talks about=20
>> failover concepts and mechanism.
>>
>> Are those concepts something used for DHCPv6 today, but for some=20
>> reason do not fulfil the failover protocol requirements?
>>
>> OR, are these general concepts that will be supported by implementing=20
>> the failover protocol?
>>
>> I think it would be good to have an introduction statement clarifying=20
>> that.
>
> These are not being used by any non-failover DHCPv6 today. There is one i=
mplementation of this draft that uses them. Most of those mechanisms are re=
quired by any sane >failover design (e.g. any kind of failover-like solutio=
n has to use lazy updates or it would be undeployable due to performance), =
but some are specific to this particular >failover design (e.g. the allocat=
ion algorithms). Would the following text added at the beginning of Section=
 4 be sufficient?
>
>"The following section describes core concepts that are a foundation of th=
is failover protocol. Allocation strategies described in Section 4.2 are sp=
ecific to this particular >failover design, while the concept of Lazy updat=
es (Section 4.3) and MCLT (Section 4.4) seem to be necessary for any failov=
er design."

Works for me.

>Also, if you think it's useful, we can repeat a 7031 reference there, poss=
ibly to Section 5.2 that discusses lazy updates
>(update-after-response) and its alternative (update-before-response).

I think that would be useful.

Note that Kim had slightly different suggestions on how to address the issu=
es. I am fine those, so I'll leave it up to you to decide which ones to ado=
pt :)

Thanks!

Regards,

Christer


From nobody Wed Feb  1 15:31:50 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3E4A12959A; Wed,  1 Feb 2017 15:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAS6v89nlLjX; Wed,  1 Feb 2017 15:31:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 78475129577; Wed,  1 Feb 2017 15:31:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C984D2D299; Thu,  2 Feb 2017 01:31:46 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sirF2p2jjvv; Thu,  2 Feb 2017 01:31:46 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E315F2CC9B; Thu,  2 Feb 2017 01:31:45 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E2D46BB7-A390-4908-8218-8F0CF2C7D59E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148130382551.4722.6409764037485645504.idtracker@ietfa.amsl.com>
Date: Thu, 2 Feb 2017 00:31:47 +0100
Message-Id: <3C664EFF-801B-4954-961E-752C252A9ADE@piuha.net>
References: <148130382551.4722.6409764037485645504.idtracker@ietfa.amsl.com>
To: Lucy Yong <lucy.yong@huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/R18Fe7w6Wd1zQU-nLktFO5SYbdA>
Cc: gen-art-private@ietf.org, "General Area Review Team \(Gen-ART\)" <gen-art@ietf.org>, draft-harkins-owe.all@ietf.org
Subject: Re: [Gen-art] Review of draft-harkins-owe-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:31:49 -0000

--Apple-Mail=_E2D46BB7-A390-4908-8218-8F0CF2C7D59E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Lucy!

Jari

On 09 Dec 2016, at 18:17, Lucy Yong <lucy.yong@huawei.com> wrote:

> Reviewer: Lucy Yong
> Review result: Ready with Nits
> 
> The draft is nearly ready for the publication.
> 
> Minor comment: Suggest adding this in security considerations: OWE
> provides encryption over the wireless medium, i.e., Wi-Fi without
> authentication. Thus it does not provide security for end-to-end
> traffic.  users should still use application level security such as
> VPN for end-to-end security. In this case, use of OWE prevents VPN
> authentication info. to be spoofed in open public Wi-Fi.
> one question: Will a user notices if OWE is used or not?  This may be
> important for some users.
> 
> nit: r/encryption of the wireless medium/encryption over the wireless
> medium/
> 
> 
> 


--Apple-Mail=_E2D46BB7-A390-4908-8218-8F0CF2C7D59E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYkm/jAAoJEM80gCTQU46qjYcP/RKH5Al8oe8qS9Z7xvGeGzbU
EmGBBMENZCMd2LV1Zmo2AR87Baq/cmPYAeWQzzUecZ5yU6e9tpeEBmxU7dJ37P8D
wN0McgE8NLhqs2KMVsniwWcXU9UoraBKSHf3O5mOhtTaFMT04QEoBkzSGs2EWPOK
QlXyop1Q3w+eJwSdAMehJJHqMwKK57bZBlxFVrnkVS0f7eT7UkutprS5XyRb1xFk
IGmBJyVwL1oJ+wvRScuyTqvPQTVoxH5qkHV2yml4aKQ/pcRfqwoWS/HtSlqACbRu
/q8N4WLwf1RpK/1iPntf//kOb+KLGCVoHM9JKzlfdAhCPINl+wgFgzgL1oKiSBXP
x7feT55GGAXZX7ebmEwLpwSVqFElw9F4OzPJ9OFgKmW36e9WjdIm5Ym6gUgVLnBH
kXvjlsKcru5wQORY/V1houTqygdGDXnNfNltKjDY+n6UqefG9L/NbtEF8qFRHiy2
Ns9E/6RunXdwg02lYajclealF6Zr8C//cCMIXt91BnocC4qFAknRRWHnGOAoAAoA
mzru+/fxbZ09U+ymnGBXi0BUswZoefGm5nUd20JdXI5/JenEtVS/giKCiY5C36nt
EUmZEbgjHmSZWUw7OvNUJkftEMl29h652rAhsy0BwPT19knGPWYFPzB+9JCYXoBi
p42JvQLRCI2V+ebe2gt0
=Ff3S
-----END PGP SIGNATURE-----

--Apple-Mail=_E2D46BB7-A390-4908-8218-8F0CF2C7D59E--


From nobody Wed Feb  1 21:09:46 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F60126579; Wed,  1 Feb 2017 21:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level: 
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPTHz_7SXkpY; Wed,  1 Feb 2017 21:09:38 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B86B3128B38; Wed,  1 Feb 2017 21:09:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15803; q=dns/txt; s=iport; t=1486012177; x=1487221777; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RXcYe8XEFbgJOe2pkyk2Xa03uI31b1HYArcRpuOUFSY=; b=TUAQ1WvrRPuQWZsUwtvLl+ZfAB5mQgimS/wOXwzPBEYY1Rq9pmASQ32x BUTHg6wF/obqHB78NZMZX+E/b5KYbidtQQbCl4bZt+IXGoRzX0fUxavdI t56A7xcjnxCIB0fqH8oGJNs7UXQ0UdStn6oQNwMkperp4XPb23zqDUCur 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BgAgBfvpJY/5ldJa1TAQkZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDU2GBCQeNWJExV5U1gg0fDYV2AoJAPxgBAgEBAQEBAQFiKIR?= =?us-ascii?q?qAgQBATgtBwsQAgEIEgIBIRAnCxcOAgQBDQMCiXEOrxyLLgEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAR2GS4NmgQmEJQEDXIUtBY82jCcBhmeDHogBgXtThESDTYYjiCe?= =?us-ascii?q?KXAEfOIFLFTuERB2BYUMyAYYsKoEGgQwBAQE?=
X-IronPort-AV: E=Sophos;i="5.33,323,1477958400"; d="scan'208";a="206564865"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2017 05:09:35 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1259ZLq009565 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 Feb 2017 05:09:35 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Feb 2017 23:09:34 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Wed, 1 Feb 2017 23:09:34 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSfRKL4IsoqrqRR0ud1/efTVlacQ==
Date: Thu, 2 Feb 2017 05:09:34 +0000
Message-ID: <D4B7FC35.258902%sgundave@cisco.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F795399A3B3588449753A5BCCF4FA1AD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9Wfe1h1gBBe80zSlfQANZkMbAzg>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 05:09:40 -0000

Thank you Dale for a great review.


Charlie/Authors - Can you please respond to Dale and address these
comments.


Regards
Sri


On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
on behalf of worley@ariadne.com> wrote:

>Reviewer: Dale Worley
>Review result: Ready with Issues
>
>I am the assigned Gen-ART reviewer for this draft.  The General Area
>Review Team (Gen-ART) reviews all IETF documents being processed
>by the IESG for the IETF Chair.  Please treat these comments just
>like any other last call comments.
>
>For more information, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Document:  draft-ietf-dmm-4283mnids-04
>Reviewer:  Dale R. Worley
>Review Date:  31 Jan 2017
>IETF LC End Date:  2 Feb 2017
>IESG Telechat date:  16 Feb 2017
>
>Summary:
>
>       This draft is on the right track but has open issues,
>described
>       in the review.
>
>Technical issues:
>
>1. The Introduction states
>
>   Other types of identifiers are in
>   common use, and even referenced in RFC 4283.
>
>For the reader's sanity, some sort of accounting needs to be made of
>these "other types of identifiers", especially because each type of
>identifier needs an identifier type number.  The text in 4283 is
>
>   Some examples of identifiers
>   include Network Access Identifier (NAI), Fully Qualified Domain
>Name
>   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>   Subscriber Number (MSISDN).
>
>Are there any other types "in common use"?
>
>- NAI (type 1) is defined by 4283.
>- Fully Qualified Domain Name (FQDN) seems not to be specified
>- International Mobile Station Identifier (IMSI) (type 3) is defined
>in
>  this draft
>- Mobile Subscriber Number (MSISDN) seems not to be specified
>
>2. Is it intended to have an IMEI identifier type?  The introduction
>mentions an IMEI type, but there is no specification for it, nor is
>there an identifier type number assigned for it.
>
>   ... types for IMSI
>   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>GUTI
>   [ThreeGPP-IDS].
>
>Initially I suspected it was it was present in an earlier revision
>and
>then later deleted without this reference being updated.  But all
>versions of draft-ietf-dmm-4283mnids and its predecessor
>draft-perkins-dmm-4283mnids mention IMEI in this way as one
>identifier
>type, but none specify it in any way.  The only discussion I can find
>on the DMM mailing list of IMEI is:
>
>  =20
>https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>=3Dd29575f767ce67a1e67a7767008ee6af
>
>    From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>    To: DMM
>    Date: Wed, 10 September 2014 13:29 UTC
>    Re: [DMM] regarding the re-chartering..
>
>    It seems the MNID is somehow overloaded to carry both,
>node-specific
>    IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>    There may be value in adding the IMEI to the list of possible
>types of
>    node-specific IDs.
>
>Either the presence of IMEI in this list is a simple mistake that has
>persisted in all versions of the draft, or specifying IMEI has always
>been intended but has always been overlooked.
>
>3. The definition of identifier types for both EUI-48 and EUI-64
>suggests that it might be desirable to define an identifier type for
>arbitrary hardware (link-level) addresses.  It seems that the natural
>differentiator for that purpose is the "hardware type" used in ARP,
>so
>a EUI-48 address would be represented as
>
>    MN identifier type (one octet) 5 (say)
>    hardware type (two octets) 1
>    EUI-48 (six octets)
>
>and an EUI-64 similarly, with hardware type 27.
>
>Although with only two subtypes in common use, generalizing this
>might
>not be worth the effort.
>
>4. Several of the identifier types can be represented as URNs:
>
>- IMEI can be represented as a URN as urn:gsma:imei:...
>- all of the RFID types have a URN representation (called the
>  "pure-identity URI" in the RFID specifications), which starts
>  urn:epc:id:...
>
>Since all URN types are ensured of being unique and persistent, it
>seems that we could define a MNID type for URNs generally, and then
>any RFID URI or an IMEI (as a URN) could be used as a value of that
>type.
>
>If this idea is adopted, it seems that the other 3GPP types (IMSI,
>P-TMSI, and GUTI) should be given defined encodings as URNs in new
>sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>of IMEIs defined in RFC 7254.
>
>This consolidation could be significantly beneficial.  It allows MNID
>to use any URN scheme as an identifier.  It reduces the three
>different RFID representations to one.  It incorporates any future
>expansion of RFID schemes (because all schemes will have a
>pure-identity URN representation).  A disadvantage is that the URN
>encodings are long, but the security considerations section states
>that MNIDs are used only on the first registration at the home agent,
>so there isn't much need for brevity.
>
>Similarly, this approach incorporates any future expansion of mobile
>identifiers that GSMA decides to define, as long as GSMA provides a
>URN representation for it.
>
>The most significant disadvantage is that some URN schemes allow
>several character strings to "mean" the same URN.  In most URN
>schemes, the allowed variation is limited to the case of letters, and
>the common convention is to always use lower-case when there is a
>choice, leading to a unique conventional canonical form for the URN.
>
>5. Regarding the encoding of a string of digits into octets, it is
>stated that "The last digit MUST be zero padded, if needed, for full
>octet size."  This seems very unwise unless there is a 3GPP decree
>that if a zero is appended to a valid IMSI, the resulting string is
>never a valid IMSI.  Instead, I would specify that padding is by
>filling the low-order 4 bits of the final octet with 0xF.  That
>ensures that the encoding can be uniquely decoded into an IMSI.
>
>6. There are four types of DUID specified, each with a distinct MNID
>value.  However, DUIDs contain an initial two-octet type field which
>distinguishes the various types of DUID, so providing them with
>distinct MNID values is redundant.
>
>Distinguishing the types and allowing only four of them to be used as
>MNIDs seems to be contrary to the philosophy of DUID construction
>(RFC
>3315 section 9):
>
>   Clients and servers MUST treat DUIDs as opaque values and MUST
>only
>   compare DUIDs for equality.  Clients and servers MUST NOT in any
>   other way interpret DUIDs.  Clients and servers MUST NOT restrict
>   DUIDs to the types defined in this document, as additional DUID
>types
>   may be defined in the future.
>
>Of course, MNID isn't a DHCP operation, so it isn't subject to those
>requirements, but I expect that devices will use the same DUID for
>both mobile identification, and we don't want mobile identification
>to
>restrict future developments of DHCP.
>
>I think this specification must treat DUIDs as opaque and use only
>one
>MNID type that allows all types of DUIDs as values.
>
>Editorial issues:
>
>Abstract
>
>   Additional Identifier Types are proposed for use with the Mobile
>Node
>   Identifier Option for IPv6 (RFC 4283).
>
>s/proposed/defined/
>This document will define the new types (once it is approved)!
>
>1.  Introduction
>
>   ... types for IMSI
>   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>GUTI
>   [ThreeGPP-IDS].
>
>There is no description of P-TMSI identifiers, although it is
>assigned
>identifier type 4.
>
>There is no description of GUTI identifiers, although it is assigned
>identifier type 7.
>
>3.  New Mobile Node Identifier Types
>
>   The following types of identifiers are commonly used to identify
>   mobile nodes.  For each type, references are provided with full
>   details on the format of the type of identifier.
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   including
>
>   o  RFID-GID (Global Identifier),
>   o  RFID-SGTIN (Serialized Global Trade Item Number),
>   o  RFID-SSCC (Serial Shipping Container),
>   o  RFID-SGLN (Global Location Number),
>   o  RFID-GRAI (Global Returnable Asset Identifier),
>   o  RFID-DOD (Department of Defense ID), and
>   o  RFID-GIAI (Global Individual Asset Identifier).
>
>   For each RFID scheme except GID, there are two variations: a
>64-bit
>   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>has
>   only a 96-bit scheme.  Within each scheme, an EPC identifier can
>be
>   represented in a binary form or other forms such as URI.
>
>   The following list includes the above RFID types as well as
>various
>   other common identifiers and several different types of DUIDs.
>
>The organization of the text here seems to be poor -- section 3
>enumerates the new identifier types, but much of the text at the
>beginning of the section is about the RFID-EPC set of types.  It
>seems
>like a better organization is to use just paragraph 1 followed by
>table 1, and move paragraphs 2-5 into section 4.9.
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   including
>
>The text is using "Tag Data", "EPC", and "RFID" in a way that is
>intertwined but not explained.  I can see that it might be useful to
>use all of the terms if they commonly used in the field (don't forget
>to make them keywords for the RFC!), but you need to explain their
>connection and distinction to the reader or make it clear that the
>reader does not need to understand the differences among the terms.
>E.g., this formulation ties all three terms together
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   which are commonly used in RFID (radio-frequency identification)
>   applications, including
>
>--
>
>   For each RFID scheme except GID, there are two variations: a
>64-bit
>   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>has
>   only a 96-bit scheme.  Within each scheme, an EPC identifier can
>be
>   represented in a binary form or other forms such as URI.
>
>The text uses "scheme" to mean the distinction between encoding
>systems (GID, SGTIN, etc.) and and also to mean the distinction
>between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>It matters here, because you say "within each scheme ... can be
>represented in a binary form or ... URI".  Which meaning of "scheme"
>are you using here?  I thought you meant the second meaning when I
>first read the paragraph, but after reading external documents about
>EPC, I now understand that that last sentence uses "scheme" to in the
>first sense.
>
>You need to be clearer here that there are three representations
>used,
>64-bit binary, 96-bit binary, and URI (URN, actually), and
>representation is orthogonal to the seven RFID schemes, with the
>exception that RFID-GID does not have a 96-bit binary representation.
>
>I'm assuming that the Tag Data standard unambiguously defines the
>serialization of the binary representations as a sequence of octets.
>If it does not, this document MUST do that, or you will have an
>endless nightmare of byte-order problems.
>
>4.  Descriptions of MNID types
>
>Identifier ownership is a general concern -- it's worth mentioning
>for
>each type of identifier where the assigner of the identifier obtains
>delegation.  For an EUI, I expect the reader will assume that it's an
>EUI assigned to the device under IEEE rules, and similarly for RFID
>and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>I'm
>guessing that the DUID is one that is, or could be, used by the
>device
>for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>the IPv6 architecture doesn't assume that the association of
>addresses
>with devices is permanent.
>
>4.1.  Description of the IPv6 address type
>
>It would be good if the document described what the semantics of this
>ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>between that address and the device?  I suspect the connection is
>"the
>device has been configured to expect that it will be assigned this
>address as a long-term interface address", but there are other
>possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>prefix (there are plenty of them!) and then assigning addresses out
>of
>it simply to create a sequence of unique identifiers for devices, but
>not using those addresses on packets.
>
>Then again, perhaps you want to allow flexibility.  But in any case,
>I
>think you need to specify what the rules are for what address is
>associated with what device.
>
>4.2.  Description of the IMSI MNID type
>
>What does "in network order" mean here?  As far as I know, there is
>no
>defined "network order" for 4-bit quantities, only for dividing
>integers into octets and placing sequences of bits into octets.  I
>assume you mean that in any octet, the high-order 4 bits are the
>first
>digit and the low-order 4 bits are the second digit, but I think you
>need to state that explicitly.
>
>4.3.  Description of the EUI-48 address type
>
>   The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>   string containing the IEEE EUI-48 address.
>
>Is "string" the correct word, this not being a sequence of
>characters?
>I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>
>4.9.  Description of the RFID types
>
>This section needs to be revised.  It provides a lot of detail about
>the RFID types, but it's not enough detail for a reader who doesn't
>understand RFID to learn how any particular RFID scheme works.  E.g.,
>the first paragraph says that GID contains three fields in the first
>sentence, and that it contains four fields in the third sentence.
>Despite this, the description isn't enough to allow the reader to
>construct GID identifiers manually.
>
>On the other hand, readers who already understand the RFID schemes
>will find this text redundant.
>
>I think that almost all of this text can be replaced by references to
>the EPC documents, since these identifiers are opaque from the point
>of view of mobile identification.
>
>5.  Security Considerations
>
>The base MNID specification, RFC 4283, gives these security
>considerations (sec 4), which ought to be referenced and probably
>summarized in this section:
>
>   Moreover, MNIDs containing sensitive identifiers might only be
>used
>   for signaling during initial network entry.  Subsequent binding
>   update exchanges might then rely on a temporary identifier
>allocated
>   during the initial network entry, perhaps using mechanisms not
>   standardized within the IETF.  Managing the association between
>long-
>   lived and temporary identifiers is outside the scope of this
>   document.
>
>What is the meaning of the word "might" in paragraph 3?  I suspect
>that the purpose is to qualify this paragraph with "One way to
>address
>these vulnerabilities is to only use MNIDs containing ...".  But if
>that is the meaning, that expanded wording should be used.  Otherwise
>the text reads as if it is hypothetical.
>
>[END]
>
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm


From nobody Wed Feb  1 22:10:28 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0F1293E9; Wed,  1 Feb 2017 22:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.888
X-Spam-Level: 
X-Spam-Status: No, score=-5.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=0.001, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSdI3YHjkYf3; Wed,  1 Feb 2017 22:10:18 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9B541293EB; Wed,  1 Feb 2017 22:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486015817; bh=x3HXDok/hHhnrTVX8MxFMbwSR5qc/TAYBNkK DaTz6OA=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=Adjph8i HRWUukzM+PAZenxSiRoJEFlc43bMa1HkqlDDouUO/MPdOVURNH5dUTSVVgbMjmFbTBJ rxIdcBoI686HJqPukvthzIjuYVcm1GZupOJ3TYIk3LfcGfgAijAV0rtR38leIuuZtaw CrWIpE+W0qsbdXdtcuusMw+YmZxntKkWc3A+btJL8iCIIAYFfGpxLWVezbKMQuAciez RtMwc3Zcy+IA3jsPmG21scNDjVPli01/XNgK2ZCN5IAJR6tt+WBmAsMupJ/cx8fJmUt KKQCxcEzVvnIioUB4HTouqjapIzxvmCrNYZUD9I9ztdWoZC+CabM8pCI+7zHYgGT01A ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=TcBMIhJbMY+uEKw7mtmEWPKj0m3/5Y2qKUsT9+tgGvDAfKsU7bU/AKdFxcAyvUfh9cdwuMDV+D+HykCG2ZJbh0p3eR4zNCtt9fC6luKDR3dOrRqWdMiAMKsqeuoNq2dS8yv1slqAmG/grwXx/nVGSKfZtSw2C9gRalFohqfPKPSSXEbaJxkHYeEUld+9YA2jWF45i7yXqim5tpgwY/i75GAw9iAjKd/SiS8x8/ej0SSQuu8To6XmpFYFnsHEALJwkg3BgqY+pnuHu/Y3UDRKMthvjTmjoI0PloMJ6oLegvAivWHvTdHq1z7xljPobtV1gr7bWM6SQyPS3s4cxQ+Ugg==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1cZAb1-0000v3-7i; Thu, 02 Feb 2017 01:10:15 -0500
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
Date: Wed, 1 Feb 2017 22:10:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D4B7FC35.258902%sgundave@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac703c35547c62c55d8cd28b8f65ed96334350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CRE6BaqRm5draSU6A9OgyJ7BIo4>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 06:10:21 -0000

Hello Sri,

The review was indeed super.  I'll respond sometime in the next few days.

Regards,
Charlie P.


On 2/1/2017 9:09 PM, Sri Gundavelli (sgundave) wrote:
> Thank you Dale for a great review.
>
>
> Charlie/Authors - Can you please respond to Dale and address these
> comments.
>
>
> Regards
> Sri
>
>
> On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
> on behalf of worley@ariadne.com> wrote:
>
>> Reviewer: Dale Worley
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft.  The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Document:  draft-ietf-dmm-4283mnids-04
>> Reviewer:  Dale R. Worley
>> Review Date:  31 Jan 2017
>> IETF LC End Date:  2 Feb 2017
>> IESG Telechat date:  16 Feb 2017
>>
>> Summary:
>>
>>        This draft is on the right track but has open issues,
>> described
>>        in the review.
>>
>> Technical issues:
>>
>> 1. The Introduction states
>>
>>    Other types of identifiers are in
>>    common use, and even referenced in RFC 4283.
>>
>> For the reader's sanity, some sort of accounting needs to be made of
>> these "other types of identifiers", especially because each type of
>> identifier needs an identifier type number.  The text in 4283 is
>>
>>    Some examples of identifiers
>>    include Network Access Identifier (NAI), Fully Qualified Domain
>> Name
>>    (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>>    Subscriber Number (MSISDN).
>>
>> Are there any other types "in common use"?
>>
>> - NAI (type 1) is defined by 4283.
>> - Fully Qualified Domain Name (FQDN) seems not to be specified
>> - International Mobile Station Identifier (IMSI) (type 3) is defined
>> in
>>   this draft
>> - Mobile Subscriber Number (MSISDN) seems not to be specified
>>
>> 2. Is it intended to have an IMEI identifier type?  The introduction
>> mentions an IMEI type, but there is no specification for it, nor is
>> there an identifier type number assigned for it.
>>
>>    ... types for IMSI
>>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>> GUTI
>>    [ThreeGPP-IDS].
>>
>> Initially I suspected it was it was present in an earlier revision
>> and
>> then later deleted without this reference being updated.  But all
>> versions of draft-ietf-dmm-4283mnids and its predecessor
>> draft-perkins-dmm-4283mnids mention IMEI in this way as one
>> identifier
>> type, but none specify it in any way.  The only discussion I can find
>> on the DMM mailing list of IMEI is:
>>
>>    
>> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>> =d29575f767ce67a1e67a7767008ee6af
>>
>>     From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>>     To: DMM
>>     Date: Wed, 10 September 2014 13:29 UTC
>>     Re: [DMM] regarding the re-chartering..
>>
>>     It seems the MNID is somehow overloaded to carry both,
>> node-specific
>>     IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>>     There may be value in adding the IMEI to the list of possible
>> types of
>>     node-specific IDs.
>>
>> Either the presence of IMEI in this list is a simple mistake that has
>> persisted in all versions of the draft, or specifying IMEI has always
>> been intended but has always been overlooked.
>>
>> 3. The definition of identifier types for both EUI-48 and EUI-64
>> suggests that it might be desirable to define an identifier type for
>> arbitrary hardware (link-level) addresses.  It seems that the natural
>> differentiator for that purpose is the "hardware type" used in ARP,
>> so
>> a EUI-48 address would be represented as
>>
>>     MN identifier type (one octet) 5 (say)
>>     hardware type (two octets) 1
>>     EUI-48 (six octets)
>>
>> and an EUI-64 similarly, with hardware type 27.
>>
>> Although with only two subtypes in common use, generalizing this
>> might
>> not be worth the effort.
>>
>> 4. Several of the identifier types can be represented as URNs:
>>
>> - IMEI can be represented as a URN as urn:gsma:imei:...
>> - all of the RFID types have a URN representation (called the
>>   "pure-identity URI" in the RFID specifications), which starts
>>   urn:epc:id:...
>>
>> Since all URN types are ensured of being unique and persistent, it
>> seems that we could define a MNID type for URNs generally, and then
>> any RFID URI or an IMEI (as a URN) could be used as a value of that
>> type.
>>
>> If this idea is adopted, it seems that the other 3GPP types (IMSI,
>> P-TMSI, and GUTI) should be given defined encodings as URNs in new
>> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>> of IMEIs defined in RFC 7254.
>>
>> This consolidation could be significantly beneficial.  It allows MNID
>> to use any URN scheme as an identifier.  It reduces the three
>> different RFID representations to one.  It incorporates any future
>> expansion of RFID schemes (because all schemes will have a
>> pure-identity URN representation).  A disadvantage is that the URN
>> encodings are long, but the security considerations section states
>> that MNIDs are used only on the first registration at the home agent,
>> so there isn't much need for brevity.
>>
>> Similarly, this approach incorporates any future expansion of mobile
>> identifiers that GSMA decides to define, as long as GSMA provides a
>> URN representation for it.
>>
>> The most significant disadvantage is that some URN schemes allow
>> several character strings to "mean" the same URN.  In most URN
>> schemes, the allowed variation is limited to the case of letters, and
>> the common convention is to always use lower-case when there is a
>> choice, leading to a unique conventional canonical form for the URN.
>>
>> 5. Regarding the encoding of a string of digits into octets, it is
>> stated that "The last digit MUST be zero padded, if needed, for full
>> octet size."  This seems very unwise unless there is a 3GPP decree
>> that if a zero is appended to a valid IMSI, the resulting string is
>> never a valid IMSI.  Instead, I would specify that padding is by
>> filling the low-order 4 bits of the final octet with 0xF.  That
>> ensures that the encoding can be uniquely decoded into an IMSI.
>>
>> 6. There are four types of DUID specified, each with a distinct MNID
>> value.  However, DUIDs contain an initial two-octet type field which
>> distinguishes the various types of DUID, so providing them with
>> distinct MNID values is redundant.
>>
>> Distinguishing the types and allowing only four of them to be used as
>> MNIDs seems to be contrary to the philosophy of DUID construction
>> (RFC
>> 3315 section 9):
>>
>>    Clients and servers MUST treat DUIDs as opaque values and MUST
>> only
>>    compare DUIDs for equality.  Clients and servers MUST NOT in any
>>    other way interpret DUIDs.  Clients and servers MUST NOT restrict
>>    DUIDs to the types defined in this document, as additional DUID
>> types
>>    may be defined in the future.
>>
>> Of course, MNID isn't a DHCP operation, so it isn't subject to those
>> requirements, but I expect that devices will use the same DUID for
>> both mobile identification, and we don't want mobile identification
>> to
>> restrict future developments of DHCP.
>>
>> I think this specification must treat DUIDs as opaque and use only
>> one
>> MNID type that allows all types of DUIDs as values.
>>
>> Editorial issues:
>>
>> Abstract
>>
>>    Additional Identifier Types are proposed for use with the Mobile
>> Node
>>    Identifier Option for IPv6 (RFC 4283).
>>
>> s/proposed/defined/
>> This document will define the new types (once it is approved)!
>>
>> 1.  Introduction
>>
>>    ... types for IMSI
>>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>> GUTI
>>    [ThreeGPP-IDS].
>>
>> There is no description of P-TMSI identifiers, although it is
>> assigned
>> identifier type 4.
>>
>> There is no description of GUTI identifiers, although it is assigned
>> identifier type 7.
>>
>> 3.  New Mobile Node Identifier Types
>>
>>    The following types of identifiers are commonly used to identify
>>    mobile nodes.  For each type, references are provided with full
>>    details on the format of the type of identifier.
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    including
>>
>>    o  RFID-GID (Global Identifier),
>>    o  RFID-SGTIN (Serialized Global Trade Item Number),
>>    o  RFID-SSCC (Serial Shipping Container),
>>    o  RFID-SGLN (Global Location Number),
>>    o  RFID-GRAI (Global Returnable Asset Identifier),
>>    o  RFID-DOD (Department of Defense ID), and
>>    o  RFID-GIAI (Global Individual Asset Identifier).
>>
>>    For each RFID scheme except GID, there are two variations: a
>> 64-bit
>>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>> has
>>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>> be
>>    represented in a binary form or other forms such as URI.
>>
>>    The following list includes the above RFID types as well as
>> various
>>    other common identifiers and several different types of DUIDs.
>>
>> The organization of the text here seems to be poor -- section 3
>> enumerates the new identifier types, but much of the text at the
>> beginning of the section is about the RFID-EPC set of types.  It
>> seems
>> like a better organization is to use just paragraph 1 followed by
>> table 1, and move paragraphs 2-5 into section 4.9.
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    including
>>
>> The text is using "Tag Data", "EPC", and "RFID" in a way that is
>> intertwined but not explained.  I can see that it might be useful to
>> use all of the terms if they commonly used in the field (don't forget
>> to make them keywords for the RFC!), but you need to explain their
>> connection and distinction to the reader or make it clear that the
>> reader does not need to understand the differences among the terms.
>> E.g., this formulation ties all three terms together
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    which are commonly used in RFID (radio-frequency identification)
>>    applications, including
>>
>> --
>>
>>    For each RFID scheme except GID, there are two variations: a
>> 64-bit
>>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>> has
>>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>> be
>>    represented in a binary form or other forms such as URI.
>>
>> The text uses "scheme" to mean the distinction between encoding
>> systems (GID, SGTIN, etc.) and and also to mean the distinction
>> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>> It matters here, because you say "within each scheme ... can be
>> represented in a binary form or ... URI".  Which meaning of "scheme"
>> are you using here?  I thought you meant the second meaning when I
>> first read the paragraph, but after reading external documents about
>> EPC, I now understand that that last sentence uses "scheme" to in the
>> first sense.
>>
>> You need to be clearer here that there are three representations
>> used,
>> 64-bit binary, 96-bit binary, and URI (URN, actually), and
>> representation is orthogonal to the seven RFID schemes, with the
>> exception that RFID-GID does not have a 96-bit binary representation.
>>
>> I'm assuming that the Tag Data standard unambiguously defines the
>> serialization of the binary representations as a sequence of octets.
>> If it does not, this document MUST do that, or you will have an
>> endless nightmare of byte-order problems.
>>
>> 4.  Descriptions of MNID types
>>
>> Identifier ownership is a general concern -- it's worth mentioning
>> for
>> each type of identifier where the assigner of the identifier obtains
>> delegation.  For an EUI, I expect the reader will assume that it's an
>> EUI assigned to the device under IEEE rules, and similarly for RFID
>> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>> I'm
>> guessing that the DUID is one that is, or could be, used by the
>> device
>> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>> the IPv6 architecture doesn't assume that the association of
>> addresses
>> with devices is permanent.
>>
>> 4.1.  Description of the IPv6 address type
>>
>> It would be good if the document described what the semantics of this
>> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>> between that address and the device?  I suspect the connection is
>> "the
>> device has been configured to expect that it will be assigned this
>> address as a long-term interface address", but there are other
>> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>> prefix (there are plenty of them!) and then assigning addresses out
>> of
>> it simply to create a sequence of unique identifiers for devices, but
>> not using those addresses on packets.
>>
>> Then again, perhaps you want to allow flexibility.  But in any case,
>> I
>> think you need to specify what the rules are for what address is
>> associated with what device.
>>
>> 4.2.  Description of the IMSI MNID type
>>
>> What does "in network order" mean here?  As far as I know, there is
>> no
>> defined "network order" for 4-bit quantities, only for dividing
>> integers into octets and placing sequences of bits into octets.  I
>> assume you mean that in any octet, the high-order 4 bits are the
>> first
>> digit and the low-order 4 bits are the second digit, but I think you
>> need to state that explicitly.
>>
>> 4.3.  Description of the EUI-48 address type
>>
>>    The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>>    string containing the IEEE EUI-48 address.
>>
>> Is "string" the correct word, this not being a sequence of
>> characters?
>> I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>>
>> 4.9.  Description of the RFID types
>>
>> This section needs to be revised.  It provides a lot of detail about
>> the RFID types, but it's not enough detail for a reader who doesn't
>> understand RFID to learn how any particular RFID scheme works.  E.g.,
>> the first paragraph says that GID contains three fields in the first
>> sentence, and that it contains four fields in the third sentence.
>> Despite this, the description isn't enough to allow the reader to
>> construct GID identifiers manually.
>>
>> On the other hand, readers who already understand the RFID schemes
>> will find this text redundant.
>>
>> I think that almost all of this text can be replaced by references to
>> the EPC documents, since these identifiers are opaque from the point
>> of view of mobile identification.
>>
>> 5.  Security Considerations
>>
>> The base MNID specification, RFC 4283, gives these security
>> considerations (sec 4), which ought to be referenced and probably
>> summarized in this section:
>>
>>    Moreover, MNIDs containing sensitive identifiers might only be
>> used
>>    for signaling during initial network entry.  Subsequent binding
>>    update exchanges might then rely on a temporary identifier
>> allocated
>>    during the initial network entry, perhaps using mechanisms not
>>    standardized within the IETF.  Managing the association between
>> long-
>>    lived and temporary identifiers is outside the scope of this
>>    document.
>>
>> What is the meaning of the word "might" in paragraph 3?  I suspect
>> that the purpose is to qualify this paragraph with "One way to
>> address
>> these vulnerabilities is to only use MNIDs containing ...".  But if
>> that is the meaning, that expanded wording should be used.  Otherwise
>> the text reads as if it is hypothetical.
>>
>> [END]
>>
>>
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>


From nobody Wed Feb  1 22:42:29 2017
Return-Path: <roni.even@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEA3127735; Wed,  1 Feb 2017 22:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level: 
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82R8R46u_R0i; Wed,  1 Feb 2017 22:42:25 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E548127078; Wed,  1 Feb 2017 22:42:24 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFQ60273; Thu, 02 Feb 2017 06:42:20 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 2 Feb 2017 06:42:18 +0000
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by nkgeml411-hub.china.huawei.com (10.98.56.70) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 2 Feb 2017 14:42:14 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.117]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0301.000; Thu, 2 Feb 2017 14:42:10 +0800
From: Roni Even <roni.even@huawei.com>
To: tianxiang li <peter416733@gmail.com>
Thread-Topic: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
Thread-Index: AQHSfKMEGC59Kqb/I0a0hf43svJnhaFVREvg
Date: Thu, 2 Feb 2017 06:42:09 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com> <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
In-Reply-To: <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.201.150]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5892D4CD.030D, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.117, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c1ff7e23a5fb1d24d3ae21aa07c5b874
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dN3Mmu8JAj8f1hx6BTln4BSGvXg>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 06:42:27 -0000

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQpJIHdpbGwgbGVhdmUgb25seSB0aGUgaXRlbXMgdGhhdCBuZWVkZWQgbXkgcmVzcG9uc2UN
Cg0KNy4gICAgICBJbiBzZWN0aW9uIDMuNCDigJxJZiB0aGUgY2xpZW50IGRlY2lkZWQgdG8gdXNl
ICB0aGUgcHJlZml4IHByb3ZpZGVkDQpieSB0aGUgc2VydmVyIGRlc3BpdGUgYmVpbmcgbG9uZ2Vy
IHRoYW4gdGhlICBwcmVmaXgtbGVuZ3RoIGhpbnTigJ0geWV0IEkNCmRpZCBub3Qgc2VlIGluIHNl
Y3Rpb24gMy4yIHRoYXQgdGhlIHNlcnZlciBjYW4gcHJvdmlkZSBhIGxvbmdlcg0KcHJlZml4Lg0K
DQpbVGlhbnhpYW5nXSBUaGlzIHdhcyBtZW50aW9uZWQgaW4gdGhlIGxhc3Qgc2VudGVuY2Ugb2Yg
c2VjdGlvbiAzLjI6DQoNCiJJZiB0aGUgcmVxdWVzdGVkIHByZWZpeCBpcyBub3QgYXZhaWxhYmxl
IGluIHRoZSBzZXJ2ZXIncyBwcmVmaXggcG9vbCwgYW5kIHRoZSBjbGllbnQgYWxzbyBpbmNsdWRl
ZCBhIHByZWZpeC1sZW5ndGggaGludCBpbiB0aGUgc2FtZSBJQV9QRCBvcHRpb24sIHRoZW4gdGhl
IHNlcnZlciBTSE9VTEQgdHJ5IHRvIHByb3ZpZGUgYSBwcmVmaXggbWF0Y2hpbmcgdGhlIHByZWZp
eC1sZW5ndGggdmFsdWUsIG9yIHRoZSBwcmVmaXggd2l0aCB0aGUgc2hvcnRlc3QgbGVuZ3RoIHBv
c3NpYmxlIHdoaWNoIGlzIGNsb3Nlc3QgdG8gdGhlIHByZWZpeC1sZW5ndGggaGludCB2YWx1ZS4i
DQpbUm9uaSBFdmVuXSBJIHVuZGVyc3Rvb2QgZnJvbSAzLjIgdGhhdCBpdCBzaG91bGQgcHJvdmlk
ZSBhIHNob3J0ZXIgbGVuZ3RoIHByZWZpeCAgY2xvc2VyIHRvIHRoZSByZXF1ZXN0IG1heWJlIOKA
nG9yIHRoZSBwcmVmaXggd2l0aCB0aGUgY2xvc2VzdCBwb3NzaWJsZSBsZW5ndGggdG8gdGhlIHBy
ZWZpeC1sZW5ndGggaGludCB2YWx1ZeKAnQ0KDQpbVGlhbnhpYW5nMl0gVGhlIG9yaWdpbmFsIHNl
bnRlbmNlIHdhcyBhIGJpdCBjb25mdXNpbmcsIHBlcmhhcHMgd2UgY291bGQgY2hhbmdlIGl0IGxp
a2UgdGhpczoNCg0KT0xEOiAiSWYgdGhlIHJlcXVlc3RlZCBwcmVmaXggaXMgbm90IGF2YWlsYWJs
ZSBpbiB0aGUgc2VydmVyJ3MgcHJlZml4IHBvb2wsIGFuZCB0aGUgY2xpZW50IGFsc28gaW5jbHVk
ZWQgYSBwcmVmaXgtbGVuZ3RoIGhpbnQgaW4gdGhlIHNhbWUgSUFfUEQgb3B0aW9uLCB0aGVuIHRo
ZSBzZXJ2ZXIgU0hPVUxEIHRyeSB0byBwcm92aWRlIGEgcHJlZml4IG1hdGNoaW5nIHRoZSBwcmVm
aXgtbGVuZ3RoIHZhbHVlLCBvciB0aGUgcHJlZml4IHdpdGggdGhlIHNob3J0ZXN0IGxlbmd0aCBw
b3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUu
Ig0KDQpORVc6IklmIHRoZSByZXF1ZXN0ZWQgcHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhl
IHNlcnZlcidzIHByZWZpeCBwb29sLCBhbmQgdGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJl
Zml4LWxlbmd0aCBoaW50IGluIHRoZSBzYW1lIElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVy
IFNIT1VMRCBwcm92aWRlIGEgcHJlZml4IG1hdGNoaW5nIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQs
IG9yIGEgcHJlZml4IHdoaWNoIGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBw
b3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5v
dCBwcm92aWRlIGEgcHJlZml4IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRo
ZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZp
eCB3aGljaCBsZW5ndGggaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUg
cHJlZml4LWxlbmd0aCBoaW50LiINCg0KW1JvbmkgRXZlbl0gSSBoYXZlIG5vIHByb2JsZW0gd2l0
aCB0aGlzIHRleHQgc2luY2UgaXQgd2lsbCBhbHNvIHdvcmsgd2l0aCB0aGUgcmVzdCBvZiB0aGUg
ZG9jdW1lbnQgYnV0IGlzIGl0IHdoYXQgd2FzIHJlYWxseSBtZWFudA0KDQpBbHNvIGEgbml0DQoN
CuKAnG9yIGEgcHJlZml4IHdoaWNoIGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBh
cyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxk
IG5vdCBwcm92aWRlIGEgcHJlZml4IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRv
IHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHBy
ZWZpeCB3aGljaCBsZW5ndGggaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0
aGUgcHJlZml4LWxlbmd0aCBoaW504oCdDQoNCnRvDQoNCuKAnG9yIGEgcHJlZml4IHdob3NlIGxl
bmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxl
bmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4IHdpdGgg
YSBzaG9ydGVyIG9yIGVxdWFsIGxlbmd0aCAgdG8gdGhlIHByZWZpeC1sZW5ndGggaGludCwgdGhl
IHNlcnZlciBTSE9VTEQgcHJvdmlkZSBhIHByZWZpeCB3aG9zZSBsZW5ndGggaXMgbG9uZ2VyIGFu
ZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW504oCdDQoNCg0K
W1RpYW54aWFuZ10gVGhlIGlkZWEgd2FzIHRvIGxpc3QgYWxsIHRoZSBvcHRpb25zLCBhbmQgZGlz
Y3VzcyB0aGVpciBjb25zZXF1ZW5jZXMuIEFuZCB0aGUgc2VydmVyIGNvdWxkIGRlY2lkZSB3aGlj
aCBvcHRpb24gdG8gdXNlIGRlcGVuZGluZyBvbiBpdHMgcG9saWN5Lg0KDQpPcHRpb24gMyBhdm9p
ZHMgdGhlIGNvbXBsZXhpdHkgb2YgaGFuZGxpbmcgbXVsdGlwbGUgZGVsZWdhdGVkIHByZWZpeGVz
LCBkZXNwaXRlIG9mIGJyZWFraW5nIHVwIGFsbCBjb25uZWN0aW9ucy4gT3B0aW9uIDQgYWxsb3dz
IHRvIHNlcnZlciB0byBjb25maWd1cmUgYSB2YWxpZC1saWZldGltZSBmb3IgdGhlIG9sZCBwcmVm
aXggZGVwZW5kaW5nIG9uIGFjdHVhbCByZXF1aXJlbWVudHMsIHJhdGhlciB0aGFuIGxldCB0aGUg
b2xkIHByZWZpeCBleHBpcmUgb24gaXRzIG93bi4NCltSb25pIEV2ZW5dIE9LLCBzdGlsbCBvcHRp
b24gNCBtYXkgaGF2ZSBzaW1pbGFyIHJlc3VsdCB0byAzIHNpbmNlIOKAnGEgc2hvcnQgbm9uLXpl
cm/igJ0gbWF5IGJlIHRvbyBzaG9ydC4gV2h5IG5vdCBhZGQgYSByZWNvbW1lbmRlZCB2YWx1ZT8N
Cg0KW1RpYW54aWFuZzJdIEFncmVlLCBhcyB0aGlzIG1heSB2YXJ5IGZvciBkaWZmZXJlbnQgc2Vy
dmljZXMsIHdlIGNvdWxkIGNoYW5nZSB0aGUgdGV4dCB0byBzYXkgImEgc3BlY2lmaWMgdmFsaWQt
bGlmZXRpbWUgZGVwZW5kaW5nIG9uIHRoZSBhY3R1YWwgcmVxdWlyZW1lbnQiLg0KW1JvbmkgRXZl
bl0gT0sNCg0KDQoNCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQoNCg0KDQo=

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiO30NCnNwYW4ubS02MDYwNzI2OTc5NTM2MDAzMTE5Z21haWwtbS02NTI0ODAyMTEyMjA3
MDQ5MjQ2Z21haWwtDQoJe21zby1zdHlsZS1uYW1lOm1fLTYwNjA3MjY5Nzk1MzYwMDMxMTlnbWFp
bC1tXy02NTI0ODAyMTEyMjA3MDQ5MjQ2Z21haWwtO30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJ
e21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhv
bWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u
bHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBXb3JkU2Vj
dGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIu
MHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0t
Pjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0
PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4
dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4N
CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SGksPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkkgd2lsbCBsZWF2ZSBvbmx5IHRoZSBpdGVtcyB0aGF0IG5lZWRlZCBteSBy
ZXNwb25zZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
cmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj43LiZuYnNwOyAmbmJzcDsgJm5ic3A7IElu
IHNlY3Rpb24gMy40IOKAnElmIHRoZSBjbGllbnQgZGVjaWRlZCB0byB1c2UmbmJzcDsgdGhlIHBy
ZWZpeCBwcm92aWRlZDxicj4NCmJ5IHRoZSBzZXJ2ZXIgZGVzcGl0ZSBiZWluZyBsb25nZXIgdGhh
biB0aGUmbmJzcDsgcHJlZml4LWxlbmd0aCBoaW504oCdIHlldCBJPGJyPg0KZGlkIG5vdCBzZWUg
aW4gc2VjdGlvbiAzLjIgdGhhdCB0aGUgc2VydmVyIGNhbiBwcm92aWRlIGEgbG9uZ2VyPGJyPg0K
cHJlZml4LjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPltUaWFueGlhbmddIFRoaXMgd2FzIG1lbnRpb25lZCBpbiB0aGUgbGFz
dCBzZW50ZW5jZSBvZiBzZWN0aW9uIDMuMjombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZxdW90O0lmIHRoZSByZXF1ZXN0ZWQg
cHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhlIHNlcnZlcidzIHByZWZpeCBwb29sLCBhbmQg
dGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJlZml4LWxlbmd0aCBoaW50IGluIHRoZSBzYW1l
IElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVyIFNIT1VMRCB0cnkgdG8NCiBwcm92aWRlIGEg
cHJlZml4IG1hdGNoaW5nIHRoZSBwcmVmaXgtbGVuZ3RoIHZhbHVlLCBvciB0aGUgcHJlZml4IHdp
dGggdGhlIHNob3J0ZXN0IGxlbmd0aCBwb3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0IHRvIHRoZSBw
cmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxiPjxpPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5bUm9uaSBFdmVuXSBJIHVuZGVyc3Rvb2QgZnJvbSAzLjIgdGhhdCBpdCBzaG91bGQgcHJv
dmlkZSBhIHNob3J0ZXIgbGVuZ3RoIHByZWZpeCAmbmJzcDtjbG9zZXIgdG8NCiB0aGUgcmVxdWVz
dCBtYXliZSDigJw8L3NwYW4+PC9pPjwvYj5vciB0aGUgcHJlZml4IHdpdGggdGhlIGNsb3Nlc3Qg
cG9zc2libGUgbGVuZ3RoIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWXigJ08bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5b
VGlhbnhpYW5nMl0gVGhlIG9yaWdpbmFsIHNlbnRlbmNlIHdhcyBhIGJpdCBjb25mdXNpbmcsIHBl
cmhhcHMgd2UgY291bGQgY2hhbmdlIGl0IGxpa2UgdGhpczo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T0xEOiZuYnNwOyZxdW90O0lmIHRoZSBy
ZXF1ZXN0ZWQgcHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhlIHNlcnZlcidzIHByZWZpeCBw
b29sLCBhbmQgdGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJlZml4LWxlbmd0aCBoaW50IGlu
IHRoZSBzYW1lIElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVyIFNIT1VMRCB0cnkgdG8gcHJv
dmlkZSBhIHByZWZpeCBtYXRjaGluZyB0aGUgcHJlZml4LWxlbmd0aCB2YWx1ZSwgb3INCiB0aGUg
cHJlZml4IHdpdGggdGhlIHNob3J0ZXN0IGxlbmd0aCBwb3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0
IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUuJnF1b3Q7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5FVzomcXVvdDtJZiB0aGUgcmVx
dWVzdGVkIHByZWZpeCBpcyBub3QgYXZhaWxhYmxlIGluIHRoZSBzZXJ2ZXIncyBwcmVmaXggcG9v
bCwgYW5kIHRoZSBjbGllbnQgYWxzbyBpbmNsdWRlZCBhIHByZWZpeC1sZW5ndGggaGludCBpbiB0
aGUgc2FtZSBJQV9QRCBvcHRpb24sIHRoZW4gdGhlIHNlcnZlciBTSE9VTEQgcHJvdmlkZSBhIHBy
ZWZpeCBtYXRjaGluZyB0aGUgcHJlZml4LWxlbmd0aCBoaW50LCBvciBhIHByZWZpeA0KIHdoaWNo
IGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJl
Zml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4
IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhp
bnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZpeCB3aGljaCBsZW5ndGggaXMg
bG9uZ2VyIGFuZCBhcyBjbG9zZSBhcw0KIHBvc3NpYmxlIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhp
bnQuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+W1JvbmkgRXZlbl0gSSBoYXZlIG5vIHBy
b2JsZW0gd2l0aCB0aGlzIHRleHQgc2luY2UgaXQgd2lsbCBhbHNvIHdvcmsgd2l0aCB0aGUgcmVz
dCBvZiB0aGUgZG9jdW1lbnQgYnV0IGlzIGl0IHdoYXQgd2FzIHJlYWxseSBtZWFudDxvOnA+PC9v
OnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFsc28gYSBuaXQ8bzpwPjwvbzpwPjwvc3Bh
bj48L2k+PC9iPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxpPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2k+
PC9iPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPuKAnG9yIGEgcHJlZml4IHdoaWNoIGlzIGxl
bmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxl
bmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4IHdoaWNo
IGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRo
ZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZpeCB3aGljaA0KIGxlbmd0aCBpcyBsb25n
ZXIgYW5kIGFzIGNsb3NlIGFzIHBvc3NpYmxlIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnTigJ08
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+dG88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+4oCcb3Ig
YSBwcmVmaXggd2hvc2UgbGVuZ3RoIGlzIHNob3J0ZXIgYW5kIGFzIGNsb3NlIGFzIHBvc3NpYmxl
IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQuIElmIHRoZSBzZXJ2ZXIgY291bGQgbm90IHByb3Zp
ZGUgYSBwcmVmaXggd2l0aCBhIHNob3J0ZXIgb3IgZXF1YWwgbGVuZ3RoICZuYnNwO3RvIHRoZSBw
cmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgYSBwcmVmaXggd2hv
c2UgbGVuZ3RoDQogaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJl
Zml4LWxlbmd0aCBoaW504oCdPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAw
Y20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPltUaWFueGlhbmddIFRoZSBpZGVhIHdhcyB0
byBsaXN0IGFsbCB0aGUgb3B0aW9ucywgYW5kIGRpc2N1c3MgdGhlaXIgY29uc2VxdWVuY2VzLiBB
bmQgdGhlIHNlcnZlciBjb3VsZCBkZWNpZGUgd2hpY2ggb3B0aW9uIHRvIHVzZSBkZXBlbmRpbmcg
b24gaXRzIHBvbGljeS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPk9wdGlvbiAzIGF2b2lkcyB0aGUgY29tcGxleGl0eSBvZiBo
YW5kbGluZyBtdWx0aXBsZSBkZWxlZ2F0ZWQgcHJlZml4ZXMsIGRlc3BpdGUgb2YgYnJlYWtpbmcg
dXAgYWxsIGNvbm5lY3Rpb25zLiBPcHRpb24gNCBhbGxvd3MgdG8gc2VydmVyIHRvIGNvbmZpZ3Vy
ZSBhIHZhbGlkLWxpZmV0aW1lIGZvciB0aGUgb2xkDQogcHJlZml4IGRlcGVuZGluZyBvbiBhY3R1
YWwgcmVxdWlyZW1lbnRzLCByYXRoZXIgdGhhbiBsZXQgdGhlIG9sZCBwcmVmaXggZXhwaXJlIG9u
IGl0cyBvd24uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPjxpPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5bUm9uaSBFdmVuXSBPSywg
c3RpbGwgb3B0aW9uIDQgbWF5IGhhdmUgc2ltaWxhciByZXN1bHQgdG8gMyBzaW5jZSDigJxhIHNo
b3J0IG5vbi16ZXJv4oCdIG1heSBiZQ0KIHRvbyBzaG9ydC4gV2h5IG5vdCBhZGQgYSByZWNvbW1l
bmRlZCB2YWx1ZT88L3NwYW4+PC9pPjwvYj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5bVGlhbnhpYW5nMl0gQWdyZWUsIGFzIHRoaXMgbWF5IHZhcnkgZm9y
IGRpZmZlcmVudCBzZXJ2aWNlcywgd2UgY291bGQgY2hhbmdlIHRoZSB0ZXh0IHRvIHNheSAmcXVv
dDthIHNwZWNpZmljIHZhbGlkLWxpZmV0aW1lIGRlcGVuZGluZyBvbiB0aGUgYWN0dWFsIHJlcXVp
cmVtZW50JnF1b3Q7LiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPltSb25pIEV2
ZW5dIE9LPC9zcGFuPjwvaT48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1i
b3R0b206MTIuMHB0Ij48YnI+DQo8YnI+DQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czo8YnI+DQo8
YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_--


From nobody Thu Feb  2 07:26:09 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79ACD12946D; Thu,  2 Feb 2017 07:26:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqguKZ3bEL2p; Thu,  2 Feb 2017 07:26:03 -0800 (PST)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17AC2129457; Thu,  2 Feb 2017 07:26:03 -0800 (PST)
Received: by mail-ot0-x22e.google.com with SMTP id f9so14190592otd.1; Thu, 02 Feb 2017 07:26:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DnF+s4vIkTb7fBFANeAtifhEqUtodV4CLlUYBpBZ9DM=; b=EnYUbYoIXvZn9mq5UPZ8uPAbZsooOixyLXPRRyWv89QRbsf6ICrWH/EucCzvXsTnk5 RuksITqGSVU7z4eSR9MDCLWPohw3e2xI4zd3zMqlQYlHOa+ouDJR8sp9IudaFUGhGbGu 5WQOKjJvHzkUxODHO/xjcAG03cY6sI3sY4XjWpcOGDMhRCPBrslxRU+B+O2+tMedm4YX XK6M+lP5YRj/iTEKcoULSAQNSQwq0/uJyCFG30ZTblm8cgByZDYnq1Hw/RdrR9O2TQXh S8LCHXUy6kjAURyo9xCiWABvFcxEu9W5SLYVwfossitw1i1RhO4hznjUDEmPQqGf/cY6 Y07Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DnF+s4vIkTb7fBFANeAtifhEqUtodV4CLlUYBpBZ9DM=; b=Pi/C7EOa1LZIVaLRIEUoRcUG/XaizSpvavV4aMPGfm15s8YtPnHSJw2WxDfuyiSVlv r5YYaZ8cx8SntJt0l+xlDmUao2zx+e6TroCjJcd7hPe9xqlj1+PJ6SujJLRIs3LmX6rB nfqAmaTKQgt/YAPm8mFJWm5PPXV8izMttnosSPufTVAUzp+ZRDihFmwA6tglFXuS48Ub 2lxpB0RTCv/z7Dke5RJ/KruCGAMkTp0terXJTLkvJzIbZiMxShcWPfeeqf15PCxu3MaR m5bNQTxFQZRgnU4AqZMkbk5oFUgGVyaftrlluDELxNSh60S6t8ujXVPoYHp9HCoxK3cX S68Q==
X-Gm-Message-State: AMke39llhjmuR/0ba06CoHmy9S5aIfn5/6xzkzLsKVPnUDYWudZwzD84B3F0VLlyLlusqpD8lLz7tjzafkJUsg==
X-Received: by 10.157.60.149 with SMTP id z21mr4074859otc.34.1486049162280; Thu, 02 Feb 2017 07:26:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Thu, 2 Feb 2017 07:25:21 -0800 (PST)
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com> <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
From: tianxiang li <peter416733@gmail.com>
Date: Thu, 2 Feb 2017 23:25:21 +0800
Message-ID: <CAFx+hEOc_U4uPGYsE9whndfF3dyoiZxLxHoH+uaxCJ6McAq4_Q@mail.gmail.com>
To: Roni Even <roni.even@huawei.com>
Content-Type: multipart/alternative; boundary=94eb2c19018e6fc61805478dc8b4
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-wND_fyAfAzzbdXbd9kJEg2K4sE>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 15:26:04 -0000

--94eb2c19018e6fc61805478dc8b4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Roni,

Thank you for comments, we'll add the changes to the document in our next
updated version.
Please see inline.

Cheers,
Tianxiang

2017-02-02 14:42 GMT+08:00 Roni Even <roni.even@huawei.com>:

> Hi,
>
> I will leave only the items that needed my response
>
>
>
> 7.      In section 3.4 =E2=80=9CIf the client decided to use  the prefix =
provided
> by the server despite being longer than the  prefix-length hint=E2=80=9D =
yet I
> did not see in section 3.2 that the server can provide a longer
> prefix.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2:
>
>
>
> "If the requested prefix is not available in the server's prefix pool, an=
d
> the client also included a prefix-length hint in the same IA_PD option,
> then the server SHOULD try to provide a prefix matching the prefix-length
> value, or the prefix with the shortest length possible which is closest t=
o
> the prefix-length hint value."
>
> *[Roni Even] I understood from 3.2 that it should provide a shorter lengt=
h
> prefix  closer to the request maybe =E2=80=9C*or the prefix with the clos=
est
> possible length to the prefix-length hint value=E2=80=9D
>
>
>
> [Tianxiang2] The original sentence was a bit confusing, perhaps we could
> change it like this:
>
>
>
> OLD: "If the requested prefix is not available in the server's prefix
> pool, and the client also included a prefix-length hint in the same IA_PD
> option, then the server SHOULD try to provide a prefix matching the
> prefix-length value, or the prefix with the shortest length possible whic=
h
> is closest to the prefix-length hint value."
>
>
>
> NEW:"If the requested prefix is not available in the server's prefix pool=
,
> and the client also included a prefix-length hint in the same IA_PD optio=
n,
> then the server SHOULD provide a prefix matching the prefix-length hint, =
or
> a prefix which is length is shorter and as close as possible to the
> prefix-length hint. If the server could not provide a prefix which length
> is shorter or equal to the prefix-length hint, the server SHOULD provide
> the prefix which length is longer and as close as possible to the
> prefix-length hint."
>
>
>
> *[Roni Even] I have no problem with this text since it will also work wit=
h
> the rest of the document but is it what was really meant*
>
>
>
[Tianxiang3] This was the intended meaning of the original sentence, if the
server could not honor the hint, it should provide a prefix closest to the
hint, the client could then decide whether to accept or neglect this prefix=
.


> *Also a nit*
>
>
>
> =E2=80=9Cor a prefix which is length is shorter and as close as possible =
to the
> prefix-length hint. If the server could not provide a prefix which length
> is shorter or equal to the prefix-length hint, the server SHOULD provide
> the prefix which length is longer and as close as possible to the
> prefix-length hint=E2=80=9D
>
>
>
> to
>
>
>
> =E2=80=9Cor a prefix whose length is shorter and as close as possible to =
the
> prefix-length hint. If the server could not provide a prefix with a short=
er
> or equal length  to the prefix-length hint, the server SHOULD provide a
> prefix whose length is longer and as close as possible to the prefix-leng=
th
> hint=E2=80=9D
>

[Tianxiang3] Thanks for the suggestion, we will edit this sentence
accordingly.

>
>
>
>
> Nits/editorial comments:
>
>
>
>
>

--94eb2c19018e6fc61805478dc8b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Roni,<div><br></div><div>Thank you for comments, we&#39=
;ll add the changes to the document in our next updated version.</div><div>=
Please see inline.=C2=A0</div><div><br></div><div>Cheers,</div><div>Tianxia=
ng</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-02-0=
2 14:42 GMT+08:00 Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:roni.ev=
en@huawei.com" target=3D"_blank">roni.even@huawei.com</a>&gt;</span>:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5663720217037483393m_3777587516231959433WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I will leave only the ite=
ms that needed my response<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div><span>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<p class=3D"MsoNormal">7.=C2=A0 =C2=A0 =C2=A0 In section 3.4 =E2=80=9CIf th=
e client decided to use=C2=A0 the prefix provided<br>
by the server despite being longer than the=C2=A0 prefix-length hint=E2=80=
=9D yet I<br>
did not see in section 3.2 that the server can provide a longer<br>
prefix.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;If the requested prefix is not available in th=
e server&#39;s prefix pool, and the client also included a prefix-length hi=
nt in the same IA_PD option, then the server SHOULD try to
 provide a prefix matching the prefix-length value, or the prefix with the =
shortest length possible which is closest to the prefix-length hint value.&=
quot;<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Roni Even] I under=
stood from 3.2 that it should provide a shorter length prefix =C2=A0closer =
to
 the request maybe =E2=80=9C</span></i></b>or the prefix with the closest p=
ossible length to the prefix-length hint value=E2=80=9D<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Tianxiang2] The original sentence was a bit confusi=
ng, perhaps we could change it like this:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD:=C2=A0&quot;If the requested prefix is not avail=
able in the server&#39;s prefix pool, and the client also included a prefix=
-length hint in the same IA_PD option, then the server SHOULD try to provid=
e a prefix matching the prefix-length value, or
 the prefix with the shortest length possible which is closest to the prefi=
x-length hint value.&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span>
<p class=3D"MsoNormal">NEW:&quot;If the requested prefix is not available i=
n the server&#39;s prefix pool, and the client also included a prefix-lengt=
h hint in the same IA_PD option, then the server SHOULD provide a prefix ma=
tching the prefix-length hint, or a prefix
 which is length is shorter and as close as possible to the prefix-length h=
int. If the server could not provide a prefix which length is shorter or eq=
ual to the prefix-length hint, the server SHOULD provide the prefix which l=
ength is longer and as close as
 possible to the prefix-length hint.&quot;<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u=
></span></i></b></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Roni Even] =
I have no problem with this text since it will also work with the rest of t=
he document but is it what was really meant<u></u><u></u></span></i></b></p=
>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0</span=
></i></b></p></div></div></div></div></div></div></div></blockquote><div>[T=
ianxiang3] This was the intended meaning of the original sentence, if the s=
erver could not honor the hint, it should provide a prefix closest to the h=
int, the client could then decide whether to accept or neglect this prefix.=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" l=
ink=3D"blue" vlink=3D"purple"><div class=3D"m_5663720217037483393m_37775875=
16231959433WordSection1"><div style=3D"border:none;border-left:solid blue 1=
.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"MsoNormal">=
<b><i><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d"><u></u></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Also a nit<u></u><u=
></u></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u=
></span></i></b></p>
<p class=3D"MsoNormal">=E2=80=9Cor a prefix which is length is shorter and =
as close as possible to the prefix-length hint. If the server could not pro=
vide a prefix which length is shorter or equal to the prefix-length hint, t=
he server SHOULD provide the prefix which
 length is longer and as close as possible to the prefix-length hint=E2=80=
=9D<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">to<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">=E2=80=9Cor a prefix whose length is shorter and as =
close as possible to the prefix-length hint. If the server could not provid=
e a prefix with a shorter or equal length =C2=A0to the prefix-length hint, =
the server SHOULD provide a prefix whose length
 is longer and as close as possible to the prefix-length hint=E2=80=9D</p><=
/div></div></div></div></div></div></div></blockquote><div><br></div><div>[=
Tianxiang3] Thanks for the suggestion, we will edit this sentence according=
ly.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"b=
lue" vlink=3D"purple"><div class=3D"m_5663720217037483393m_3777587516231959=
433WordSection1"><div style=3D"border:none;border-left:solid blue 1.5pt;pad=
ding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"MsoNormal"><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d"><u></u><u></u></span></p>
</div><span>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;pad=
ding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><div><div s=
tyle=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"=
><div><div><div><blockquote style=3D"border:none;border-left:solid #cccccc =
1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-r=
ight:0cm;margin-bottom:5.0pt"><p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><br>
<br>
Nits/editorial comments:<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--94eb2c19018e6fc61805478dc8b4--


From nobody Thu Feb  2 08:06:11 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 694AC12947A; Thu,  2 Feb 2017 08:06:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148605156539.13830.6416316067398939320.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 08:06:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CbaNiEKdGin5diZmsLr_uaAqkK4>
Cc: ipsec@ietf.org, draft-ietf-ipsecme-rfc4307bis.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-ipsecme-rfc4307bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 16:06:05 -0000

Reviewer: Pete Resnick
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments. (Apologies for the late
submission.)

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ipsecme-rfc4307bis-??
Reviewer: Pete Resnick
Review Date: 2017-02-02
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-02-16

Summary:

This document is basically ready, but there are a large number of
nits, so many that I would think additional review would be desired.

Major issues: None

Minor issues: None

Nits/editorial comments: 

[Note: I do not see any particular technical problems with the
document, but I don't have expertise in this area. I have listed below
many clarifications and fixes to typographical and grammatical errors.
(I did not note all of the punctuation errors as none of them left
ambiguity.) Normally, I would simply list these as nits/editorial
comments and leave it at that. But there are so many of these that I'm
a bit concerned that the document did not receive sufficient technical
review, given that it went through 15 versions and nobody fixed all of
these editorial issues. That said, that is an issue between the AD and
the WG.]

It seems like section 2 should be moved up above section 1 since these
specialized conventions are used in section 1.

1: The second to last sentence is ungrammatical and hard to read. Try
this:

OLD
   This document describes the parameters of the IKE protocol and
   updates the IKEv2 specification because it changes the mandatory
to
   implement authentication algorithms of the section 4 of the
RFC7296
   by saying RSA key lengths of less than 2048 are SHOULD NOT.
NEW
   This document describes the parameters of the IKE protocol. It
also
   updates the IKEv2 specification because it changes the mandatory
to
   implement authentication algorithms of section 4 of RFC 7296
   by saying RSA key lengths of less than 2048 SHOULD NOT be used.
END

1.1, first sentence: s/then/than

1.1, last sentence: s/in a separate document/in this separate
document.

1.2: The last sentence of the third paragraph repeats what is in the
last paragraph of 1.2 and therefore redundant. You can strike it. 

2: I suggest adding a sentence after the first paragraph for
clarification: "When used in the tables in this document, these terms
indicate that the listed algorithm MUST, MUST NOT, SHOULD, SHOULD NOT
or MAY be implemented as part of an IKEv2 implementation." 4307 never
said that specifically, and I've always found it weird.

3.1, first paragraph: s/an integrity algorithms in Section 3.3/one of
the integrity algorithms in Section 3.3

3.1, third paragraph: s/CRFG/the Crypto Forum Research Group (CFRG) of
the IRTF

(You not only didn't define it, you got the acronym backwards.)

3.1, third from last paragraph: s/on those cases/in those cases

3.1, second from last paragraph: s/implementation/implementations

3.1, last paragraph: s/of-the-shelves/off-the-shelf ;
s/therefor/therefore

3.3, last paragraph: s/status ware/statuses were

3.4, third paragraph: s/were/was

3.4, fourth paragraph: s/vulnerable to be broken/vulnerable to being
broken

3.4, last paragraph: s/thater/that; s/academia have/academia has

4: s/concerned on/concerned with

4.1, first paragraph: 

OLD
                                           RSA Digital Signature is
not
   recommended for keys smaller then 2048, but since these signatures
   only have value in real-time, and need no future protection,
smaller
   keys was kept at SHOULD NOT instead of MUST NOT.

NEW
	See section 4.1.1 for a discussion of key length recommendations for
	use in RSA Digital Signature.
END

(If you want, include some of the original text in 4.1.1.

4.1, third paragraph: s/it does not/they do not

4.2, paragraphs 1, 2, & 3: s/When Digital Signature
authentication/When a Digital Signature authentication ; also, strike
the word "then" in the first two paragraphs.


From nobody Thu Feb  2 15:03:42 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 688FC1299A8; Thu,  2 Feb 2017 15:03:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 15:03:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/F7nJzrvLIhl99GChWRtHWBjNYI8>
Cc: ietf@ietf.org, draft-ietf-oauth-jwsreq.all@ietf.org, oauth@ietf.org
Subject: [Gen-art] Review of draft-ietf-oauth-jwsreq-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 23:03:40 -0000

Reviewer: Joel Halpern
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-oauth-jwsreq-??
Reviewer: Joel Halpern
Review Date: 2017-02-02
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-02-16

Summary: This document is ready for publication as a Proposed
Standard

Major issues: N/A

Minor issues:
    Why is the example if section 4 (and others later on) described
as
"non-normative"?  Is it incomplete?  incorrect?  An example is, by
definition, not a full specification.  The language seems designed to
reduce the value of the example.  I would recommend removing all the
"non-normative" notes from the examples.  They are clearly stated to
be examples. 

Nits/editorial comments: 



From nobody Thu Feb  2 15:13:57 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E667D1294FF for <gen-art@ietf.org>; Thu,  2 Feb 2017 15:13:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Jean Mahoney" <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148607723691.13910.14780133703406706667.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 15:13:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/a_B7ZooTDWnsMhRIhLXrmy5xvKw>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: mahoney@nostrum.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 23:13:57 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-02-16

Reviewer               Type      LC end     Draft
Brian Carpenter        Telechat  2016-12-20 draft-ietf-6tisch-minimal-19 *
Francis Dupont         Last Call 2017-02-24 draft-kivinen-802-15-ie-04 
Francis Dupont         Telechat  2017-02-24 draft-kivinen-802-15-ie-04
Orit Levin             Last Call 2017-01-31 draft-ietf-sidr-delta-protocol-05
Pete Resnick           Last Call 2017-01-31 draft-ietf-ccamp-flexible-grid-ospf-ext-07
Lucy Yong              Last Call 2017-01-30 draft-ietf-sidr-rpki-rtr-rfc6810-bis-08

For telechat 2017-03-02

Reviewer               Type      LC end     Draft
Roni Even              Last Call 2017-02-27 draft-sgtatham-secsh-iutf8-05
Meral Shirazipour      Last Call 2017-02-10 draft-ietf-dmm-hnprenum-05
Robert Sparks          Telechat  2017-01-17 draft-ietf-mpls-residence-time-13 *

Last calls:

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-03-01 draft-ietf-6man-rfc1981bis-04
Brian Carpenter        Last Call 2017-02-09 draft-ietf-mmusic-sctp-sdp-22
Ralph Droms            Last Call 2017-02-07 draft-ietf-nfsv4-rfc5666bis-09
Francis Dupont         Last Call 2017-02-14 draft-freytag-lager-variant-rules-03 *
Fernando Gont          Last Call 2017-01-23 draft-ietf-dime-agent-overload-08
Vijay Gurbani          Last Call 2017-02-15 draft-ietf-grow-mrt-add-paths-03
Joel Halpern           Last Call 2017-02-15 draft-ietf-bmwg-virtual-net-04
Russ Housley           Last Call 2017-02-13 draft-ietf-pals-mpls-tp-dual-homing-protection-05
Jouni Korhonen         Last Call 2017-02-13 draft-ietf-pals-mpls-tp-dual-homing-coordination-05
Meral Shirazipour      Last Call 2017-02-07 draft-ietf-nfsv4-rpcrdma-bidirection-06
Robert Sparks          Last Call 2017-03-01 draft-ietf-6man-rfc4291bis-07
Peter Yee              Last Call 2017-03-01 draft-ietf-6man-rfc2460bis-08

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Robert Sparks
  Dale Worley
  Peter Yee
  Lucy Yong
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Ralph Droms
  Francis Dupont
  Roni Even

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Fri Feb  3 15:22:26 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0EB3129980; Fri,  3 Feb 2017 15:22:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
Date: Fri, 03 Feb 2017 15:22:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/INeB1_e3pB4_yVY9k5OUKK_NIBQ>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 23:22:20 -0000

Reviewer: Pete Resnick
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ccamp-flexible-grid-ospf-ext-07
Reviewer: Pete Resnick
Review Date: 2017-02-03
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-02-16

Summary:

Looks good from a non-expert point of view. A few things I found
ambiguous or confusing that should be easily clarified, but nothing
that should stop the document from moving forward.

Major issues:

None.

Minor issues:

4.1.1:

The figure is a bit confusing: There might not exist a "Max Slot Width
at Priority 7" if bit 7 is clear in the Priority field, correct?
Perhaps it would be better to just show that as "..." or "Max Slot
Width at Priority n". The thing is, it might only be a single value,
followed by the padding, so having the second value in there might be
misleading. (Perhaps similar constructs are used in other MPLS docs
and people will understand. But it took me a while to figure it out.)

The discussion of Priority was very confusing for me. In the third
sentence, do you mean, "A bit is set (1) corresponding to each
priority represented in the sub-TLV, and clear (0) for each priority
not represented in the sub-TLV"? I don't understand the MUST/MUST NOT
as you had it. And I don't understand the last sentence at all. Are
you trying to say, "The leftmost bit (priority level 0) MUST be set,
and priority level 0 MUST be advertised in the sub-TLV."? Otherwise, I
don't get it.

I don't understand the MAY in the last sentence. Does that mean that I
MAY also set it to the highest possible nominal central frequency
supported by the link? I don't understand what that sentence is trying
to tell me.

Nits/editorial comments: 

3, last paragraph:

OLD
   That is, the additional information
NEW
   That is, this section defines the additional information
END

As it is, it is ungrammatical.

3.1:

   On a DWDM link, the allocated or in-use frequency slots must not 
   overlap with each other.

I think perhaps it's clearer to simply say "frequency slots do not
overlap each other", assuming that's what you mean. I don't think
you're trying to say something normative there; it's just a fact. But
people often read "must" (whether it's uppercased or not) to be
imposing a requirement. I don't think that's what you're doing here,
so better to make it clear. (As you may know, I'm not a fan of overuse
of MUSTs and SHOULDs, but I do like it when documents are clear.)

As an opposite example:

   Hence, in order to clearly show which LSPs can be supported and
what 
   frequency slots are unavailable, the available frequency ranges
MUST 
   be advertised by the routing protocol for the flexi-grid DWDM
links.  
   A set of non-overlapping available frequency ranges MUST be 
   disseminated in order to allow efficient resource management of 
   flexi-grid DWDM links and RSA procedures which are described in 
   Section 4.8 of [RFC7698]. 

Those MUSTs look weird to me. I think instead of "MUST be" you mean
"are", since it doesn't look like an implementation really has a
choice here.

3.2:

   Hence, in order to support all possible applications and 
   implementations the following information should be advertised for
a 
   flexi-grid DWDM link:
   
Is that "should" in there meant to be normative? That is, do bad
things happen if I don't advertise one of those items? Or do you just
mean "the following information is advertised..."? 

3.3:

   For this reason, the available frequency slot/ranges need to be 
   advertised for a flexi-grid DWDM link instead of the specific 
   "wavelengths" points that are sufficient for a fixed-grid link.  

Where you say "needs to be advertised", are you making a normative
statement, or are you just describing, in which case "are advertised"
would be clearer?

(By the way: Typo in the following sentence. Change "thus" to
"this".)

4.1:

   When Switching Capability and Encoding fields are set to values as

   stated above, the Interface Switching Capability Descriptor MUST be

   interpreted as in [RFC4203] with the optional inclusion of one or 
   more Switching Capability Specific Information sub-TLVs.  

Same question as earlier about "MUST be" vs. "is".

4.1.1:

   The technology specific part of the Flexi-grid ISCD should include


Same question as earlier about "should include" vs. "includes".

   Length (16 bits): The length of the value field of this sub-TLV. 

Perhaps obvious to an MPLS person, but is this the length in bits or
bytes, and does it include the Type and Length fields?

   Max Slot Width
   
I think the first "MUST be" should be "is". In the rest, I think you
mean that if bits 0, 3, and 6 are set in Priority, then there should
be 3 Max Slot Width entries, and the first one is the max slot width
for priority level 0, the second one is the width for priority level
3, and the last is the priority slot width for priority level 7. Do I
understand that correctly? If so, it might be useful to say that. And
the last sentence would be clearer if it said, "The number of Max Slot
Width fields MUST be identical to the number of bits set in the
Priority field." Saying it with the MUST NOT confused me.

   Unreserved Padding

Shouldn't this say, "MUST be set to 0 and MUST be ignored on
receipt"?

   The Reserved field

Why is this a "SHOULD be ignored on receipt" whereas the Padding Bits
"MUST be ignored"? (And I think it would be better to move this up in
order so it's right after Priority.)

4.2:

In Switching Cap, you say "MUST be consistent with" and in Encoding,
you say "must be consistent with". Either make them both "MUST be", or
just strike the words and simply make it, "consistent with".



From nobody Sat Feb  4 11:31:30 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7279912969C; Sat,  4 Feb 2017 11:31:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148623668946.2758.17261798423102538026.idtracker@ietfa.amsl.com>
Date: Sat, 04 Feb 2017 11:31:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/43sJ05RAeu3bF3i4XfyxzyquI0M>
Cc: draft-ietf-6tisch-minimal.all@ietf.org
Subject: [Gen-art] Review of draft-ietf-6tisch-minimal-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 19:31:29 -0000

Reviewer: Brian Carpenter
Review result: Ready

Gen-ART telechat review of draft-ietf-6tisch-minimal-19

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-6tisch-minimal-19.txt
Reviewer: Brian Carpenter
Review Date: 2017-02-05
IETF LC End Date: 2016-12-20
IESG Telechat date: 2017-02-16

Summary: Ready
--------

Comment:
--------

Thanks for handling my Last Call comments. I have also reviewed
the recent security-related updates.


From nobody Sat Feb  4 19:23:17 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 814B11294FE; Sat,  4 Feb 2017 19:23:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148626499152.2778.12224491829240452688.idtracker@ietfa.amsl.com>
Date: Sat, 04 Feb 2017 19:23:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/bA6XfZn0KGfTnQ8afnscjcu_eRc>
Cc: draft-ietf-mmusic-sctp-sdp.all@ietf.org, mmusic@ietf.org
Subject: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 03:23:11 -0000

Reviewer: Brian Carpenter
Review result: Ready with Nits

Gen-ART Last Call review of draft-ietf-mmusic-sctp-sdp-22

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-mmusic-sctp-sdp-22.txt
Reviewer: Brian Carpenter
Review Date: 2017-02-XX
IETF LC End Date: 2017-02-09
IESG Telechat date:  

Summary: Ready with nits
--------

Comments:
---------

Two points I noted in the writeup:
"There are existing implementations of earlier versions of the
document..."

Excellent, but I wonder why we don't see Implementation Status
sections
under RFC 6982 in more Last Call drafts.

"IPv6 address examples are not necessary since IP version differences
are immaterial to the purpose of the specification."

It's just as easy to give an IPv6 example though, and more future
proof.

Minor issue: (almost a nit)
------------

> 1.  Introduction
...
>   NOTE: Due to the characteristics of TCP, usage of 'TCP/DTLS/SCTP'
>   will always force ordered and reliable delivery of the SCTP
packets,
>   which limits the usage of the SCTP options.  Therefore, it is
>   RECOMMENDED that TCP is only used in situations where UDP traffic
is
>   blocked.

Why would one choose 'TCP/DTLS/SCTP' rather than just 'TCP/TLS'? I
don't
object to it being specified, but since you don't support multihoming
or multiple associations, what is the use case, in a few words?

Nits:
-----

> 4.4.2.  SDP Media Description values
>
>      m= line parameter        parameter value(s)
>     
------------------------------------------------------------------
>      <media>:                 "application"
>      <proto>:                 "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"
>      <port>:                  UDP port number (for "UDP/DTLS/SCTP")
>                               TCP port number (for
""UDP/DTLS/SCTP")

I think the last line should be: TCP port number (for
"TCP/DTLS/SCTP")

There is some inconsistency in the use of quotation marks:
"UDP/DTLS/SCTP"
or 'UDP/DTLS/SCTP'




From nobody Sun Feb  5 06:14:14 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50C4A129434; Sun,  5 Feb 2017 06:14:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7O-FEONiP2gA; Sun,  5 Feb 2017 06:14:11 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0DB129422; Sun,  5 Feb 2017 06:14:09 -0800 (PST)
X-AuditID: c1b4fb30-b99fe70000007389-7f-5897332e64e5
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id E0.C8.29577.E2337985; Sun,  5 Feb 2017 15:14:08 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0319.002; Sun, 5 Feb 2017 15:14:06 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Index: AQHSf18vg7KvnMe4fUWDAsU2eyafs6Faa6TQ
Date: Sun, 5 Feb 2017 14:14:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFE5BE2@ESESSMB209.ericsson.se>
References: <148626499152.2778.12224491829240452688.idtracker@ietfa.amsl.com>
In-Reply-To: <148626499152.2778.12224491829240452688.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbFdVNfAeHqEwdvdvBZtF/cxWWzq38Ri cfXVZxaLqcsfsziweOycdZfdY8mSn0wBTFFcNimpOZllqUX6dglcGb3nnrEVnJCu2Nie1cD4 RqqLkZNDQsBE4vv2TqYuRi4OIYF1jBI3761mhHAWMUr0PFkJ5HBwsAlYSHT/0wZpEBGIkujZ upYZpIZZoIFR4sDJJkaQhDDQpF2HWlggikwlbi5bzgRhG0lc3d3LDmKzCKhI3Hi2lA3E5hXw lZjz/CZYvRCQferPVmYQm1PAT2LB+oVgcUYBMYnvp9aAzWEWEJe49WQ+E8TVAhJL9pxnhrBF JV4+/scKYStJLLr9mQnkZmYBTYn1u/QhWhUlpnQ/ZIdYKyhxcuYTlgmMorOQTJ2F0DELSccs JB0LGFlWMYoWpxYn5aYbGemlFmUmFxfn5+nlpZZsYgTGzcEtvw12ML587niIUYCDUYmH90PM tAgh1sSy4srcQ4wSHMxKIrw7daZHCPGmJFZWpRblxxeV5qQWH2KU5mBREuc1W3k/XEggPbEk NTs1tSC1CCbLxMEp1cBYw5m4e/+h1GPyHJevmt9x2+c+20juWVNIyf3i9Y67zvfc3Ml2If+Y +7XXFYx/UmylH7/hmfNYq/6IN3vFR8fyecuUP7T6h76qEvjEmbwv5suSJ9HXMvdPf9KnffiT bH5743+JW6eEM/t9236F18odkX6azF2r8uCZfOW910wd/7WPf/1b6sirxFKckWioxVxUnAgA hTJSSpcCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dg_ZHxS91XS3u8m5nCtZNeKK62A>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 14:14:12 -0000

SGkgQnJpYW4sDQoNClRoYW5rcyBmb3IgeW91ciByZXZpZXchIFBsZWFzZSBzZWUgaW5saW5lLg0K
DQouLi4NCg0KQ29tbWVudHM6DQotLS0tLS0tLS0NCg0KPlR3byBwb2ludHMgSSBub3RlZCBpbiB0
aGUgd3JpdGV1cDoNCj4iVGhlcmUgYXJlIGV4aXN0aW5nIGltcGxlbWVudGF0aW9ucyBvZiBlYXJs
aWVyIHZlcnNpb25zIG9mIHRoZSBkb2N1bWVudC4uLiINCj4NCj5FeGNlbGxlbnQsIGJ1dCBJIHdv
bmRlciB3aHkgd2UgZG9uJ3Qgc2VlIEltcGxlbWVudGF0aW9uIFN0YXR1cyBzZWN0aW9ucyB1bmRl
ciBSRkMgNjk4MiBpbiBtb3JlIExhc3QgQ2FsbCBkcmFmdHMuDQoNClBlcmhhcHMgYSB0b3BpYyBm
b3IgYW4gSUVURiBjaGFpcnMgbHVuY2ggcHJlc2VudGF0aW9uPw0KDQpJIGhhdmUgdG8gYWRtaXQg
dGhhdCBJIGRpZCBub3Qga25vdyBhYm91dCA2OTgyIChub3cgb2Jzb2xldGVkIGJ5IDc5NDIpLiBN
eSBzdWdnZXN0aW9uIHdvdWxkIHRvIG5vdCBjb2xsZWN0IHRoYXQgaW5mb3JtYXRpb24gZm9yIHRo
aXMgZHJhZnQgYXQgdGhpcyBwb2ludCBvZiB0aW1lLCBhcyBpdCBjb3VsZCB0YWtlIHNvbWUgdGlt
ZS4NCg0KPiJJUHY2IGFkZHJlc3MgZXhhbXBsZXMgYXJlIG5vdCBuZWNlc3Nhcnkgc2luY2UgSVAg
dmVyc2lvbiBkaWZmZXJlbmNlcyBhcmUgaW1tYXRlcmlhbCB0byB0aGUgcHVycG9zZSBvZiB0aGUg
c3BlY2lmaWNhdGlvbi4iDQo+DQo+SXQncyBqdXN0IGFzIGVhc3kgdG8gZ2l2ZSBhbiBJUHY2IGV4
YW1wbGUgdGhvdWdoLCBhbmQgbW9yZSBmdXR1cmUgcHJvb2YuDQoNCkkgY2FuIG1vZGlmeSB0aGUg
YWRkcmVzcyBpbiB0aGUgZXhhbXBsZSwgZnJvbSBJUHY0IHRvIHY2Lg0KDQoNCk1pbm9yIGlzc3Vl
OiAoYWxtb3N0IGEgbml0KQ0KLS0tLS0tLS0tLS0tDQoNCjEuICBJbnRyb2R1Y3Rpb24NCi4uLg0K
Pj4gICBOT1RFOiBEdWUgdG8gdGhlIGNoYXJhY3RlcmlzdGljcyBvZiBUQ1AsIHVzYWdlIG9mICdU
Q1AvRFRMUy9TQ1RQJw0KPj4gICB3aWxsIGFsd2F5cyBmb3JjZSBvcmRlcmVkIGFuZCByZWxpYWJs
ZSBkZWxpdmVyeSBvZiB0aGUgU0NUUA0KPj4gICBwYWNrZXRzLCB3aGljaCBsaW1pdHMgdGhlIHVz
YWdlIG9mIHRoZSBTQ1RQIG9wdGlvbnMuICBUaGVyZWZvcmUsIGl0IGlzDQo+PiAgIFJFQ09NTUVO
REVEIHRoYXQgVENQIGlzIG9ubHkgdXNlZCBpbiBzaXR1YXRpb25zIHdoZXJlIFVEUCB0cmFmZmlj
DQo+PiAgIGlzIGJsb2NrZWQuDQo+DQo+IFdoeSB3b3VsZCBvbmUgY2hvb3NlICdUQ1AvRFRMUy9T
Q1RQJyByYXRoZXIgdGhhbiBqdXN0ICdUQ1AvVExTJz8gSSBkb24ndCBvYmplY3QgdG8gaXQgYmVp
bmcgc3BlY2lmaWVkLCBidXQgc2luY2UgeW91IA0KPiBkb24ndCBzdXBwb3J0IG11bHRpaG9taW5n
IG9yIG11bHRpcGxlIGFzc29jaWF0aW9ucywgd2hhdCBpcyB0aGUgdXNlIGNhc2UsIGluIGEgZmV3
IHdvcmRzPw0KDQpTQ1RQIHN1cHBvcnRzIG11bHRpcGxlIFNDVFAgc3RyZWFtcyBvdmVyIGEgc2lu
Z2xlIGFzc29jaWF0aW9uLCBhbmQgeW91IGNhbiBzdGlsbCB1c2UgdGhhdCB3aXRoICdUQ1AvRFRM
Uy9TQ1RQJy4gRS5nLCB0aGUgV2ViUlRDIERhdGEgQ2hhbm5lbCBwcm90b2NvbCB1c2VzIHR3byBz
dHJlYW1zIHRvIHJlYWxpemUgYSBkYXRhIGNoYW5uZWwuDQoNCkkgY291bGQgbW9kaWZ5IHRoZSBm
aXJzdCBzZW50ZW5jZSBhcyBmb2xsb3dpbmc6DQoNCiAgICAgICAgIk5PVEU6IER1ZSB0byB0aGUg
Y2hhcmFjdGVyaXN0aWNzIG9mIFRDUCwgd2hpbGUgbXVsdGlwbGUgU0NUUCBzdHJlYW1zDQogICAg
ICAgICBjYW4gc3RpbGwgYmUgdXNlZCwgdXNhZ2Ugb2YgJ1RDUC9EVExTL1NDVFAnIHdpbGwgYWx3
YXlzIGZvcmNlLi4uLiINCg0KTml0czoNCi0tLS0tDQoNCj4+IDQuNC4yLiAgU0RQIE1lZGlhIERl
c2NyaXB0aW9uIHZhbHVlcw0KPj4NCj4+ICAgICAgbT0gbGluZSBwYXJhbWV0ZXIgICAgICAgIHBh
cmFtZXRlciB2YWx1ZShzKQ0KPj4gICAgIA0KPj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+ICAgICAgPG1lZGlhPjog
ICAgICAgICAgICAgICAgICJhcHBsaWNhdGlvbiINCj4+ICAgICAgPHByb3RvPjogICAgICAgICAg
ICAgICAgICJVRFAvRFRMUy9TQ1RQIiBvciAiVENQL0RUTFMvU0NUUCINCj4+ICAgICAgPHBvcnQ+
OiAgICAgICAgICAgICAgICAgIFVEUCBwb3J0IG51bWJlciAoZm9yICJVRFAvRFRMUy9TQ1RQIikN
Cj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRDUCBwb3J0IG51bWJlciAo
Zm9yICIiVURQL0RUTFMvU0NUUCIpDQo+DQo+IEkgdGhpbmsgdGhlIGxhc3QgbGluZSBzaG91bGQg
YmU6IFRDUCBwb3J0IG51bWJlciAoZm9yICJUQ1AvRFRMUy9TQ1RQIikNCg0KQ29ycmVjdC4gV2ls
bCBiZSBmaXhlZC4NCg0KPlRoZXJlIGlzIHNvbWUgaW5jb25zaXN0ZW5jeSBpbiB0aGUgdXNlIG9m
IHF1b3RhdGlvbiBtYXJrczogIlVEUC9EVExTL1NDVFAiIG9yICdVRFAvRFRMUy9TQ1RQJw0KDQpJ
J2xsIGZpeCB0aGF0LiBJIHdpbGwgdXNlIHNpbmdsZSBxdW90ZXMuDQoNClJlZ2FyZHMsDQoNCkNo
cmlzdGVyDQoNCg==


From nobody Sun Feb  5 09:43:21 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2744C126D74; Sun,  5 Feb 2017 09:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRLquIOC2SIX; Sun,  5 Feb 2017 09:43:18 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C166412940D; Sun,  5 Feb 2017 09:43:18 -0800 (PST)
X-AuditID: c6180641-c53ff70000000a06-05-58971de17dfd
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by  (Symantec Mail Security) with SMTP id 08.5D.02566.1ED17985; Sun,  5 Feb 2017 13:43:15 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0319.002; Sun, 5 Feb 2017 12:43:15 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Review of draft-ietf-6tisch-minimal-19
Thread-Index: AQHSfx1LXAe96xmIgUyRTExwo2VhMaFbBD6A
Date: Sun, 5 Feb 2017 17:43:15 +0000
Message-ID: <23D53438-3D90-4FC9-9984-3CDA0E0F5B9D@ericsson.com>
References: <148623668946.2758.17261798423102538026.idtracker@ietfa.amsl.com>
In-Reply-To: <148623668946.2758.17261798423102538026.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_AB4E2E20-765D-42ED-B30A-D2D65A98F5C3"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCIsWRmVeSWpSXmKPExsUyuXRPoO5j2ekRBg2nzS3aLu5jsjg8Yy6z xdVXn1kcmD12zrrL7rFkyU+mAKYoLpuU1JzMstQifbsErow1174yFzw2rbiw5glrA+Nnoy5G Tg4JAROJeW+3MXcxcnEICaxnlDi89hEbhLOMUWJpexcrSBUbUNWGnZ+ZQGwRAUOJ/08/M4LY zALFEtNerWfvYuTgEBYwlmjeLAJiigCVH1rOAlFtJLGx4yPYFBYBFYnrm6aCxXkF7CU6Dq8E s4UEfCVmf3nOBmJzCvhJXJ51BWwTo4CYxPdTa5ggNolL3HoynwniZhGJhxdPs0HYohIvH/9j hbCVJOa8vgb2C7PAFEaJOfN2QC0TlDg58wnLBEaRWUhmzUJWNwtJHUSRtsSyha+ZZwH9wyyg IzF5ISNE2FTi9dGPULa1xIxfB9kgbEWJKd0P2Rcwcqxi5CgtLsjJTTcy3MQIjK9jEmyOOxj3 9noeYhTgYFTi4d3AOj1CiDWxrLgy9xCjClDrow2rLzBKseTl56UqifAuSgBK86YkVlalFuXH F5XmpBYfYpTmYFES570ecj9cSCA9sSQ1OzW1ILUIJsvEwSnVwOg5/fjkrHunt2j27nBLmh/a aCr75c2hU1Ylb9lOvD0uXHfM6rVczDxGsVXdq569zjpYMO+v4BnOpt5pkf16ntufKWm1tehY fThRqb5aQ/ZNavuM41xi7rs9/36651Tux/Uyv2vDi0L5q4X9XI0r1nT/rq25dSVBf2JUkMLy jvWL0ssCQp7OmKvEUpyRaKjFXFScCADuMf35twIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CJrhorV3_3ycmFgiAhBsk_wMA-I>
Cc: Gen art <gen-art@ietf.org>, "draft-ietf-6tisch-minimal.all@ietf.org" <draft-ietf-6tisch-minimal.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6tisch-minimal-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 17:43:20 -0000

--Apple-Mail=_AB4E2E20-765D-42ED-B30A-D2D65A98F5C3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks a lot for your review Brian.

Regards
Suresh

> On Feb 4, 2017, at 2:31 PM, Brian Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> Reviewer: Brian Carpenter
> Review result: Ready
>=20
> Gen-ART telechat review of draft-ietf-6tisch-minimal-19
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-6tisch-minimal-19.txt
> Reviewer: Brian Carpenter
> Review Date: 2017-02-05
> IETF LC End Date: 2016-12-20
> IESG Telechat date: 2017-02-16
>=20
> Summary: Ready
> --------
>=20
> Comment:
> --------
>=20
> Thanks for handling my Last Call comments. I have also reviewed
> the recent security-related updates.
>=20


--Apple-Mail=_AB4E2E20-765D-42ED-B30A-D2D65A98F5C3
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjA1MTc0MzE1WjAjBgkqhkiG9w0B
CQQxFgQUYs0Ja196aXyebvZmSubYNvK8yEEwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQB+j7PBjSpktAkVUxzMUf2YON7Fadhgn2JRgaK5cVp9x1BPKOlDHpEP32d181kW
6OAXpPBOJdJI4OKnyDAJScWcUQTQxBGnNqI1VZb5nf5bOERwHZ8lZyoKNdo8fK4iLfKO/EPJ4tAY
IA2/eFyrCggG6u88wxmlDwSfMv7wJwl6ztChToZ7x3mYbBsmLqHcIei/k8uVWwxbohfcHuHxWmd6
/2Wz2RVL0hUB/D4XI2r6UCAK0mcMnri/QhqZyII73NOL34n8EZurH2ovIaqQ33a7EpRe7pAzu84g
6zt7NyEG09r+oefSl9qu7DBURVN9Usrt/oNbiFMxssPXZ2mpXbJCAAAAAAAA

--Apple-Mail=_AB4E2E20-765D-42ED-B30A-D2D65A98F5C3--


From nobody Sun Feb  5 11:05:52 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBBA1294B1; Sun,  5 Feb 2017 11:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P2fgRpV_Q26l; Sun,  5 Feb 2017 11:05:47 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30C1B12944B; Sun,  5 Feb 2017 11:05:47 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id f144so17985519pfa.2; Sun, 05 Feb 2017 11:05:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=sidxvlWB/QdR1je1FPvMFJt4/ybtvfcjZqvx764GwUQ=; b=pI/do7v3NP0eF4QsB5siE+qu/6MMoq6DVQMVctZd74HQCzxGWnJtJN5zWBTNGCJqzz YpLAbzMGSOEdqjyOKeZMoZCD/z1AJhuzzhdK4zikl8BEweki7Z4gpXeB8wVHmbImVMq0 Aj4DmFbqht6cEt5qkjG8xvUPR7Bn34CEhLbmiuLWphCxRpUe+1EEKnHghF3o1+mlWV1J ywEo+nSYVJSDt+IOEyebRqp0wsCk1hhakzbkQZbvZBBEVqq7W+fhj9kV3yS+hCgB7x8E MbK4F6B8FWS9QjtrP2a62L9y9wwE6yMPkwCmGMruDFZ9zUVFy+pD87B0iI8yO7hYg+w4 Y3+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=sidxvlWB/QdR1je1FPvMFJt4/ybtvfcjZqvx764GwUQ=; b=BVuFZU0WFtRbfemH5DY+HXwTkeUpUhgOUjStcwALzdUt/BgZnMEAUadlaQRJFNxC8y CZ444YI5egY016IoOsF+FI73LkIyiIbRYNlo2WUOz/fXU+d5HPux1kirAfklte3mTLq4 4H1prIOZIaVe5CoOq5LcB8TXwrR2tTtgUS0i9vbsrQoy6228Do02qg2/d08gr8WXX1q/ Nohhe2wgBSflUPdJa/8FYHt95H0A3kKdI3xQL9kmwZ+l6xhgyKxrJAKzkWgR1peDLkvb Wp/90Q+qlHoFy40uX4KJCKzL3yPMRKzQ6KIaSQDx3WeMXuwk1sd12yOwIkWudUQk40WO 6jjQ==
X-Gm-Message-State: AIkVDXK5eff2bzPKHVltmKHoQFs1/y8sxxuyAVzUU/Dp1kaM7veYfuNVLTx3x72VGXU95w==
X-Received: by 10.98.44.10 with SMTP id s10mr9069408pfs.161.1486321546633; Sun, 05 Feb 2017 11:05:46 -0800 (PST)
Received: from ?IPv6:2406:e007:43d3:1:28cc:dc4c:9703:6781? ([2406:e007:43d3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z77sm82832211pfk.47.2017.02.05.11.05.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Feb 2017 11:05:45 -0800 (PST)
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148626499152.2778.12224491829240452688.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B4BFE5BE2@ESESSMB209.ericsson.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dcc818aa-5283-a521-98f2-0fae9f43ae8f@gmail.com>
Date: Mon, 6 Feb 2017 08:05:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFE5BE2@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/L95Ba-z7FCvstHtd5sCIE0y5Lqc>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 19:05:48 -0000

Hi Christer,
On 06/02/2017 03:14, Christer Holmberg wrote:
> Hi Brian,
> 
> Thanks for your review! Please see inline.
> 
> ...
> 
> Comments:
> ---------
> 
>> Two points I noted in the writeup:
>> "There are existing implementations of earlier versions of the document..."
>>
>> Excellent, but I wonder why we don't see Implementation Status sections under RFC 6982 in more Last Call drafts.
> 
> Perhaps a topic for an IETF chairs lunch presentation?

Or at least a short reminder!

> 
> I have to admit that I did not know about 6982 (now obsoleted by 7942). My suggestion would to not collect that information for this draft at this point of time, as it could take some time.

Agreed.

>> "IPv6 address examples are not necessary since IP version differences are immaterial to the purpose of the specification."
>>
>> It's just as easy to give an IPv6 example though, and more future proof.
> 
> I can modify the address in the example, from IPv4 to v6.

As you wish.

> Minor issue: (almost a nit)
> ------------
> 
> 1.  Introduction
> ...
>>>   NOTE: Due to the characteristics of TCP, usage of 'TCP/DTLS/SCTP'
>>>   will always force ordered and reliable delivery of the SCTP
>>>   packets, which limits the usage of the SCTP options.  Therefore, it is
>>>   RECOMMENDED that TCP is only used in situations where UDP traffic
>>>   is blocked.
>>
>> Why would one choose 'TCP/DTLS/SCTP' rather than just 'TCP/TLS'? I don't object to it being specified, but since you 
>> don't support multihoming or multiple associations, what is the use case, in a few words?
> 
> SCTP supports multiple SCTP streams over a single association, and you can still use that with 'TCP/DTLS/SCTP'. E.g, the WebRTC Data Channel protocol uses two streams to realize a data channel.

OK.

(I now remember that I raised essentially the same question when reviewing
draft-ietf-clue-datachannel. Actually I'm glad to see SCTP proving useful.)

> I could modify the first sentence as following:
> 
>         "NOTE: Due to the characteristics of TCP, while multiple SCTP streams
>          can still be used, usage of 'TCP/DTLS/SCTP' will always force...."

OK

> 
> Nits:
> -----
> 
>>> 4.4.2.  SDP Media Description values
>>>
>>>      m= line parameter        parameter value(s)
>>>     
>>> ------------------------------------------------------------------
>>>      <media>:                 "application"
>>>      <proto>:                 "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"
>>>      <port>:                  UDP port number (for "UDP/DTLS/SCTP")
>>>                               TCP port number (for ""UDP/DTLS/SCTP")
>>
>> I think the last line should be: TCP port number (for "TCP/DTLS/SCTP")
> 
> Correct. Will be fixed.
> 
>> There is some inconsistency in the use of quotation marks: "UDP/DTLS/SCTP" or 'UDP/DTLS/SCTP'
> 
> I'll fix that. I will use single quotes.

Thanks,
    Brian


From nobody Sun Feb  5 13:43:50 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39DA7129705; Sun,  5 Feb 2017 13:43:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
Date: Sun, 05 Feb 2017 13:43:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/EyfGxUxcS-od-kJhUJPPhttXnlc>
Cc: draft-ietf-bmwg-virtual-net.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Subject: [Gen-art] Review of draft-ietf-bmwg-virtual-net-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 21:43:44 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bmwg-virtual-net-??
Reviewer: Joel Halpern
Review Date: 2017-02-05
IETF LC End Date: 2017-02-15
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as an Informational
RFC.

Major issues:

Minor issues:
    The second figure in section 4.4 talks about the use of multiple
3x3 tables, but appears to show the use of multiple 4x4 tables.  This
reader found himself confused.

Nits/editorial comments: 



From nobody Mon Feb  6 01:15:59 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9B9129CC1; Mon,  6 Feb 2017 01:15:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJ1-5txFrgQt; Mon,  6 Feb 2017 01:15:56 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85B9129CC2; Mon,  6 Feb 2017 01:15:55 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-67-58983ec96827
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by  (Symantec Mail Security) with SMTP id 89.1F.22993.9CE38985; Mon,  6 Feb 2017 10:15:53 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0319.002; Mon, 6 Feb 2017 10:15:52 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Index: AQHSf18vg7KvnMe4fUWDAsU2eyafs6Faa6TQgABKiACAAQ+dAA==
Date: Mon, 6 Feb 2017 09:15:50 +0000
Message-ID: <D4BE0BC4.177A8%christer.holmberg@ericsson.com>
References: <148626499152.2778.12224491829240452688.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B4BFE5BE2@ESESSMB209.ericsson.se> <dcc818aa-5283-a521-98f2-0fae9f43ae8f@gmail.com>
In-Reply-To: <dcc818aa-5283-a521-98f2-0fae9f43ae8f@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5EBCF2F9A4AA4F4D83A06CA03DA20AED@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJIsWRmVeSWpSXmKPExsUyM2K7se5JuxkRBrduWFm0XdzHZLGpfxOL xdVXn1kspi5/zOLA4rFz1l12jyVLfjIFMEVx2aSk5mSWpRbp2yVwZUzY08FYsFGqYk5rUAPj dpEuRk4OCQETicWtZ9m6GLk4hATWMUq86N3HCOEsYpS4emgRSxcjBwebgIVE9z9tkAYRgRiJ nS+6mEBqmAUaGCUOnGxiBEkIA02a0v6aEaLIVOLmsuVMELaTxMv+NmYQm0VARaKvfRmYzStg LTHp+GcWiGVHGCV6L5wEa+YUsJU41HUZzGYUEJP4fmoN2CBmAXGJW0/mM0GcLSCxZM95Zghb VOLl43+sILaogJ7E8udroOJKEj82XGKB6NWTuDF1ChvIM8xAi8//koYIa0ssW/ga6h5BiZMz n7BMYBSfhWTbLCTdsxC6ZyHpnoWkewEj6ypG0eLU4uLcdCNjvdSizOTi4vw8vbzUkk2MwAg8 uOW37g7G1a8dDzEKcDAq8fB+sJ0eIcSaWFZcmXuIUYKDWUmEN9ByRoQQb0piZVVqUX58UWlO avEhRmkOFiVxXrOV98OFBNITS1KzU1MLUotgskwcnFINjOvSVy2b8PL6em7hmsjmF1IsDX1X 2QTWbzDbJx74/sxpI+522XV9RmnP15w1XJU76f5U/58KP19EPXN+s3al1bHY06brndM2q86o n32qvPmOZp7dzClut39mOq7YLMCkYfjOc962qz6dMVNu/JDWenFvffZJzbkSncGJ7tc0u8y7 nA0+mMlpliixFGckGmoxFxUnAgBG3FYOvAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4MJxS4Tq-oxihiJxiNdKnp60a4Q>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 09:15:58 -0000

Hi,

I=B9ve created a pull request with the changes based on Brian=B9s comments.

https://github.com/cdh4u/draft-sctp-sdp/pull/10


Regards,

Christer


On 05/02/17 21:05, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:

>Hi Christer,
>On 06/02/2017 03:14, Christer Holmberg wrote:
>> Hi Brian,
>>=20
>> Thanks for your review! Please see inline.
>>=20
>> ...
>>=20
>> Comments:
>> ---------
>>=20
>>> Two points I noted in the writeup:
>>> "There are existing implementations of earlier versions of the
>>>document..."
>>>
>>> Excellent, but I wonder why we don't see Implementation Status
>>>sections under RFC 6982 in more Last Call drafts.
>>=20
>> Perhaps a topic for an IETF chairs lunch presentation?
>
>Or at least a short reminder!
>
>>=20
>> I have to admit that I did not know about 6982 (now obsoleted by 7942).
>>My suggestion would to not collect that information for this draft at
>>this point of time, as it could take some time.
>
>Agreed.
>
>>> "IPv6 address examples are not necessary since IP version differences
>>>are immaterial to the purpose of the specification."
>>>
>>> It's just as easy to give an IPv6 example though, and more future
>>>proof.
>>=20
>> I can modify the address in the example, from IPv4 to v6.
>
>As you wish.
>
>> Minor issue: (almost a nit)
>> ------------
>>=20
>> 1.  Introduction
>> ...
>>>>   NOTE: Due to the characteristics of TCP, usage of 'TCP/DTLS/SCTP'
>>>>   will always force ordered and reliable delivery of the SCTP
>>>>   packets, which limits the usage of the SCTP options.  Therefore, it
>>>>is
>>>>   RECOMMENDED that TCP is only used in situations where UDP traffic
>>>>   is blocked.
>>>
>>> Why would one choose 'TCP/DTLS/SCTP' rather than just 'TCP/TLS'? I
>>>don't object to it being specified, but since you
>>> don't support multihoming or multiple associations, what is the use
>>>case, in a few words?
>>=20
>> SCTP supports multiple SCTP streams over a single association, and you
>>can still use that with 'TCP/DTLS/SCTP'. E.g, the WebRTC Data Channel
>>protocol uses two streams to realize a data channel.
>
>OK.
>
>(I now remember that I raised essentially the same question when reviewing
>draft-ietf-clue-datachannel. Actually I'm glad to see SCTP proving
>useful.)
>
>> I could modify the first sentence as following:
>>=20
>>         "NOTE: Due to the characteristics of TCP, while multiple SCTP
>>streams
>>          can still be used, usage of 'TCP/DTLS/SCTP' will always
>>force...."
>
>OK
>
>>=20
>> Nits:
>> -----
>>=20
>>>> 4.4.2.  SDP Media Description values
>>>>
>>>>      m=3D line parameter        parameter value(s)
>>>>    =20
>>>> ------------------------------------------------------------------
>>>>      <media>:                 "application"
>>>>      <proto>:                 "UDP/DTLS/SCTP" or "TCP/DTLS/SCTP"
>>>>      <port>:                  UDP port number (for "UDP/DTLS/SCTP")
>>>>                               TCP port number (for ""UDP/DTLS/SCTP")
>>>
>>> I think the last line should be: TCP port number (for "TCP/DTLS/SCTP")
>>=20
>> Correct. Will be fixed.
>>=20
>>> There is some inconsistency in the use of quotation marks:
>>>"UDP/DTLS/SCTP" or 'UDP/DTLS/SCTP'
>>=20
>> I'll fix that. I will use single quotes.
>
>Thanks,
>    Brian


From nobody Mon Feb  6 03:32:34 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A695C12952F; Mon,  6 Feb 2017 03:32:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Deh-izE0Nkc6; Mon,  6 Feb 2017 03:32:31 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 48696129522; Mon,  6 Feb 2017 03:32:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C90A62CCFF; Mon,  6 Feb 2017 13:32:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pStH5ftdeJI; Mon,  6 Feb 2017 13:32:29 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5DBC92CC9B; Mon,  6 Feb 2017 13:32:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
Date: Mon, 6 Feb 2017 13:32:29 +0200
Message-Id: <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0gKYboPDXWKZ_RHJfxfoYdCkA0o>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, gen-art@ietf.org, ccamp@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 11:32:33 -0000

--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Pete. Authors, any comments?

Jari


--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYmF7NAAoJEM80gCTQU46qFGoP/1b4R8OjCZxXHEB929EL2QaT
jgV6eZoJCCY8b1gQU7YrzSpfNEYD8KJvpbXJOC4xFsvu644S8m4VSTjEAX/DJ2TQ
pOakW/itbv50uwrcYAoKNMQ3qRryAjI66YM1NfHDiL7II15vc9DFy7KMS4grWdGT
h+hIhfefaLCa1cxpGE1rsGAsKW+zpHnEt4wm5hP1BKv9UtDuI6DZ0f+yAbAtRstH
J60Ovd0v8/4Lxqf/CnrI4gI713iYhOCQEv0+TjtsWtWAY6/UNG27dlKgAxpg7qcg
j9scb63grTM8uLNf8rUCYjTe7z3YIaAry6c2bnjuGvin1rVkRzF0I8jz719c6ZND
t78xEQwvEcZmwPhlnb9+6xgpgHDYQAgNsbv6nn6bsQWs7Dt/DYtyG/aLEYHST5Jy
HvSYFxU9ObmYG2ss8pqltJALbBkadYcSW04z3vPGM6Odglq72+d44w6pvl1Eu4Ow
QBDOXH6xuHBh0TJh/4kpg5QJo4706E+30x5Oy1z/hOZnYaDIErHBueWDfp86pHrG
Gq5Aye9jhpeBUuCjiAz60etcXMFCUKunO77o3sClCYWknKpb1LKscy4/BBbqfnO8
yJAZYuftq0qxPZyQR+egw/dmNFWotC/MrfPpQudQ/27/9TX5Kvt88ueUtLHFZN+E
jvxZCm++jeinYqGaXlaU
=MqAt
-----END PGP SIGNATURE-----

--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E--


From nobody Mon Feb  6 05:37:51 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01ABC129D7A; Mon,  6 Feb 2017 05:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2a0ezxfJ04mf; Mon,  6 Feb 2017 05:37:43 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0AE5129D6B; Mon,  6 Feb 2017 05:37:42 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-42-58987c242f2a
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 54.70.22993.42C78985; Mon,  6 Feb 2017 14:37:40 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.63) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 6 Feb 2017 14:36:48 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=PSkq5iPphyhTo00k+E8Rdo2mzZVEUzFRw0yBt7u7l/o=; b=jacihOEUHHyRqP/h7NTRJNr8MeN0GTLCTnrACZJ8oa/mIKvegYxxQVUhXjf6dx3w+Ijl89WEqj7V7px1qc/WsOv1bNHg1hGq71I6Tm55F7ZXBlV1UCQ+yr1NT5V9adSWQiXNIJvPop2Oj8RiZ+QYMK5wxyCFIReN04yf0RRvQ50=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0996.eurprd07.prod.outlook.com (10.162.37.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Mon, 6 Feb 2017 13:36:46 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Mon, 6 Feb 2017 13:36:46 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Jari Arkko <jari.arkko@piuha.net>, Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9A=
Date: Mon, 6 Feb 2017 13:36:46 +0000
Message-ID: <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
In-Reply-To: <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 2528a4d3-45de-45cb-4f9f-08d44e953246
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0996;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0996; 7:WZxsaZH8S8PYhlhZR3FPmyS0eybqwum5QuN8YMhlGqnni70vB1Y1qfEOo9lJCdF2hc+Do36Zu45RK5JpPdg5BgkHup/O+gDJED5ZeKfv9pXqyNH/aUC5lbC1tNnQfSJEhJVcpJsVCZFcoxn5gUTjJRQFjxkNd9+M5qkHeGfu7GsJ77itEO2GceVF+ZFIQ1blP0CuKIWVCGGlnwdHI+lt1VpbJI9Y0KIAjGj0WZ8yINCHYk0Nobhgl/0v+lmw1nNkrABYJ8ncvBlkaIbEG9QVc901GJG053c7ClRYSAl61yFLc2Hh74uri4+GD0VoIcpcbTw1UdAiiAoRucAOGvx0tCxnc4Pw0IIHghKZOSILyn4lMOtQ5Jso8lPjwVSTw3cG4zsnGb+XPB3Ld8rBOUXebaYNVso57YN9RyHSehIBWBcCmWI4raFo9DoF/bVwDbhedqCaIoRb8g5oeeO6itUYbm7eCqf5ktT9e8DB6ydDVoshshN4Y+S07jyZU+O1tUDv4/ZXMlarCIP48GzYca/HxA==
x-microsoft-antispam-prvs: <AM2PR07MB099690999327245292673B4EF0400@AM2PR07MB0996.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(20170203043)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123558025)(20161123562025)(20161123560025)(20161123555025)(6072148); SRVR:AM2PR07MB0996; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0996; 
x-forefront-prvs: 0210479ED8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(51914003)(13464003)(189002)(2900100001)(81156014)(8936002)(74316002)(81166006)(2950100002)(53936002)(8676002)(50986999)(38730400001)(6436002)(76176999)(54356999)(6506006)(25786008)(77096006)(189998001)(7696004)(5001770100001)(97736004)(9686003)(99286003)(54906002)(55016002)(229853002)(92566002)(5660300001)(230783001)(86362001)(6116002)(3280700002)(102836003)(7736002)(6246003)(3846002)(2906002)(105586002)(4326007)(122556002)(68736007)(305945005)(3660700001)(101416001)(66066001)(33656002)(106116001)(106356001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0996; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2017 13:36:46.4613 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0996
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfSzUcRzH9/39fnf9ztz2dZ4+roetm7+EirKbQq2H2WKqf7LK6spvno/u xw3VkshD1JXOY4W6RYQxOkXEKDWhRiTFuHm61SxTmSJ3X2399/5+Xu/v+/P5fPdlaUmRQMqG KWM5lVIRKRNaMAWBeh8Xxwv5gdt+6DzkhjtDjPze72pKPjA7z8gna4sZeX5LuVDeP5BC7xH6 6nSLlG+DLk/oe187iQ7Txy12B3ORYWpOtdX7tEXoQo4oZlIa35FbjJKQxjYTiVjAO2ClZVqY iSxYCa5GUGJsRuTwCsHl4npkcjE4m4bvuZYE5FBgzOoyAwnuRPCpYFWzrBB7gqHdz1S2wUeg O0VPmfw0Hl8NWs6mTMAaH4IXH+rWEZMfLD7tpYn2hAXjLEOaOYJm/r05X4xPQmVtj4D0ugS/ ajQCUy8R9oJnE86mMsJ28PPNY3M8je1h2FBMkc0w6JpJPGBbmJlYFhD/GahJbVzzbIa+ikLK FAnYH+qaNpGyPyxd7zSPD7ibgda3RkRABOhTe9fuOkF6R+GaqYyCha9jDAEbQNvUwxAwIYCU oo8MWYCDsqpURB5CCp/7M5AGORX+NzjRrjCkvS0kegs8LDXShea3sILXBQamBDEVyJbneD4q xM3dlVOFneX5aKWrkoutQ6tfpq1+yaURVRr3tiPMIpmleM4rL1AiUKj5hKh2BCwtsxEHqfMD JeJgRUIip4o+pYqL5Ph2tJ5lZPZij0ejxyQ4RBHLRXBcDKf6RylWJE1CArc0Q+UTD034zvHk pvKjaVcPODqMdl5UcSN3z6UmX7NK58VBpZ12wye+6bVL+l3e6beSqpwHB/JvzMW39mX7J85Y P+9yaGie2v+gLUbtXB/k5PqH2Sidc1+8kpF88DznNxUw0s0HjNmH2mRpfV6W1Azkxd2c7xjc p12ZDs991/tFxvChiu1OtIpX/AVgPjrgLgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/TYMHaerwJvSDpGBBquzgE7822kE>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 13:37:45 -0000

Hi Jari, Pete,

First of all thanks for the accurate review.

All the nits/editorial comments are correct and will be fixed.

Regarding the minor issue:=20

> 4.1.1:
>=20
> The figure is a bit confusing: There might not exist a "Max Slot Width at=
 Priority
> 7" if bit 7 is clear in the Priority field, correct?
> Perhaps it would be better to just show that as "..." or "Max Slot Width =
at
> Priority n". The thing is, it might only be a single value, followed by t=
he
> padding, so having the second value in there might be misleading. (Perhap=
s
> similar constructs are used in other MPLS docs and people will understand=
. But
> it took me a while to figure it out.)
>=20

it was difficult to express in the figure the fact that only some of the pr=
iorities are advertised. As you said it could be one, two or any number up =
to 8.=20
What about a single field (with ~ on the borders to indicate that it can ha=
ve variable length) saying "Max Slot Width at Prio n" and then say that 16 =
bits are used for each prio and when an odd number of priorities is used th=
e field is padded to line up with multiples of 32 bits?

> The discussion of Priority was very confusing for me. In the third senten=
ce, do
> you mean, "A bit is set (1) corresponding to each priority represented in=
 the
> sub-TLV, and clear (0) for each priority not represented in the sub-TLV"?=
 I don't
> understand the MUST/MUST NOT as you had it. And I don't understand the
> last sentence at all. Are you trying to say, "The leftmost bit (priority =
level 0)
> MUST be set, and priority level 0 MUST be advertised in the sub-TLV."?
> Otherwise, I don't get it.

It means that if the priority field is set to e.g. 10010010 in the followin=
g you would find 4 fields indicating respectively: Max Slot Width at Priori=
ty 0, Max Slot Width at Priority 3, Max Slot Width at Priority 6 and since =
they are 3 a 16 bits padding to 32 bits.=20
It also means that at least one priority must be advertised (i.e. priority =
00000000 is not allowed).

>=20
> I don't understand the MAY in the last sentence. Does that mean that I MA=
Y
> also set it to the highest possible nominal central frequency supported b=
y the
> link? I don't understand what that sentence is trying to tell me.
>

An example is provided in section 4.1.2, where the available range goes fro=
m -2 to +8 but the range supported by the link goes from -9 to +11. The sen=
tence means that even if not available it could be possible to indicate als=
o n=3D-9 to indicate the starting point of the range supported by the link.=
=20

  " In this example, it is assumed that the lowest nominal central
   frequency supported is n=3D -9 and the highest is n=3D11. Note they
   cannot be used as a nominal central frequency for setting up a LSP,
   but merely as the way to express the supported frequency range."

I'm ok with dropping the sentence.

Thank you
Daniele=20

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: luned=EC 6 febbraio 2017 12:32
> To: Pete Resnick <presnick@qti.qualcomm.com>
> Cc: gen-art@ietf.org; draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.or=
g;
> ccamp@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-=
07
>=20
> Thanks for your review, Pete. Authors, any comments?
>=20
> Jari


From nobody Mon Feb  6 06:14:44 2017
Return-Path: <sakimura@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC69A129DA3; Mon,  6 Feb 2017 06:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9ULawRVM7Xc; Mon,  6 Feb 2017 06:14:34 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3EA1129D9A; Mon,  6 Feb 2017 06:14:33 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id b65so122241168wmf.0; Mon, 06 Feb 2017 06:14:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iqBblcxBJpi94r0QkcVPXBz5Ak3RnGNdiseim23l63Y=; b=Z4qk0H28s5x8/cN2gCOX44yygp7owC4OexSZsEoBArWKs3RhFD1Gw6mWEdcibR2SpT r94lCuL1OWezUxOzv6Z47p6LLK9GKe/yZlEAuHSAMfq0yDFH25gVp5sCZtG/Yb/xo6QZ JScaGEhDnnzDFec7Ag8aN/VJvD797L81OsNKRV/nRzbrvc6GZo8belSbdauQhnRenvUh VPMRIXhL4gyLOiAunGkQ2UuBh+4oCC7kh/Gm2ASkBARODWLqaRUlKVHmFp4la3/+epvD a6yE5tnjtKmahIXokC8N0UqMdtWcTxxFPBg5B0YVg0PqgJ80XEhcT1eOaE2Gy0Sm6nex 16hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iqBblcxBJpi94r0QkcVPXBz5Ak3RnGNdiseim23l63Y=; b=iejT9xN/M+KOr9LvdafiOXyGTX734BA406hRbLqy2Hcohw0pZrzi7pjpoyA2bTZyVM R9O7ff6oaqWl1SOwjda/cwkZEzyQNjywtgyUHKgy8lPxOA5cb6nEm9OCCXK3kGcbICPL HZPm1cZDH3QMpRWFUWrInDP8NP2qUaTaDk7ta+XtaU9GAZHZ1QnA2/CUTHLYpBMnD5iA /6/Sq+6IyVqmXtM4PQLlxvYn+guRvAFUSAVQS+1/N07FNSVPsxfS0GHTViG7jz/EOqjv 1D5aI5YA7do+5DURY5estCDBt/+QKLFpumo0QdVfaiDtXPgHt7CuBBX2ZqpuWYupCgWl 88wA==
X-Gm-Message-State: AMke39kvq8OKJYdiF24k5eIH2AwAj4GRUEeELVJTxWA9HLJ2sEtzx7MmN1p2Vsqiem4N6rj639Cq8XdmuFCDmQ==
X-Received: by 10.28.1.216 with SMTP id 207mr9593070wmb.7.1486390472437; Mon, 06 Feb 2017 06:14:32 -0800 (PST)
MIME-Version: 1.0
References: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
In-Reply-To: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Mon, 06 Feb 2017 14:14:22 +0000
Message-ID: <CABzCy2AUXh5kW_+-0T4r2HWqyhrmQ5DLQ6-GPiXdwqzE5ZOHmA@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
Content-Type: multipart/alternative; boundary=001a113c73f81b78bd0547dd4018
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/onjT_vKIPRPyCN63NT3yWSZXGEc>
Cc: ietf@ietf.org, draft-ietf-oauth-jwsreq.all@ietf.org, oauth@ietf.org
Subject: Re: [Gen-art] [OAUTH-WG] Review of draft-ietf-oauth-jwsreq-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 14:14:36 -0000

--001a113c73f81b78bd0547dd4018
Content-Type: text/plain; charset=UTF-8

Thanks Joel,

-11 only contains the fixes to the comments received by Jan. 17. I am now
applying all the edits needed for the comments received after that.
The next version will fix the problem you have pointed out.

Best,

Nat

On Fri, Feb 3, 2017 at 8:03 AM Joel Halpern <jmh@joelhalpern.com> wrote:

> Reviewer: Joel Halpern
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-oauth-jwsreq-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-02
> IETF LC End Date: 2017-02-13
> IESG Telechat date: 2017-02-16
>
> Summary: This document is ready for publication as a Proposed
> Standard
>
> Major issues: N/A
>
> Minor issues:
>     Why is the example if section 4 (and others later on) described
> as
> "non-normative"?  Is it incomplete?  incorrect?  An example is, by
> definition, not a full specification.  The language seems designed to
> reduce the value of the example.  I would recommend removing all the
> "non-normative" notes from the examples.  They are clearly stated to
> be examples.
>
> Nits/editorial comments:
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
-- 

Nat Sakimura

Chairman of the Board, OpenID Foundation

--001a113c73f81b78bd0547dd4018
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Joel,=C2=A0<div><br></div><div>-11 only contains th=
e fixes to the comments received by Jan. 17. I am now applying all the edit=
s needed for the comments received after that.=C2=A0</div><div>The next ver=
sion will fix the problem you have pointed out.=C2=A0</div><div><br></div><=
div>Best,=C2=A0</div><div><br></div><div>Nat</div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr">On Fri, Feb 3, 2017 at 8:03 AM Joel Halpern &l=
t;<a href=3D"mailto:jmh@joelhalpern.com">jmh@joelhalpern.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Reviewer: Joel Halpern<br class=3D=
"gmail_msg">
Review result: Not Ready<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I am the assigned Gen-ART reviewer for this draft. The General Area<br clas=
s=3D"gmail_msg">
Review Team (Gen-ART) reviews all IETF documents being processed<br class=
=3D"gmail_msg">
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br c=
lass=3D"gmail_msg">
like any other last call comments.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
For more information, please see the FAQ at<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" class=3D"gmail_msg" target=3D"_blank">https://trac.ietf.org/trac/gen/=
wiki/GenArtfaq</a>&gt;.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Document: draft-ietf-oauth-jwsreq-??<br class=3D"gmail_msg">
Reviewer: Joel Halpern<br class=3D"gmail_msg">
Review Date: 2017-02-02<br class=3D"gmail_msg">
IETF LC End Date: 2017-02-13<br class=3D"gmail_msg">
IESG Telechat date: 2017-02-16<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Summary: This document is ready for publication as a Proposed<br class=3D"g=
mail_msg">
Standard<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Major issues: N/A<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Minor issues:<br class=3D"gmail_msg">
=C2=A0 =C2=A0 Why is the example if section 4 (and others later on) describ=
ed<br class=3D"gmail_msg">
as<br class=3D"gmail_msg">
&quot;non-normative&quot;?=C2=A0 Is it incomplete?=C2=A0 incorrect?=C2=A0 A=
n example is, by<br class=3D"gmail_msg">
definition, not a full specification.=C2=A0 The language seems designed to<=
br class=3D"gmail_msg">
reduce the value of the example.=C2=A0 I would recommend removing all the<b=
r class=3D"gmail_msg">
&quot;non-normative&quot; notes from the examples.=C2=A0 They are clearly s=
tated to<br class=3D"gmail_msg">
be examples.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Nits/editorial comments:<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
_______________________________________________<br class=3D"gmail_msg">
OAuth mailing list<br class=3D"gmail_msg">
<a href=3D"mailto:OAuth@ietf.org" class=3D"gmail_msg" target=3D"_blank">OAu=
th@ietf.org</a><br class=3D"gmail_msg">
<a href=3D"https://www.ietf.org/mailman/listinfo/oauth" rel=3D"noreferrer" =
class=3D"gmail_msg" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/oauth</a><br class=3D"gmail_msg">
</blockquote></div><div dir=3D"ltr">-- <br></div><div data-smartmail=3D"gma=
il_signature"><p dir=3D"ltr">Nat Sakimura</p>
<p dir=3D"ltr">Chairman of the Board, OpenID Foundation</p>
</div>

--001a113c73f81b78bd0547dd4018--


From nobody Mon Feb  6 09:37:59 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A27129418; Mon,  6 Feb 2017 09:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LvvZ10Mgjgt; Mon,  6 Feb 2017 09:37:52 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0420E1293D8; Mon,  6 Feb 2017 09:37:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486402672; x=1517938672; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=8CUooSX7jNZmLb4sycMKsdyMVTjQUMs+U9S55/nlvxM=; b=rvUXdQEE8kNkTPeDOTwB6Q/FIArktiaci7Gn5XUZMLZ3aqCl8FLH47Dl /vFq7vyV9D7QTpI4iz4qLsouAlKZLFSidDO1zqdO3zFf7gH6s+ZT3L9ZH Bxz06nG3cPWWdczljRJg0Zxese+3jCmve72HFSDeAiihjdAbEm1ZSIuFD c=;
X-IronPort-AV: E=Sophos;i="5.33,342,1477983600";  d="scan'208,217";a="356023463"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine02.qualcomm.com with ESMTP; 06 Feb 2017 09:37:51 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8431"; a="861405932"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Feb 2017 09:37:51 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 6 Feb 2017 09:37:50 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Date: Mon, 6 Feb 2017 11:37:48 -0600
Message-ID: <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CqPAWGTMlE5rbPF90kr1uwtFy00>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 17:37:53 -0000

--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

On 6 Feb 2017, at 7:36, Daniele Ceccarelli wrote:

> Hi Jari, Pete,
>
> First of all thanks for the accurate review.
>
> All the nits/editorial comments are correct and will be fixed.
>
> Regarding the minor issue:
>
>> 4.1.1:
>>
>> The figure is a bit confusing: There might not exist a "Max Slot 
>> Width at Priority
>> 7" if bit 7 is clear in the Priority field, correct?
>> Perhaps it would be better to just show that as "..." or "Max Slot 
>> Width at
>> Priority n". The thing is, it might only be a single value, followed 
>> by the
>> padding, so having the second value in there might be misleading. 
>> (Perhaps
>> similar constructs are used in other MPLS docs and people will 
>> understand. But
>> it took me a while to figure it out.)
>>
>
> it was difficult to express in the figure the fact that only some of 
> the priorities are advertised. As you said it could be one, two or any 
> number up to 8.
> What about a single field (with ~ on the borders to indicate that it 
> can have variable length) saying "Max Slot Width at Prio n" and then 
> say that 16 bits are used for each prio and when an odd number of 
> priorities is used the field is padded to line up with multiples of 32 
> bits?

Yes, I think that would make more sense to me.

>> The discussion of Priority was very confusing for me. In the third 
>> sentence, do
>> you mean, "A bit is set (1) corresponding to each priority 
>> represented in the
>> sub-TLV, and clear (0) for each priority not represented in the 
>> sub-TLV"? I don't
>> understand the MUST/MUST NOT as you had it. And I don't understand 
>> the
>> last sentence at all. Are you trying to say, "The leftmost bit 
>> (priority level 0)
>> MUST be set, and priority level 0 MUST be advertised in the 
>> sub-TLV."?
>> Otherwise, I don't get it.
>
> It means that if the priority field is set to e.g. 10010010 in the 
> following you would find 4 fields indicating respectively: Max Slot 
> Width at Priority 0, Max Slot Width at Priority 3, Max Slot Width at 
> Priority 6 and since they are 3 a 16 bits padding to 32 bits.

OK, then I think my sentence is clearer for that: "A bit is set (1) 
corresponding to each priority represented in the sub-TLV, and clear (0) 
for each priority not represented in the sub-TLV."

> It also means that at least one priority must be advertised (i.e. 
> priority 00000000 is not allowed).

I get that part ("At least one priority level MUST be advertised"). It's 
the end I don't understand: "that, unless overridden by local policy, 
SHALL be at priority level 0." What does that mean?

>> I don't understand the MAY in the last sentence. Does that mean that 
>> I MAY
>> also set it to the highest possible nominal central frequency 
>> supported by the
>> link? I don't understand what that sentence is trying to tell me.
>>
>
> An example is provided in section 4.1.2, where the available range 
> goes from -2 to +8 but the range supported by the link goes from -9 to 
> +11. The sentence means that even if not available it could be 
> possible to indicate also n=-9 to indicate the starting point of the 
> range supported by the link.
>
>   " In this example, it is assumed that the lowest nominal central
>    frequency supported is n= -9 and the highest is n=11. Note they
>    cannot be used as a nominal central frequency for setting up a LSP,
>    but merely as the way to express the supported frequency range."
>
> I'm ok with dropping the sentence.

I think dropping the sentence would make the most sense.

> Thank you
> Daniele

Thanks for considering my suggested changes.

pr

>> -----Original Message-----
>> From: Jari Arkko [mailto:jari.arkko@piuha.net]
>> Sent: lunedì 6 febbraio 2017 12:32
>> To: Pete Resnick <presnick@qti.qualcomm.com>
>> Cc: gen-art@ietf.org; 
>> draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org;
>> ccamp@ietf.org; ietf@ietf.org
>> Subject: Re: [Gen-art] Review of 
>> draft-ietf-ccamp-flexible-grid-ospf-ext-07
>>
>> Thanks for your review, Pete. Authors, any comments?
>>
>> Jari


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 6 Feb 2017, at 7:36, Daniele Ceccarelli wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i Jari, Pete,<br>
<br>
First of all thanks for the accurate review.<br>
<br>
All the nits/editorial comments are correct and will be fixed.<br>
<br>
Regarding the minor issue:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">4.1.1:<br>
<br>
The figure is a bit confusing: There might not exist a "Max Slot Width at=
 Priority<br>
7" if bit 7 is clear in the Priority field, correct?<br>
Perhaps it would be better to just show that as "..." or "Max Slot Width =
at<br>
Priority n". The thing is, it might only be a single value, followed by t=
he<br>
padding, so having the second value in there might be misleading. (Perhap=
s<br>
similar constructs are used in other MPLS docs and people will understand=
=2E But<br>
it took me a while to figure it out.)<br>
</p>
</blockquote><p dir=3D"auto">it was difficult to express in the figure th=
e fact that only some of the priorities are advertised. As you said it co=
uld be one, two or any number up to 8.<br>
What about a single field (with ~ on the borders to indicate that it can =
have variable length) saying "Max Slot Width at Prio n" and then say that=
 16 bits are used for each prio and when an odd number of priorities is u=
sed the field is padded to line up with multiples of 32 bits?</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Yes, I think that would make more sense to me.</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">The discussion of Priority w=
as very confusing for me. In the third sentence, do<br>
you mean, "A bit is set (1) corresponding to each priority represented in=
 the<br>
sub-TLV, and clear (0) for each priority not represented in the sub-TLV"?=
 I don't<br>
understand the MUST/MUST NOT as you had it. And I don't understand the<br=
>
last sentence at all. Are you trying to say, "The leftmost bit (priority =
level 0)<br>
MUST be set, and priority level 0 MUST be advertised in the sub-TLV."?<br=
>
Otherwise, I don't get it.</p>
</blockquote><p dir=3D"auto">It means that if the priority field is set t=
o e.g. 10010010 in the following you would find 4 fields indicating respe=
ctively: Max Slot Width at Priority 0, Max Slot Width at Priority 3, Max =
Slot Width at Priority 6 and since they are 3 a 16 bits padding to 32 bit=
s.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">OK, then I think my sentence is clearer for that: "A bit =
is set (1) corresponding to each priority represented in the sub-TLV, and=
 clear (0) for each priority not represented in the sub-TLV."</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">I=
t also means that at least one priority must be advertised (i.e. priority=
 00000000 is not allowed).</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">I get that part ("At least one priority level MUST be adv=
ertised"). It's the end I don't understand: "that, unless overridden by l=
ocal policy, SHALL be at priority level 0." What does that mean?</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">I don't understand the MAY i=
n the last sentence. Does that mean that I MAY<br>
also set it to the highest possible nominal central frequency supported b=
y the<br>
link? I don't understand what that sentence is trying to tell me.<br>
</p>
</blockquote><p dir=3D"auto">An example is provided in section 4.1.2, whe=
re the available range goes from -2 to +8 but the range supported by the =
link goes from -9 to +11. The sentence means that even if not available i=
t could be possible to indicate also n=3D-9 to indicate the starting poin=
t of the range supported by the link.<br>
<br>
  " In this example, it is assumed that the lowest nominal central<br>
   frequency supported is n=3D -9 and the highest is n=3D11. Note they<br=
>
   cannot be used as a nominal central frequency for setting up a LSP,<br=
>
   but merely as the way to express the supported frequency range."<br>
<br>
I'm ok with dropping the sentence.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">I think dropping the sentence would make the most sense.<=
/p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">T=
hank you<br>
Daniele</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Thanks for considering my suggested changes.</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">-----Original Message-----<b=
r>
From: Jari Arkko [<a href=3D"mailto:jari.arkko@piuha.net" style=3D"color:=
#999">mailto:jari.arkko@piuha.net</a>]<br>
Sent: luned=C3=AC 6 febbraio 2017 12:32<br>
To: Pete Resnick &lt;presnick@qti.qualcomm.com&gt;<br>
Cc: gen-art@ietf.org; draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.or=
g;<br>
ccamp@ietf.org; ietf@ietf.org<br>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-=
07<br>
<br>
Thanks for your review, Pete. Authors, any comments?<br>
<br>
Jari</p>
</blockquote></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=--


From nobody Mon Feb  6 13:05:43 2017
Return-Path: <vijay.gurbani@nokia-bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7287D1294C0 for <gen-art@ietfa.amsl.com>; Mon,  6 Feb 2017 13:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zngQk_v5ZY52 for <gen-art@ietfa.amsl.com>; Mon,  6 Feb 2017 13:05:40 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-02.alcatel-lucent.com [135.245.18.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ADA1129482 for <gen-art@ietf.org>; Mon,  6 Feb 2017 13:05:39 -0800 (PST)
Received: from us70uumx4.dmz.alcatel-lucent.com (unknown [135.245.18.16]) by Websense Email Security Gateway with ESMTPS id E14CE1FCA91D2; Mon,  6 Feb 2017 21:05:35 +0000 (GMT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (us70uusmtp4.zam.alcatel-lucent.com [135.5.2.66]) by us70uumx4.dmz.alcatel-lucent.com (GMO) with ESMTP id v16L5bx7014924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2017 21:05:38 GMT
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id v16L5abE007176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2017 21:05:37 GMT
Received: from [135.185.238.154] (shoonya.ih.lucent.com [135.185.238.154]) by umail.lucent.com (8.13.8/TPES) with ESMTP id v16L5aFx016688; Mon, 6 Feb 2017 15:05:36 -0600 (CST)
To: "Peterson, Jon" <jon.peterson@neustar.biz>
References: <4a800ae0-b09f-675d-c287-81689b271f4d@nokia-bell-labs.com> <D4786999.1CB19F%jon.peterson@neustar.biz>
From: "Vijay K.Gurbani" <vijay.gurbani@nokia-bell-labs.com>
Message-ID: <dcca6b06-5bb8-6920-17a8-7b25a233bef3@nokia-bell-labs.com>
Date: Mon, 6 Feb 2017 15:05:35 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <D4786999.1CB19F%jon.peterson@neustar.biz>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/x44K69tN9tG7lsUw6REVPEkLNQk>
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] COMPLETE Gen-ART review of draft-ietf-stir-rfc4474bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 21:05:42 -0000

On 01/24/2017 12:59 PM, Peterson, Jon wrote:
 > Hey Vijay,
 >
 > Took me a bit to get back to you here, sorry. Appreciate the notes.
 > Here's my thoughts.


Jon: No worries.  I must also apologize for the delay in getting back
to you.

More inline (please see to end).  I have re-arranged your comments so
that those we agree on appear at the end.

 >> Major:
 >>
 >> - S7.4 contains requirements for a credential system, and the draft
 >>  assumes that any credential system that works with the draft will
 >>  adhere to the five expectations outlined in the section.
 >>
 >>  My question is how do we ensure that these expectations are met?
 >>  Through IANA?  (But there is no subsection in the IANA registry
 >>  section corresponding to this.)  Through some form of domain expert
 >>  required to review a specification outlining the five expectations?
 >>  It seems to me that since the credential service is an integral part
 >>  of the system, some manner of review by the appropriate working
 >> group (or a designated expert) should take place.
 >
 > I don't think this is an IANA-like thing where failure to comply with
 > these requirements will result in something like a code point
 > overload.  The relevant text in 7.4 says "in order for a credential
 > system to work with this mechanism, its specification must detail"
 > the following points.  If the credential system doesn't do these
 > things, it won't work with the rfc4474bis mechanism.
 >
 > I think this is pretty typical of how requirements language like this
 > fits into our process - we may as part of a WGLC for a document ask
 > if it meets requirements given in a previous RFC, but it's not a
 > designated expert kind of thing. I imagine that any chartered
 > deliverable, say, to do a credential system might be held to that bar
 > - but we don't put text to that effect in RFCs I think.
 >
 > So in short I hear what you're saying but I think this one is fine.

OK; I wanted to at least raise the issue to make sure that it was
subjected to some thought.

 >> - S6.2.2, the 436 response case.  I am a big believer of protocols
 >>  imparting as much error information as they can, especially if the
 >>  protocol is as expressive as SIP.  Since this error code is
 >> repairable, why not provide information to the repairer on exactly
 >> which Identity header was 'bad'.  Something like:
 >>
 >>  436 Bad Identity Info
 >>  Warning: 399 https://biloxi.example.org/biloxi.cert is not
 >>  accessible
 >>
 >>  Or message/sipfrag could be used as well.
 >>
 >>  We do not have to make such debugging/error information propagation
 >>  mandatory (MUST), but we should at least alert the implementers to
 >>  it existence (SHOULD).
 >
 > I know that ATIS has been playing around with some Reason codes for
 > responses to give additional information, especially in provisional
 > responses. I can see the use of this, but I'm not sure at this stage
 > in rfc4474bis's lifecycle I really want to open this up to new
 > functionality along those lines. It seems to me that this could be
 > broken off as a modular chunk of future work.
 >
 > But how about this - I can put in some text to 6.2.2 to the effect
 > that future specifications could look at Warnings or Reason codes as
 > a means to disambiguate the source of errors etc?

Sure; that works for me.  I will defer to you if you feel, as you write
above, that you don't want to open up new functionality at this stage of
rfc4474bis.  But that said, I will appreciate your to-appear text in
S6.2.2.  I think that if protocols have primitives to aid in being
descriptive, then designers should make use of the said primitives.

 >> - S6.2.2, the 437 response case.  Same reasoning as above.  Example:
 >>
 >>  437 Unsupported credential
 >>  Warning: 399 https://biloxi.example.org/biloxi.cert
 >
 > I think a blanket statement about future work at the end of the
 > section could cover it.

OK.

 >> - S3: s/can issue them an identity/issues an identity/
 >
 > I like the original better. The organization could also issue them a
 > telephone number, say, instead of a SIP URI.

I don't think that my suggested change precludes issuance of other
forms of identity.  I think that "issues an identity" reads better
and is less colloquial; but if I cannot convince you (as the editor),
then no worries.  I'll leave it up to you.

That's it.  For the sake of completeness, I list below the changes
agreed upon.  Thanks for your time attending to my comments.

 >
 >>
 >> Minor:
 >>
 >> - S3: "baseline SIP" ==> What do you mean by this?  (I know what you
 >>  mean, of course, but others reading the document may not.)  Perhaps
 >>  the following substitution is better?
 >>
 >>  s/purposes of baseline SIP,/use of SIP as defined in [RFC 3261],/
 >
 > Good catch, done.

 >>
 >> Nits:
 >>
 >> - S1: "However, the recipient of a SIP request has no way to verify
 >>  that the From header field has been populated appropriately, in the
 >>  absence of some sort of cryptographic authentication mechanism."
 >>  Changing the order of the dependent clauses may lead to better
 >>  readability.  That is,
 >>  "However, in the absence of some sort of cryptographic
 >> authentication mechanism, the recipient of a SIP request has no way
 >> to verify that the From header field has been populated
 >> appropriately."
 >
 > Done.

 >> - S1: You may want to define what "swatting" is for those not well-
 >>  versed in ART terminology.
 >
 > The "as described in [RFC7340]" is there for people to read further
 > about those motivations; it does define swatting etc.

 >> - S1: "less spoofable" ... Merriam-Webster does not define
 >> "spoofable" as a word (online version).  Perhaps better to say "less
 >> amenable to spoofing" instead.  Something as the following suggested
 >> text:
 >>  "Ideally, a cryptographic approach to identity can provide a much
 >>  stronger assurance of identity than the Caller ID service used
 >>  by the public-switched telephone network today.  Such an approach
 >>  would also be less amenable to identity spoofing."
 >
 > Um... all right, I guess. Added "... and less vulnerable to spoofing"
 > to the end of the clause.

 >> - S3: s/through means entirely up to the authentication
 >> service,/through per-arranged means with the authentication service,/
 >
 > OK.

 >> - S3: s/credentials that will be trusted by relying parties to sign
 >> for telephone numbers are a key component of the
 >> architecture./credentials that will be trusted by relying parties to
 >> be authoritative for telephone numbers become a key component of the
 >> architecture./
 >
 > I think I like the original text here better.

 >> - S3: s/not so easy to/not as easy to/
 >
 > OK.

 >> - S3: s/ but this document does not mandate or specify a credential
 >>  system.  [I-D.ietf-stir-certificates] describes a credential system
 >>  compatible with this architecture./ but this document does not
 >> mandate or specify a particular credential system;
 >>  [I-D.ietf-stir-certificates] describes one credential system
 >> compatible with this architecture."
 >
 > OK.

 >> - S3 s/This is typically easier to deal with, as these identities are
 >>  issued to users by authorities over Internet domains./This is
 >>  typically easier to deal with as these identities are issued by
 >>  organizations that have authority over Internet domains./
 >
 > OK.

 >> - S3: s/prove in some fashion/proves/
 >
 > OK.

 >> - S6.2, Step 3: "The verifier must ensure that it possesses the
 >> proper keying material to validate the signature...".  Here, I
 >> believe that the verifier must ensure that it *has access to* to the
 >> proper keying material, more than the fact that it "possesses" it.
 >> Namely, the verifier needs to have access to the URI in the "info"
 >> parameter.  Whether or not it caches the certificate (thus making it
 >> "possess" it), is up to the policies of the verifier.
 >>
 >>  Summary: s/possesses/has access to/
 >
 > OK.

 >> - S7.1, first paragraph, first sentence.  With respect to my above
 >>  comment, s/have access to/possess/
 >>
 >>  The Authentication Service must not only have access to, but must
 >>  possess the private keying material.  Possession implies access, but
 >>  access may not imply possession.
 >
 > OK.

 >> - S7.1, second paragaph: s/For non-telephone number user parts/For
 >>  non-telephone number URIs/
 >
 > Um... I think the original is fine? The telephone number is in the
 > user part.
 >
 >>
 >> - S8, s/vet the identity/confirm the identity/
 >
 >
 > OK.


- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Nokia Networks
Email: vkg@bell-labs.com / vijay.gurbani@nokia-bell-labs.com
Web: https://www.bell-labs.com/usr/vijay.gurbani
Calendar: http://goo.gl/x3Ogq


From nobody Mon Feb  6 13:20:32 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 73EBD12949E; Mon,  6 Feb 2017 13:20:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms.ietf@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148641603043.18879.10370223612053997606.idtracker@ietfa.amsl.com>
Date: Mon, 06 Feb 2017 13:20:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6DIvk1TPSSB0FDxTjho1v1NrzFM>
Cc: ietf@ietf.org, draft-ietf-nfsv4-rfc5666bis.all@ietf.org, nfsv4@ietf.org
Subject: [Gen-art] Review of draft-ietf-nfsv4-rfc5666bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 21:20:30 -0000

Reviewer: Ralph Droms
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-rfc5666bis-09
Reviewer: Ralph Droms
Review Date: 2017-02-06
IETF LC End Date: 2017-02-07
IESG Telechat date: Not scheduled for a telechat

Summary: draft-ietf-nfsv4-rfc5666bis-09 is ready for publication; it
is a well-written document that I found readable and understandable
based on my basic (and, likely, quite out of date!) knowledge of ONS
RPC, XDR and NFS.

Major issues: None

Minor issues: None

Nits/editorial comments:  None



From nobody Tue Feb  7 01:37:02 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B501295EA; Tue,  7 Feb 2017 01:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6AdllDks58B; Tue,  7 Feb 2017 01:36:58 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3554C127058; Tue,  7 Feb 2017 01:36:57 -0800 (PST)
X-AuditID: c1b4fb25-4bbfb70000006c88-d7-589995350d22
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 6B.D4.27784.53599985; Tue,  7 Feb 2017 10:36:55 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.27) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 7 Feb 2017 10:36:53 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kZaYWAl40rP3n3/bUUfi0wLpE1XqIQDW8UlOj3+SVyU=; b=TinfBy0/czOCPRM0tPaClf0Lv1iO6P8i0+MhbF85PxU9n2Wcs7S0iaWW+Y2QtuUK6mw61x6uCJI/LwWUU2Ze/vrGxTmx95Gr2bmvhvFzpnqmmKMb+GMR43zxHcJrv43ZnyM+ATPrDUIa+iHbt7uwLM3psIhiDwO1dLvLyASI5jE=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0993.eurprd07.prod.outlook.com (10.162.37.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Tue, 7 Feb 2017 09:36:51 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Tue, 7 Feb 2017 09:36:51 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2A
Date: Tue, 7 Feb 2017 09:36:51 +0000
Message-ID: <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
In-Reply-To: <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 89430744-6d54-4be3-76e9-08d44f3cd89c
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0993;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0993; 7:0TVbv4OBIJIOxY/wkMj88yoBi/co9Sv26VhsCevf+F0KHR7IYR/nZiqxabH4VwCYCoy25fM0fqcWxwN2QVh7fWGKSFtx4mBQdNxg7wNqKYT2VlSfjFMj4bNzguB7LAjoo6F3kxbNTwJe7GiWOgr+kT/mbXTzB2jJpHDCNkrDty4Jn5EhumLvBQY1FdwcU7P4b1wcwuzDlZsV5Nv05/8MPwcb+ny340cffoR0bPrrit8wyOGAA01rQVl1SkLlb6XioCiCqk/5xztibE9l9qd+HtG7Q0BpRC8LrVOzmzJphKoLEzIcjR41kPN+xcw09tj/vIP/jbI3qSf7wxsgcZvkgRCOC0ZpMK+tWHXSOgOfz8DIYhQBLtZIw1DT+WMXZFOTXjqDWmf8r9T5J+fobQZcH82tzlafm4mbiYxbQld5gk5vKt4p/svQlFDYQdzEUvl7eBWrhhFJnzNye8Gg3tthE0bdc/c8HI8l4j8Iv/6naS+QsC50aMd4OjN0V4O5eQ9lhHYXYPFtLXU22tG7LO4pXA==
x-microsoft-antispam-prvs: <AM2PR07MB099336B339C9009A6FD040C8F0430@AM2PR07MB0993.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(2017020603029)(20170203043)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123555025)(20161123560025)(20161123558025)(20161123562025)(6072148); SRVR:AM2PR07MB0993; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0993; 
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(24454002)(199003)(189002)(13464003)(51914003)(51444003)(93886004)(2950100002)(230783001)(122556002)(6916009)(6246003)(2900100001)(229853002)(66066001)(3660700001)(53546003)(54906002)(92566002)(74316002)(68736007)(110136004)(38730400002)(6306002)(53936002)(54896002)(9686003)(5660300001)(86362001)(8676002)(8936002)(77096006)(4326007)(3280700002)(105586002)(76176999)(25786008)(106116001)(54356999)(7696004)(6506006)(236005)(790700001)(102836003)(2906002)(7906003)(3846002)(7736002)(55016002)(6116002)(189998001)(33656002)(966004)(106356001)(606005)(81166006)(101416001)(81156014)(97736004)(6436002)(99286003)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0993; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Feb 2017 09:36:51.5597 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0993
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfUhTURjGOffe3V2l0WlqvmlBrsI0tQ9LZ5oUSEga6F+uMG3mTefXZJuV UbIwy2bWiC2dmZoZptX8oI9lFjYsKSyzNGwoFq5AMTCdyPIr513gf7/3fR6e85zDYUhhJ8+L keWoWEWONEtEu1IGyTPvwFC9QbLD1LBObK0coMRVc0ZC3D82RYl/tVRT4vJX92lxX/9Fcj8d XVdnJ6Kf1JXR0bX6XyiOPOoakcpmyU6xiu2Rx13T1U2v6NyHZnTm49QDWo3KXyINcmEA74aa FgOpQa6MEBsRzHaN8LihC8G3XhtyDBQuJeFtY7VT0RFQardR3PAGge1aJa1BDEPjvWA1xzpy 3XEA6G4/X84lcREBVl0V5RDccAx0fG3lc6ZYsD/vITk+CPrC7uVSFN4M7QudhCNTgBPhsiae O+sqAXN/KnkOjwuOgr8N88t+hNfCzPuHhINJ7AkWazXBXQ5DXTuXD9gDRkcWeJw/BZqKTE6P D3xqrHDyYdB3VKH//Nt0k89xNwXFdsxxJgxbSiiOD8Gtge+EoxzgpwQM6PudQeuhvrnMKbyg YfRF83KSELNQ/6gIcS/hBUN9V5AW+VWsKM6xHIxDdykHC/AaeGewLjGztPeDprbtnMUHdCU/ +BxvhaLK2/yV+xrEb0QeSlaZkp22KziIVchOKJXynKAcVtWKlv7W68ezW0zoy/gBM8IMEq0S 5F4vlwh50lPK/GwzAoYUuQvOaw0SoSBVmn+WVciTFXlZrNKMvBlK5CkIaRhOEOI0qYrNZNlc VvFfJRgXLzWit2WGBoR8jpv2HZEXHpOoLQUxSRlVdy603ZBDseXDhsmw1aO9s/4TzzZZ8hYn Ijsyrs4sxl8KmJ8zT5/eGBlh8tXrA8fcf6q1lgfDPQlwLlU2aasJLn2f2J4ctsXl3p6TSfvc tM22imxJQUP9eMxgljz8+uCRcE2UUTVU6yOeEVHKdOlOf1KhlP4DFhUDpVcDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/rC77_dZlHctlOtYiyqUmTYE7S38>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 09:37:00 -0000

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGV0ZSwNCg0KV2XigJlyZSBnZXR0aW5nIHRoZXJlLg0KUGxlYXNlIHNlZSBpbiBsaW5lIGZv
ciBmdXJ0aGVyIGV4cGxhbmF0aW9uLg0KDQpUaGFua3MgYSBsb3QNCkRhbmllbGUNCg0KRnJvbTog
UGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbV0NClNlbnQ6IGx1
bmVkw6wgNiBmZWJicmFpbyAyMDE3IDE4OjM4DQpUbzogRGFuaWVsZSBDZWNjYXJlbGxpIDxkYW5p
ZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24uY29tPg0KQ2M6IEphcmkgQXJra28gPGphcmkuYXJra29A
cGl1aGEubmV0PjsgZ2VuLWFydEBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1n
cmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzsgY2NhbXBAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtZmxleGli
bGUtZ3JpZC1vc3BmLWV4dC0wNw0KDQoNCk9uIDYgRmViIDIwMTcsIGF0IDc6MzYsIERhbmllbGUg
Q2VjY2FyZWxsaSB3cm90ZToNCg0KSGkgSmFyaSwgUGV0ZSwNCg0KRmlyc3Qgb2YgYWxsIHRoYW5r
cyBmb3IgdGhlIGFjY3VyYXRlIHJldmlldy4NCg0KQWxsIHRoZSBuaXRzL2VkaXRvcmlhbCBjb21t
ZW50cyBhcmUgY29ycmVjdCBhbmQgd2lsbCBiZSBmaXhlZC4NCg0KUmVnYXJkaW5nIHRoZSBtaW5v
ciBpc3N1ZToNCg0KNC4xLjE6DQoNClRoZSBmaWd1cmUgaXMgYSBiaXQgY29uZnVzaW5nOiBUaGVy
ZSBtaWdodCBub3QgZXhpc3QgYSAiTWF4IFNsb3QgV2lkdGggYXQgUHJpb3JpdHkNCjciIGlmIGJp
dCA3IGlzIGNsZWFyIGluIHRoZSBQcmlvcml0eSBmaWVsZCwgY29ycmVjdD8NClBlcmhhcHMgaXQg
d291bGQgYmUgYmV0dGVyIHRvIGp1c3Qgc2hvdyB0aGF0IGFzICIuLi4iIG9yICJNYXggU2xvdCBX
aWR0aCBhdA0KUHJpb3JpdHkgbiIuIFRoZSB0aGluZyBpcywgaXQgbWlnaHQgb25seSBiZSBhIHNp
bmdsZSB2YWx1ZSwgZm9sbG93ZWQgYnkgdGhlDQpwYWRkaW5nLCBzbyBoYXZpbmcgdGhlIHNlY29u
ZCB2YWx1ZSBpbiB0aGVyZSBtaWdodCBiZSBtaXNsZWFkaW5nLiAoUGVyaGFwcw0Kc2ltaWxhciBj
b25zdHJ1Y3RzIGFyZSB1c2VkIGluIG90aGVyIE1QTFMgZG9jcyBhbmQgcGVvcGxlIHdpbGwgdW5k
ZXJzdGFuZC4gQnV0DQppdCB0b29rIG1lIGEgd2hpbGUgdG8gZmlndXJlIGl0IG91dC4pDQoNCml0
IHdhcyBkaWZmaWN1bHQgdG8gZXhwcmVzcyBpbiB0aGUgZmlndXJlIHRoZSBmYWN0IHRoYXQgb25s
eSBzb21lIG9mIHRoZSBwcmlvcml0aWVzIGFyZSBhZHZlcnRpc2VkLiBBcyB5b3Ugc2FpZCBpdCBj
b3VsZCBiZSBvbmUsIHR3byBvciBhbnkgbnVtYmVyIHVwIHRvIDguDQpXaGF0IGFib3V0IGEgc2lu
Z2xlIGZpZWxkICh3aXRoIH4gb24gdGhlIGJvcmRlcnMgdG8gaW5kaWNhdGUgdGhhdCBpdCBjYW4g
aGF2ZSB2YXJpYWJsZSBsZW5ndGgpIHNheWluZyAiTWF4IFNsb3QgV2lkdGggYXQgUHJpbyBuIiBh
bmQgdGhlbiBzYXkgdGhhdCAxNiBiaXRzIGFyZSB1c2VkIGZvciBlYWNoIHByaW8gYW5kIHdoZW4g
YW4gb2RkIG51bWJlciBvZiBwcmlvcml0aWVzIGlzIHVzZWQgdGhlIGZpZWxkIGlzIHBhZGRlZCB0
byBsaW5lIHVwIHdpdGggbXVsdGlwbGVzIG9mIDMyIGJpdHM/DQoNClllcywgSSB0aGluayB0aGF0
IHdvdWxkIG1ha2UgbW9yZSBzZW5zZSB0byBtZS4NCg0KW0RDXSBPSw0KDQpUaGUgZGlzY3Vzc2lv
biBvZiBQcmlvcml0eSB3YXMgdmVyeSBjb25mdXNpbmcgZm9yIG1lLiBJbiB0aGUgdGhpcmQgc2Vu
dGVuY2UsIGRvDQp5b3UgbWVhbiwgIkEgYml0IGlzIHNldCAoMSkgY29ycmVzcG9uZGluZyB0byBl
YWNoIHByaW9yaXR5IHJlcHJlc2VudGVkIGluIHRoZQ0Kc3ViLVRMViwgYW5kIGNsZWFyICgwKSBm
b3IgZWFjaCBwcmlvcml0eSBub3QgcmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYiPyBJIGRvbid0
DQp1bmRlcnN0YW5kIHRoZSBNVVNUL01VU1QgTk9UIGFzIHlvdSBoYWQgaXQuIEFuZCBJIGRvbid0
IHVuZGVyc3RhbmQgdGhlDQpsYXN0IHNlbnRlbmNlIGF0IGFsbC4gQXJlIHlvdSB0cnlpbmcgdG8g
c2F5LCAiVGhlIGxlZnRtb3N0IGJpdCAocHJpb3JpdHkgbGV2ZWwgMCkNCk1VU1QgYmUgc2V0LCBh
bmQgcHJpb3JpdHkgbGV2ZWwgMCBNVVNUIGJlIGFkdmVydGlzZWQgaW4gdGhlIHN1Yi1UTFYuIj8N
Ck90aGVyd2lzZSwgSSBkb24ndCBnZXQgaXQuDQoNCkl0IG1lYW5zIHRoYXQgaWYgdGhlIHByaW9y
aXR5IGZpZWxkIGlzIHNldCB0byBlLmcuIDEwMDEwMDEwIGluIHRoZSBmb2xsb3dpbmcgeW91IHdv
dWxkIGZpbmQgNCBmaWVsZHMgaW5kaWNhdGluZyByZXNwZWN0aXZlbHk6IE1heCBTbG90IFdpZHRo
IGF0IFByaW9yaXR5IDAsIE1heCBTbG90IFdpZHRoIGF0IFByaW9yaXR5IDMsIE1heCBTbG90IFdp
ZHRoIGF0IFByaW9yaXR5IDYgYW5kIHNpbmNlIHRoZXkgYXJlIDMgYSAxNiBiaXRzIHBhZGRpbmcg
dG8gMzIgYml0cy4NCg0KT0ssIHRoZW4gSSB0aGluayBteSBzZW50ZW5jZSBpcyBjbGVhcmVyIGZv
ciB0aGF0OiAiQSBiaXQgaXMgc2V0ICgxKSBjb3JyZXNwb25kaW5nIHRvIGVhY2ggcHJpb3JpdHkg
cmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYsIGFuZCBjbGVhciAoMCkgZm9yIGVhY2ggcHJpb3Jp
dHkgbm90IHJlcHJlc2VudGVkIGluIHRoZSBzdWItVExWLiINCg0KW0RDXSBBZ3JlZS4gV2XigJls
bCB1c2UgeW91ciB0ZXh0Lg0KDQpJdCBhbHNvIG1lYW5zIHRoYXQgYXQgbGVhc3Qgb25lIHByaW9y
aXR5IG11c3QgYmUgYWR2ZXJ0aXNlZCAoaS5lLiBwcmlvcml0eSAwMDAwMDAwMCBpcyBub3QgYWxs
b3dlZCkuDQoNCkkgZ2V0IHRoYXQgcGFydCAoIkF0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBN
VVNUIGJlIGFkdmVydGlzZWQiKS4gSXQncyB0aGUgZW5kIEkgZG9uJ3QgdW5kZXJzdGFuZDogInRo
YXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwgU0hBTEwgYmUgYXQgcHJpb3Jp
dHkgbGV2ZWwgMC4iIFdoYXQgZG9lcyB0aGF0IG1lYW4/DQoNCltEQ10gSXQgbWVhbnMgdGhhdCBp
ZiBvbmx5IG9uZSBwcmlvcml0eSBpcyBzdXBwb3J0ZWQgaXQgaGFzIHRvIGJlIHByaW9yaXR5IDAu
IEZvciBhbnkgcGFydGljdWxhciBhZG1pbmlzdHJhdGl2ZSBwdXJwb3NlIGl0IGNvdWxkIGJlIHBv
c3NpYmxlIHRvIHNldCBpdCB0byBhIGRpZmZlcmVudCB2YWx1ZSwgYnV0IHRoYXQgc2hvdWxkbuKA
mXQgYmUgZG9uZS4NCg0KSSBkb24ndCB1bmRlcnN0YW5kIHRoZSBNQVkgaW4gdGhlIGxhc3Qgc2Vu
dGVuY2UuIERvZXMgdGhhdCBtZWFuIHRoYXQgSSBNQVkNCmFsc28gc2V0IGl0IHRvIHRoZSBoaWdo
ZXN0IHBvc3NpYmxlIG5vbWluYWwgY2VudHJhbCBmcmVxdWVuY3kgc3VwcG9ydGVkIGJ5IHRoZQ0K
bGluaz8gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgdGhhdCBzZW50ZW5jZSBpcyB0cnlpbmcgdG8g
dGVsbCBtZS4NCg0KQW4gZXhhbXBsZSBpcyBwcm92aWRlZCBpbiBzZWN0aW9uIDQuMS4yLCB3aGVy
ZSB0aGUgYXZhaWxhYmxlIHJhbmdlIGdvZXMgZnJvbSAtMiB0byArOCBidXQgdGhlIHJhbmdlIHN1
cHBvcnRlZCBieSB0aGUgbGluayBnb2VzIGZyb20gLTkgdG8gKzExLiBUaGUgc2VudGVuY2UgbWVh
bnMgdGhhdCBldmVuIGlmIG5vdCBhdmFpbGFibGUgaXQgY291bGQgYmUgcG9zc2libGUgdG8gaW5k
aWNhdGUgYWxzbyBuPS05IHRvIGluZGljYXRlIHRoZSBzdGFydGluZyBwb2ludCBvZiB0aGUgcmFu
Z2Ugc3VwcG9ydGVkIGJ5IHRoZSBsaW5rLg0KDQoiIEluIHRoaXMgZXhhbXBsZSwgaXQgaXMgYXNz
dW1lZCB0aGF0IHRoZSBsb3dlc3Qgbm9taW5hbCBjZW50cmFsDQpmcmVxdWVuY3kgc3VwcG9ydGVk
IGlzIG49IC05IGFuZCB0aGUgaGlnaGVzdCBpcyBuPTExLiBOb3RlIHRoZXkNCmNhbm5vdCBiZSB1
c2VkIGFzIGEgbm9taW5hbCBjZW50cmFsIGZyZXF1ZW5jeSBmb3Igc2V0dGluZyB1cCBhIExTUCwN
CmJ1dCBtZXJlbHkgYXMgdGhlIHdheSB0byBleHByZXNzIHRoZSBzdXBwb3J0ZWQgZnJlcXVlbmN5
IHJhbmdlLiINCg0KSSdtIG9rIHdpdGggZHJvcHBpbmcgdGhlIHNlbnRlbmNlLg0KDQpJIHRoaW5r
IGRyb3BwaW5nIHRoZSBzZW50ZW5jZSB3b3VsZCBtYWtlIHRoZSBtb3N0IHNlbnNlLg0KDQpbRENd
IE9rIGZvciBtZQ0KDQpUaGFuayB5b3UNCkRhbmllbGUNCg0KVGhhbmtzIGZvciBjb25zaWRlcmlu
ZyBteSBzdWdnZXN0ZWQgY2hhbmdlcy4NCg0KcHINCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEphcmkgQXJra28gW21haWx0bzpqYXJpLmFya2tvQHBpdWhhLm5ldF0NClNlbnQ6
IGx1bmVkw6wgNiBmZWJicmFpbyAyMDE3IDEyOjMyDQpUbzogUGV0ZSBSZXNuaWNrIDxwcmVzbmlj
a0BxdGkucXVhbGNvbW0uY29tPG1haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPj4NCkNj
OiBnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0QGlldGYub3JnPjsgZHJhZnQtaWV0Zi1j
Y2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0
Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZz47DQpjY2FtcEBpZXRm
Lm9yZzxtYWlsdG86Y2NhbXBAaWV0Zi5vcmc+OyBpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGll
dGYub3JnPg0KU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft
cC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA3DQoNClRoYW5rcyBmb3IgeW91ciByZXZpZXcsIFBl
dGUuIEF1dGhvcnMsIGFueSBjb21tZW50cz8NCg0KSmFyaQ0KDQotLQ0KUGV0ZSBSZXNuaWNrIGh0
dHA6Ly93d3cucXVhbGNvbW0uY29tL35wcmVzbmljay88aHR0cDovL3d3dy5xdWFsY29tbS5jb20v
JTdFcHJlc25pY2svPg0KUXVhbGNvbW0gVGVjaG5vbG9naWVzLCBJbmMuIC0gKzEgKDg1OCk2NTEt
NDQ3OA0K

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IklUIiBsaW5rPSJibHVl
IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSBQZXRlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
Pldl4oCZcmUgZ2V0dGluZyB0aGVyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5QbGVhc2Ugc2VlIGluIGxpbmUgZm9yIGZ1cnRoZXIgZXhwbGFuYXRpb24uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+VGhhbmtzIGEgbG90PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+RGFuaWVsZSZuYnNwOyAmbmJzcDs8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj4gUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbV0NCjxi
cj4NCjxiPlNlbnQ6PC9iPiBsdW5lZMOsIDYgZmViYnJhaW8gMjAxNyAxODozODxicj4NCjxiPlRv
OjwvYj4gRGFuaWVsZSBDZWNjYXJlbGxpICZsdDtkYW5pZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24u
Y29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7amFyaS5hcmtrb0BwaXVoYS5u
ZXQmZ3Q7OyBnZW4tYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRmLWNjYW1w
LWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj5PbiA2IEZlYiAyMDE3LCBhdCA3OjM2LCBEYW5pZWxlIENlY2NhcmVsbGkgd3Jv
dGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4t
Ym90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5IaSBKYXJpLCBQZXRlLDxicj4NCjxicj4N
CkZpcnN0IG9mIGFsbCB0aGFua3MgZm9yIHRoZSBhY2N1cmF0ZSByZXZpZXcuPGJyPg0KPGJyPg0K
QWxsIHRoZSBuaXRzL2VkaXRvcmlhbCBjb21tZW50cyBhcmUgY29ycmVjdCBhbmQgd2lsbCBiZSBm
aXhlZC48YnI+DQo8YnI+DQpSZWdhcmRpbmcgdGhlIG1pbm9yIGlzc3VlOjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCAjOTk5OTk5IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNt
O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izk5OTk5OSI+
NC4xLjE6PGJyPg0KPGJyPg0KVGhlIGZpZ3VyZSBpcyBhIGJpdCBjb25mdXNpbmc6IFRoZXJlIG1p
Z2h0IG5vdCBleGlzdCBhICZxdW90O01heCBTbG90IFdpZHRoIGF0IFByaW9yaXR5PGJyPg0KNyZx
dW90OyBpZiBiaXQgNyBpcyBjbGVhciBpbiB0aGUgUHJpb3JpdHkgZmllbGQsIGNvcnJlY3Q/PGJy
Pg0KUGVyaGFwcyBpdCB3b3VsZCBiZSBiZXR0ZXIgdG8ganVzdCBzaG93IHRoYXQgYXMgJnF1b3Q7
Li4uJnF1b3Q7IG9yICZxdW90O01heCBTbG90IFdpZHRoIGF0PGJyPg0KUHJpb3JpdHkgbiZxdW90
Oy4gVGhlIHRoaW5nIGlzLCBpdCBtaWdodCBvbmx5IGJlIGEgc2luZ2xlIHZhbHVlLCBmb2xsb3dl
ZCBieSB0aGU8YnI+DQpwYWRkaW5nLCBzbyBoYXZpbmcgdGhlIHNlY29uZCB2YWx1ZSBpbiB0aGVy
ZSBtaWdodCBiZSBtaXNsZWFkaW5nLiAoUGVyaGFwczxicj4NCnNpbWlsYXIgY29uc3RydWN0cyBh
cmUgdXNlZCBpbiBvdGhlciBNUExTIGRvY3MgYW5kIHBlb3BsZSB3aWxsIHVuZGVyc3RhbmQuIEJ1
dDxicj4NCml0IHRvb2sgbWUgYSB3aGlsZSB0byBmaWd1cmUgaXQgb3V0Lik8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5pdCB3YXMgZGlmZmljdWx0
IHRvIGV4cHJlc3MgaW4gdGhlIGZpZ3VyZSB0aGUgZmFjdCB0aGF0IG9ubHkgc29tZSBvZiB0aGUg
cHJpb3JpdGllcyBhcmUgYWR2ZXJ0aXNlZC4gQXMgeW91IHNhaWQgaXQgY291bGQgYmUgb25lLCB0
d28gb3IgYW55IG51bWJlciB1cCB0byA4Ljxicj4NCldoYXQgYWJvdXQgYSBzaW5nbGUgZmllbGQg
KHdpdGggfiBvbiB0aGUgYm9yZGVycyB0byBpbmRpY2F0ZSB0aGF0IGl0IGNhbiBoYXZlIHZhcmlh
YmxlIGxlbmd0aCkgc2F5aW5nICZxdW90O01heCBTbG90IFdpZHRoIGF0IFByaW8gbiZxdW90OyBh
bmQgdGhlbiBzYXkgdGhhdCAxNiBiaXRzIGFyZSB1c2VkIGZvciBlYWNoIHByaW8gYW5kIHdoZW4g
YW4gb2RkIG51bWJlciBvZiBwcmlvcml0aWVzIGlzIHVzZWQgdGhlIGZpZWxkIGlzIHBhZGRlZCB0
byBsaW5lIHVwIHdpdGgNCiBtdWx0aXBsZXMgb2YgMzIgYml0cz88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+WWVzLCBJIHRoaW5rIHRoYXQgd291
bGQgbWFrZSBtb3JlIHNlbnNlIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+W0RDXSBPSzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1y
aWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41cHQ7cGFkZGluZzowY20gMGNtIDBj
bSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMu
NzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojOTk5OTk5Ij5UaGUgZGlzY3Vzc2lvbiBvZiBQcmlvcml0eSB3YXMgdmVy
eSBjb25mdXNpbmcgZm9yIG1lLiBJbiB0aGUgdGhpcmQgc2VudGVuY2UsIGRvPGJyPg0KeW91IG1l
YW4sICZxdW90O0EgYml0IGlzIHNldCAoMSkgY29ycmVzcG9uZGluZyB0byBlYWNoIHByaW9yaXR5
IHJlcHJlc2VudGVkIGluIHRoZTxicj4NCnN1Yi1UTFYsIGFuZCBjbGVhciAoMCkgZm9yIGVhY2gg
cHJpb3JpdHkgbm90IHJlcHJlc2VudGVkIGluIHRoZSBzdWItVExWJnF1b3Q7PyBJIGRvbid0PGJy
Pg0KdW5kZXJzdGFuZCB0aGUgTVVTVC9NVVNUIE5PVCBhcyB5b3UgaGFkIGl0LiBBbmQgSSBkb24n
dCB1bmRlcnN0YW5kIHRoZTxicj4NCmxhc3Qgc2VudGVuY2UgYXQgYWxsLiBBcmUgeW91IHRyeWlu
ZyB0byBzYXksICZxdW90O1RoZSBsZWZ0bW9zdCBiaXQgKHByaW9yaXR5IGxldmVsIDApPGJyPg0K
TVVTVCBiZSBzZXQsIGFuZCBwcmlvcml0eSBsZXZlbCAwIE1VU1QgYmUgYWR2ZXJ0aXNlZCBpbiB0
aGUgc3ViLVRMVi4mcXVvdDs/PGJyPg0KT3RoZXJ3aXNlLCBJIGRvbid0IGdldCBpdC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5JdCBtZWFucyB0
aGF0IGlmIHRoZSBwcmlvcml0eSBmaWVsZCBpcyBzZXQgdG8gZS5nLiAxMDAxMDAxMCBpbiB0aGUg
Zm9sbG93aW5nIHlvdSB3b3VsZCBmaW5kIDQgZmllbGRzIGluZGljYXRpbmcgcmVzcGVjdGl2ZWx5
OiBNYXggU2xvdCBXaWR0aCBhdCBQcmlvcml0eSAwLCBNYXggU2xvdCBXaWR0aCBhdCBQcmlvcml0
eSAzLCBNYXggU2xvdA0KIFdpZHRoIGF0IFByaW9yaXR5IDYgYW5kIHNpbmNlIHRoZXkgYXJlIDMg
YSAxNiBiaXRzIHBhZGRpbmcgdG8gMzIgYml0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+T0ssIHRoZW4gSSB0aGluayBteSBzZW50ZW5jZSBp
cyBjbGVhcmVyIGZvciB0aGF0OiAmcXVvdDtBIGJpdCBpcyBzZXQgKDEpIGNvcnJlc3BvbmRpbmcg
dG8gZWFjaCBwcmlvcml0eSByZXByZXNlbnRlZCBpbiB0aGUgc3ViLVRMViwgYW5kIGNsZWFyICgw
KSBmb3IgZWFjaCBwcmlvcml0eSBub3QgcmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYuJnF1b3Q7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
W0RDXSBBZ3JlZS4gV2XigJlsbCB1c2UgeW91ciB0ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxl
ZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+SXQgYWxzbyBtZWFucyB0aGF0IGF0IGxlYXN0IG9uZSBwcmlvcml0eSBtdXN0IGJlIGFk
dmVydGlzZWQgKGkuZS4gcHJpb3JpdHkgMDAwMDAwMDAgaXMgbm90IGFsbG93ZWQpLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIGdldCB0aGF0
IHBhcnQgKCZxdW90O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBNVVNUIGJlIGFkdmVydGlz
ZWQmcXVvdDspLiBJdCdzIHRoZSBlbmQgSSBkb24ndCB1bmRlcnN0YW5kOiAmcXVvdDt0aGF0LCB1
bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNIQUxMIGJlIGF0IHByaW9yaXR5IGxl
dmVsIDAuJnF1b3Q7IFdoYXQgZG9lcyB0aGF0IG1lYW4/PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+W0RDXSBJdCBtZWFucyB0aGF0IGlmIG9u
bHkgb25lIHByaW9yaXR5IGlzIHN1cHBvcnRlZCBpdCBoYXMgdG8gYmUgcHJpb3JpdHkgMC4gRm9y
IGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZlIHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2li
bGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZhbHVlLCBidXQNCiB0aGF0IHNob3VsZG7igJl0
IGJlIGRvbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTtt
YXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgIzk5OTk5OSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O21h
cmdpbi1sZWZ0OjBjbTttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206My43NXB0Ij4NCjxw
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiM5OTk5OTkiPkkgZG9uJ3QgdW5kZXJzdGFuZCB0aGUgTUFZIGluIHRoZSBsYXN0IHNlbnRl
bmNlLiBEb2VzIHRoYXQgbWVhbiB0aGF0IEkgTUFZPGJyPg0KYWxzbyBzZXQgaXQgdG8gdGhlIGhp
Z2hlc3QgcG9zc2libGUgbm9taW5hbCBjZW50cmFsIGZyZXF1ZW5jeSBzdXBwb3J0ZWQgYnkgdGhl
PGJyPg0KbGluaz8gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgdGhhdCBzZW50ZW5jZSBpcyB0cnlp
bmcgdG8gdGVsbCBtZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojNzc3Nzc3Ij5BbiBleGFtcGxlIGlzIHByb3ZpZGVkIGluIHNlY3Rpb24gNC4xLjIsIHdoZXJl
IHRoZSBhdmFpbGFibGUgcmFuZ2UgZ29lcyBmcm9tIC0yIHRvICYjNDM7OCBidXQgdGhlIHJhbmdl
IHN1cHBvcnRlZCBieSB0aGUgbGluayBnb2VzIGZyb20gLTkgdG8gJiM0MzsxMS4gVGhlIHNlbnRl
bmNlIG1lYW5zIHRoYXQgZXZlbiBpZiBub3QgYXZhaWxhYmxlIGl0IGNvdWxkDQogYmUgcG9zc2li
bGUgdG8gaW5kaWNhdGUgYWxzbyBuPS05IHRvIGluZGljYXRlIHRoZSBzdGFydGluZyBwb2ludCBv
ZiB0aGUgcmFuZ2Ugc3VwcG9ydGVkIGJ5IHRoZSBsaW5rLjxicj4NCjxicj4NCiZxdW90OyBJbiB0
aGlzIGV4YW1wbGUsIGl0IGlzIGFzc3VtZWQgdGhhdCB0aGUgbG93ZXN0IG5vbWluYWwgY2VudHJh
bDxicj4NCmZyZXF1ZW5jeSBzdXBwb3J0ZWQgaXMgbj0gLTkgYW5kIHRoZSBoaWdoZXN0IGlzIG49
MTEuIE5vdGUgdGhleTxicj4NCmNhbm5vdCBiZSB1c2VkIGFzIGEgbm9taW5hbCBjZW50cmFsIGZy
ZXF1ZW5jeSBmb3Igc2V0dGluZyB1cCBhIExTUCw8YnI+DQpidXQgbWVyZWx5IGFzIHRoZSB3YXkg
dG8gZXhwcmVzcyB0aGUgc3VwcG9ydGVkIGZyZXF1ZW5jeSByYW5nZS4mcXVvdDs8YnI+DQo8YnI+
DQpJJ20gb2sgd2l0aCBkcm9wcGluZyB0aGUgc2VudGVuY2UuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkgdGhpbmsgZHJvcHBpbmcgdGhlIHNl
bnRlbmNlIHdvdWxkIG1ha2UgdGhlIG1vc3Qgc2Vuc2UuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj5bRENdIE9rIGZvciBtZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxl
ZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+VGhhbmsgeW91PGJyPg0KRGFuaWVsZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxv
Y2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFua3MgZm9yIGNvbnNpZGVyaW5nIG15IHN1Z2dl
c3RlZCBjaGFuZ2VzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5wcjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFy
Z2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41
cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0
OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IEphcmkgQXJra28gWzxhIGhyZWY9Im1haWx0bzpqYXJp
LmFya2tvQHBpdWhhLm5ldCI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5OTk5OTkiPm1haWx0bzpqYXJp
LmFya2tvQHBpdWhhLm5ldDwvc3Bhbj48L2E+XTxicj4NClNlbnQ6IGx1bmVkw6wgNiBmZWJicmFp
byAyMDE3IDEyOjMyPGJyPg0KVG86IFBldGUgUmVzbmljayAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBy
ZXNuaWNrQHF0aS5xdWFsY29tbS5jb20iPnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb208L2E+Jmd0
Ozxicj4NCkNjOiA8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyI+Z2VuLWFydEBpZXRm
Lm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnIj4NCmRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1v
c3BmLWV4dC5hbGxAaWV0Zi5vcmc8L2E+Ozxicj4NCjxhIGhyZWY9Im1haWx0bzpjY2FtcEBpZXRm
Lm9yZyI+Y2NhbXBAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+
DQppZXRmQGlldGYub3JnPC9hPjxicj4NClN1YmplY3Q6IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9m
IGRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC0wNzxicj4NCjxicj4NClRo
YW5rcyBmb3IgeW91ciByZXZpZXcsIFBldGUuIEF1dGhvcnMsIGFueSBjb21tZW50cz88YnI+DQo8
YnI+DQpKYXJpPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPi0tIDxicj4NClBldGUgUmVzbmljayA8YSBocmVmPSJodHRw
Oi8vd3d3LnF1YWxjb21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0eWxlPSJjb2xvcjojMzk4
M0M0Ij5odHRwOi8vd3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9zcGFuPjwvYT48YnI+DQpR
dWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2NTEtNDQ3ODxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_--


From nobody Tue Feb  7 09:05:02 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24488129D78; Tue,  7 Feb 2017 09:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level: 
X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Klejm2yJ325S; Tue,  7 Feb 2017 09:04:59 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E683129444; Tue,  7 Feb 2017 09:04:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486487099; x=1518023099; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Vt5NGl4TxA7moqo/JKPQ2JXWcVIJ5FKzbBDjVw22ssk=; b=skMgGY9Pzt0H6f1zNqzuJOmWoaeFlUNf3uoomyWxyVtpTb7q9Loi+BDc NIrS7i2Fd4tvi4q6MHXAGh0fPsk9K6grUq0OvjxLU1O0YSh3rnlAWLYA+ KyaNBTVzR+4ZfqYVqgH2g6u0r1ta+L1Zy54C8A8c5pm0uY8XakHa2uqN3 Q=;
X-IronPort-AV: E=Sophos;i="5.33,346,1477983600";  d="scan'208,217";a="356310173"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine02.qualcomm.com with ESMTP; 07 Feb 2017 09:04:59 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8432"; a="1304809432"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Feb 2017 09:04:58 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 09:04:57 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Date: Tue, 7 Feb 2017 11:04:56 -0600
Message-ID: <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1Z3oYvTxoEgekyQn9TTut-xSrYA>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 17:05:01 -0000

--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Hi Daniele,

Thanks for addressing everything. There's only one issue left in section 
4.1.1 on Priority, below. I've trimmed out all the rest.

On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:

>> I get that part ("At least one priority level MUST be advertised"). 
>> It's the end I don't understand: "that, unless overridden by local 
>> policy, SHALL be at priority level 0." What does that mean?
>
> [DC] It means that if only one priority is supported it has to be 
> priority 0.

So, let me see if I have this right: It's OK to have 01100000 but not 
01000000 or 00100000? If so, why is that?

> For any particular administrative purpose it could be possible to set 
> it to a different value, but that shouldn’t be done.

Well, it doesn't say that shouldn't be done, but it probably doesn't 
need to say anything about local configurations.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Hi Daniele,</p>

<p dir=3D"auto">Thanks for addressing everything. There's only one issue =
left in section 4.1.1 on Priority, below. I've trimmed out all the rest.<=
/p>

<p dir=3D"auto">On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">I get that part ("At least one priority level MUST be adv=
ertised"). It's the end I don't understand: "that, unless overridden by l=
ocal policy, SHALL be at priority level 0." What does that mean?</p>
</blockquote>

<p dir=3D"auto">[DC] It means that if only one priority is supported it h=
as to be priority 0.</p>
</blockquote>

<p dir=3D"auto">So, let me see if I have this right: It's OK to have 0110=
0000 but not 01000000 or 00100000? If so, why is that?</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">For any particular administrative purpose it could be pos=
sible to set it to a different value, but that shouldn=E2=80=99t be done.=
</p>
</blockquote>

<p dir=3D"auto">Well, it doesn't say that shouldn't be done, but it proba=
bly doesn't need to say anything about local configurations.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=--


From nobody Tue Feb  7 10:13:31 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B390B129DCA; Tue,  7 Feb 2017 10:13:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
Date: Tue, 07 Feb 2017 10:13:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/d0-hu-Ceh9zwGN9uiuFFigePBk8>
Cc: draft-ietf-pals-mpls-tp-dual-homing-protection.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: [Gen-art] Review of draft-ietf-pals-mpls-tp-dual-homing-protection-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 18:13:21 -0000

Reviewer: Russ Housley
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-protection-05
Reviewer: Russ Housley
Review Date: 2017-02-07
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary: Ready

Major Concerns:  None

Minor Concerns:  None

Nits:

In the last sentence of the first paragraph of Section 1, the
document
says: "This mechanism is only applicable ..."  I believe that this is
a reference to the repair mechanism that is defined in
[I-D.ietf-pals-endpoint-fast-protection], not the mechanism that is
defined in this document.  Please replace "This mechanism" with a
clear reference.

Notes:

I see that draft-cheng-pwe3-mpls-tp-dual-homing-protection the
earlier
Internet-Draft file name for this document.  An IPR declaration was
issued against that earlier name.  The shepherd write-up indicates
that
"The WG were not concerned about the IPR disclosure." However, it is
unclear to me whether we should ask for the IPR declaration to be
issued
against the current Internet-Draft file name.


From nobody Tue Feb  7 11:45:36 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE13129E5E for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 11:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8K6eojREv63 for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 11:45:33 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9D14129E5B for <gen-art@ietf.org>; Tue,  7 Feb 2017 11:45:32 -0800 (PST)
X-AuditID: c6180641-0291898000000a06-6d-5899dd890bb0
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by  (Symantec Mail Security) with SMTP id 36.66.02566.68DD9985; Tue,  7 Feb 2017 15:45:29 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0319.002; Tue, 7 Feb 2017 14:45:28 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org" <draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirection-06
Thread-Index: AdKBeqZ/21QNKY8YTlG9PZCKJMeN0g==
Date: Tue, 7 Feb 2017 19:45:28 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E882975@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E882975eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXSPt27n3ZkRBgcuW1pM2buWzeLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGoZWiBR/VKhZPOMPSwLhEqYuRk0NCwETi d+8uti5GLg4hgfWMEs8mr2GFcJYxSvw6spoFpIpNwEJi++/nYAkRgUWMEssv/2HvYuTgEBbw kdi/0QCkRkQgWGL+9AlsELaexIF3m1hBbBYBFYnvHw4wg9i8Ar4Sy1fOAqthFBCT+H5qDROI zSwgLnHryXwmiIsEJJbsOc8MYYtKvHz8jxXCVpTY1z+dHaI+X+LixrtsEDMFJU7OfMIygVFw FpJRs5CUzUJSBhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxcpQWF+TkphsZbmIEBv0x CTbHHYx7ez0PMQpwMCrx8BqEz4gQYk0sK67MPcQowcGsJMI76+PMCCHelMTKqtSi/Pii0pzU 4kOM0hwsSuK810PuhwsJpCeWpGanphakFsFkmTg4pRoYpU/vTHAI/1OcHdl8y/PjotcTvuzd NmvOfq7la5onS/b9MWqf93bvyV31v273+zodXqqYvjbNUy2w56p7jo9BmjOfxMf7Wf+7ok1Z 99dJPnHr8qsKZHBhcPUQ8q/Nrd/t0JHJUOLDFqmj+zv6pvPJ5eKa5jI6zToWMXP4hSKZnyZp zXzRlaLEUpyRaKjFXFScCAAiX1p9dgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/g5ipDgkx-5xQCN0SeNlqzNdR9zc>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirection-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:45:34 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E882975eusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.
For more information, please see the FAQ at <http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq>.


Document: draft-ietf-nfsv4-rpcrdma-bidirection-06
Reviewer: Meral Shirazipour
Review Date: 2017-02-07
IETF LC End Date:   2017-02-07
IESG Telechat date: -


Summary:
This draft is ready to be published as Standards Track RFC but I have comme=
nts.

Major issues:
Minor issues:
Nits/editorial comments:
-General: please consider spelling out acronyms at first use and use the ac=
ronym consistently thereafter.
-[Page 6], "(ie. a "---->"(i.e., a"


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E882975eusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair.&nbsp; Please treat these comments jus=
t like any other last call comments.<o:p></o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-nfsv4-rpcrdma-bidirection-06<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-02-07<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp;&nbsp; 2017-02-07<o:p></o:p><=
/p>
<p class=3D"MsoNormal">IESG Telechat date: -<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-General: please consider spelling out acronyms at f=
irst use and use the acronym consistently thereafter.
<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6], &quot;(ie. a &quot;----&gt;&quot;(i.e., a=
&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E882975eusaamb107erics_--


From nobody Tue Feb  7 12:26:39 2017
Return-Path: <chuck.lever@oracle.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34FDF129501 for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 12:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.087
X-Spam-Level: 
X-Spam-Status: No, score=-6.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmNaHoBZBFN4 for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 12:26:36 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF6F5129548 for <gen-art@ietf.org>; Tue,  7 Feb 2017 12:26:36 -0800 (PST)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v17KQTDl025963 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2017 20:26:30 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.13.8/8.14.4) with ESMTP id v17KQStL014690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2017 20:26:29 GMT
Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id v17KQQ93019903; Tue, 7 Feb 2017 20:26:27 GMT
Received: from anon-dhcp-171.1015granger.net (/68.46.169.226) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 07 Feb 2017 12:26:26 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A4E882975@eusaamb107.ericsson.se>
Date: Tue, 7 Feb 2017 15:26:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB6C6DC9-7B0D-4813-9992-BA3C519DFB52@oracle.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4E882975@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/UOSs-Bd1cH00EUjwHbk6jRuKja0>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org" <draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirection-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:26:38 -0000

> On Feb 7, 2017, at 2:45 PM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for the IETF Chair.  Please treat these comments just like any =
other last call comments.
> For more information, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> =20
> Document: draft-ietf-nfsv4-rpcrdma-bidirection-06
> Reviewer: Meral Shirazipour
> Review Date: 2017-02-07
> IETF LC End Date:   2017-02-07
> IESG Telechat date: -
> =20
> =20
> Summary:
> This draft is ready to be published as Standards Track RFC but I have =
comments.
> =20
> Major issues:
> Minor issues:
> Nits/editorial comments:
> -General: please consider spelling out acronyms at first use and use =
the acronym consistently thereafter.

To address this comment (and Jouni's related LC comment)
I've introduced the following forward definitions:

- RPC =3D Remote Procedure Call

- RDMA =3D Remote Direct Memory Access

- RPC-over-RDMA - defined by citation

- NFS =3D Network File System

- XDR - removed all usage

- XID =3D RPC transaction ID, and capitalized consistently

- NULL probe - replaced with "RPC NULL procedure"

- ULP - replaced with "RPC Program"

- Chunks - defined before use, and added citation


Please let me know if there are other unfamiliar terms I've
missed, or if there is a particular inconsistent usage that
should be corrected.


> -[Page 6], "(ie. a "---->"(i.e., a"

Fixed.

--
Chuck Lever




From nobody Tue Feb  7 13:31:46 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5751293FB for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 13:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXawsP-JJNdh for <gen-art@ietfa.amsl.com>; Tue,  7 Feb 2017 13:31:42 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B621288B8 for <gen-art@ietf.org>; Tue,  7 Feb 2017 13:31:41 -0800 (PST)
X-AuditID: c618062d-d5fff700000009d8-02-589a4c6f769b
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id 5B.E7.02520.F6C4A985; Tue,  7 Feb 2017 23:38:43 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Tue, 7 Feb 2017 16:31:37 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Chuck Lever <chuck.lever@oracle.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirection-06
Thread-Index: AdKBeqZ/21QNKY8YTlG9PZCKJMeN0gAL7LSAAAg0KsA=
Date: Tue, 7 Feb 2017 21:31:36 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E883D15@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4E882975@eusaamb107.ericsson.se> <AB6C6DC9-7B0D-4813-9992-BA3C519DFB52@oracle.com>
In-Reply-To: <AB6C6DC9-7B0D-4813-9992-BA3C519DFB52@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyuXRPrG6xz6wIg2MvxCz+333OZDFl71o2 i6uvPrM4MHssWfKTyePj01ssHl8uf2YLYI7isklJzcksSy3St0vgymifsJK9YJpgxd3jXxgb GK/wdjFycEgImEg0N/h2MXJxCAmsZ5SY8XgWI4SzjFFi/78FLF2MnBxsAhYS238/ZwWxRQQ0 JHZP38EMUsQssIhRom31I3aQScICQRL/f8ZC1ARLzJ8+gQ3CtpI4+3gPM4jNIqAisfzMZrCZ vAK+EleXv2SDWNbIKHH561SwBk4BO4kpUyaCLWMUEJP4fmoNE4jNLCAucevJfDBbQkBAYsme 88wQtqjEy8f/WCFsJYlJS8+xQtTrSCzY/YkNwtaWWLbwNTPEYkGJkzOfsExgFJ2FZOwsJC2z kLTMQtKygJFlFSNHaXFBTm66kcEmRmCMHJNg093BeH+65yFGAQ5GJR7eDcdnRAixJpYVV+Ye YpTgYFYS4b2kPStCiDclsbIqtSg/vqg0J7X4EKM0B4uSOG/c6vvhQgLpiSWp2ampBalFMFkm Dk6pBsYZoas+TzUy+PP+8yr7i/+vyphlOCcuLp/+6sSTrlfrsjR/PpHs92Zn2G2p5fyhYYNw 1cknBQcFl0nXr7zwZd558XehaeXVf9TMZzVcjnGwmh8mf/KOPePDNx6Jz93LU/4syerbdPn0 MynHsofdknkcPxK7BYyF5qfdmZAcd/2pd//1Y39SA9cpsRRnJBpqMRcVJwIAgtEiiY0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aAuSITOc7RbEfd0MGGQ3yEkAn_M>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org" <draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirection-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:31:44 -0000

Hi,
  Thank you.

Best,
Meral

> -----Original Message-----
> From: Chuck Lever [mailto:chuck.lever@oracle.com]
> Sent: Tuesday, February 07, 2017 12:26 PM
> To: Meral Shirazipour <meral.shirazipour@ericsson.com>
> Cc: draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org; gen-art@ietf=
.org
> Subject: Re: Gen-ART Last Call review of draft-ietf-nfsv4-rpcrdma-bidirec=
tion-06
>=20
>=20
> > On Feb 7, 2017, at 2:45 PM, Meral Shirazipour
> <meral.shirazipour@ericsson.com> wrote:
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area Rev=
iew
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for=
 the
> IETF Chair.  Please treat these comments just like any other last call co=
mments.
> > For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >
> > Document: draft-ietf-nfsv4-rpcrdma-bidirection-06
> > Reviewer: Meral Shirazipour
> > Review Date: 2017-02-07
> > IETF LC End Date:   2017-02-07
> > IESG Telechat date: -
> >
> >
> > Summary:
> > This draft is ready to be published as Standards Track RFC but I have
> comments.
> >
> > Major issues:
> > Minor issues:
> > Nits/editorial comments:
> > -General: please consider spelling out acronyms at first use and use th=
e
> acronym consistently thereafter.
>=20
> To address this comment (and Jouni's related LC comment) I've introduced =
the
> following forward definitions:
>=20
> - RPC =3D Remote Procedure Call
>=20
> - RDMA =3D Remote Direct Memory Access
>=20
> - RPC-over-RDMA - defined by citation
>=20
> - NFS =3D Network File System
>=20
> - XDR - removed all usage
>=20
> - XID =3D RPC transaction ID, and capitalized consistently
>=20
> - NULL probe - replaced with "RPC NULL procedure"
>=20
> - ULP - replaced with "RPC Program"
>=20
> - Chunks - defined before use, and added citation
>=20
>=20
> Please let me know if there are other unfamiliar terms I've missed, or if=
 there is a
> particular inconsistent usage that should be corrected.
>=20
>=20
> > -[Page 6], "(ie. a "---->"(i.e., a"
>=20
> Fixed.
>=20
> --
> Chuck Lever
>=20
>=20


From nobody Wed Feb  8 02:15:23 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE88129504; Wed,  8 Feb 2017 02:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vd_R8HYAL0X8; Wed,  8 Feb 2017 02:15:14 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC5F128E18; Wed,  8 Feb 2017 02:15:13 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-d6-589aefb09e8c
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id 47.F6.22993.FAFEA985; Wed,  8 Feb 2017 11:15:12 +0100 (CET)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 8 Feb 2017 11:14:49 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8yxydEOt4q5+mxKh+fFjVpyuM0hQUh3gpUi6J6bm3cU=; b=gi+1nhOhcIOFNP5cYCUm9J1I990TdeohICzSJGt23SefU+hc/Z76eC/qE66/fQzhABCEfShAuIW+9HNXmvzlhVPacX3uxgeT26ABwQsfQfvu+jfgR1snglF52h3N6dMqxpC0dV/k8DHsY03lKim2WxSNdLAMGDLA5X6GDPVh5jA=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0996.eurprd07.prod.outlook.com (10.162.37.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Wed, 8 Feb 2017 10:14:48 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Wed, 8 Feb 2017 10:14:48 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2AgACGiQCAARhlUA==
Date: Wed, 8 Feb 2017 10:14:48 +0000
Message-ID: <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
In-Reply-To: <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 3afe353e-0e8b-4951-da89-08d4500b5066
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0996;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0996; 7:2knK6iJrRA0VQlNCD3a1s3NatztQ0S7zqKrPwr2rTUufrUm3AoXT0vn0Uv622bjjUc7stFxSs9/tAwmO1NWokRPkmr7vtIwDbF6eittiGbQBVqb1zj+n60H7aKBbZw2G7khFV4HSJu2cXbQDTRy74rVPTscSGgt7GziJbtmDx/gnB6XFmBPG1OXMKM3RQ5KHXNUJdab5qC772NKkxxzEjX3NbcOOSr9IbnXx34iyEzlQiem/uw8jUrr2E12TIRGuL5JE606m+QG1SCBx8oOo0BZxhFyQokJfhNvYh+25yU+TQfTDy3EgES3cm07RdQhvpKxnP+0rZUq1EMaKowxNaZXw5Yi+qvYac7pSj+9HKQZzavW+tMqYPKER92mjH9Bq8hKhnjZp4lELmQDpv+LxGWZdztdmYyjLI/jsxpb29FLyiBWCbzEQdehdzlJN7J4h6x7attOLGrKt9hQiGnohhYKG8I4epDLDNx0jhVqWcVkNPZpEIyMTJjC52W03IJsvE/BDwAG+k4CB4H2dbDbAHg==
x-microsoft-antispam-prvs: <AM2PR07MB09960DD2B3432E79DF078BB5F0420@AM2PR07MB0996.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(20170203043)(8121501046)(5005006)(2017020702029)(3002001)(10201501046)(6041248)(20161123560025)(20161123564025)(20161123555025)(20161123558025)(20161123562025)(6072148); SRVR:AM2PR07MB0996; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0996; 
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(189002)(199003)(24454002)(790700001)(6246003)(5660300001)(6116002)(3280700002)(102836003)(93886004)(110136004)(33656002)(7736002)(53546003)(966004)(86362001)(230783001)(3846002)(3660700001)(106356001)(106116001)(66066001)(4326007)(101416001)(7906003)(68736007)(122556002)(105586002)(2906002)(53936002)(54356999)(76176999)(25786008)(606005)(50986999)(6506006)(77096006)(8936002)(74316002)(2950100002)(81156014)(2900100001)(81166006)(8676002)(6916009)(6436002)(38730400002)(92566002)(99286003)(229853002)(9686003)(54906002)(6306002)(54896002)(236005)(97736004)(189998001)(55016002)(7696004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0996; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Feb 2017 10:14:48.8925 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0996
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA01Sa0hTYRjuO+dsO1qDr6X5qhE4orxrKjIkIsMfUtrlRyVR6cyTmjptxyzt j4iLVDQhTbe8jDlQl6kNLRXxMpUoFhpeWopYORd5S5BK0ySPZ4H/nvd5nu95vu/lo0lJv8CN TlZkMkqFPFUqdKTUMa/P+bX+0MQEmn+JZdYqCyWr2WwmZOPzq5TM9rKWklX2NAhlY+P55Clh pF6/TkS26yuEkbpyG7pAXnU8kcCkJmcxyoCTcY5Jmw1aUcaf+PuG8QEqF2njCpEDDTgE1hYH qELkSEtwM4JPrTYBP7xBUGIxi7iBwsUkrI7aEK88IaD8o5bizkvwEIK86qBCRNNCHAZWUxRH O2FfKKvuJDk/iVUEWMtqdvwH8FnomzCKeFMUrHcOkzy+DMapZcTlUPgIdM97c7QYXwNDSRPJ 96pJeGibEnCCA46AisqnOxjhg/D7XRPBYRK7wKS1luDfhkHfzecDdobvs1t2fzy0qDrsHg8Y MWgIrhdwNCyognk6GjZKhgiuF7CZgk3jrD0nBVa68wU8PgPPLJ/tplcEvFct2EMPwVhtH+KF aiHoLQ+F/LYYqH+hQvwm3GB6rACVIi/NrovzOB3KdDOUZmcD++Gt2rqN6W3eC1q6AniLB5QV fRHx2BNUVdWi3bwWiQzImWVYNi0xKNifUSbfZNl0hb+CyTSi7Y/V37bh14GeL4SbEKaRdJ+4 tUATIxHIs9jsNBMCmpQ6ib8ublPiBHl2DqNMj1XeTWVYE3KnKamLOLRx5ooEJ8ozmRSGyWCU /1WCdnDLRXWhNwKNvfU/z8+FrLGT6uk4r9HoAssgClPrHtXe8ywfPHax98OEZ7GuLrst/YGD CqeE3Tp92Ef1LcgjYY/Z4KtdCRf7xF76uzCwlWNwjegICM7LaRwqDG8XPy66058/o+k66t2/ 1LlMxexNbBP0eMwPuyqWyr3nSjXX9SPut1ulFJskP+5NKln5PyRjc65UAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jiTDS0zdpoIH7jurLfl6x9nS-do>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 10:15:16 -0000

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGV0ZSwNCg0KVGhpcyBpcyBhbiDigJxpbmhlcml0YW5jZeKAnSBmcm9tIEdNUExTLCB3aGVy
ZSBzdXBwb3J0aW5nIGEgc2luZ2xlIHByaW9yaXR5IGVxdWFscyBub3Qgc3VwcG9ydGluZyBwcmlv
cml0aWVzLiBJZiB5b3UgZG9u4oCZdCB3YW50IHRvIHN1cHBvcnQgcHJpb3JpdGllcyB5b3UgZG9u
4oCZdCB3YW50IHlvdXIgdHJhZmZpYyB0byBiZSBwcmVlbXB0ZWTigKZoZW5jZSBwcmlvcml0eSAw
Lg0KDQoNCj5XZWxsLCBpdCBkb2Vzbid0IHNheSB0aGF0IHNob3VsZG4ndCBiZSBkb25lLCBidXQg
aXQgcHJvYmFibHkgZG9lc24ndCBuZWVkIHRvIHNheSBhbnl0aGluZyBhYm91dCBsb2NhbCBjb25m
aWd1cmF0aW9ucy4NCkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBvbiB0aGF0
Lg0KDQpUaGFua3MNCkRhbmllbGUNCg0KRnJvbTogUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25p
Y2tAcXRpLnF1YWxjb21tLmNvbV0NClNlbnQ6IG1hcnRlZMOsIDcgZmViYnJhaW8gMjAxNyAxODow
NQ0KVG86IERhbmllbGUgQ2VjY2FyZWxsaSA8ZGFuaWVsZS5jZWNjYXJlbGxpQGVyaWNzc29uLmNv
bT4NCkNjOiBKYXJpIEFya2tvIDxqYXJpLmFya2tvQHBpdWhhLm5ldD47IGdlbi1hcnRAaWV0Zi5v
cmc7IGRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC5hbGxAaWV0Zi5vcmc7
IGNjYW1wQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0dlbi1hcnRdIFJl
dmlldyBvZiBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDcNCg0KDQpI
aSBEYW5pZWxlLA0KDQpUaGFua3MgZm9yIGFkZHJlc3NpbmcgZXZlcnl0aGluZy4gVGhlcmUncyBv
bmx5IG9uZSBpc3N1ZSBsZWZ0IGluIHNlY3Rpb24gNC4xLjEgb24gUHJpb3JpdHksIGJlbG93LiBJ
J3ZlIHRyaW1tZWQgb3V0IGFsbCB0aGUgcmVzdC4NCg0KT24gNyBGZWIgMjAxNywgYXQgMzozNiwg
RGFuaWVsZSBDZWNjYXJlbGxpIHdyb3RlOg0KDQpJIGdldCB0aGF0IHBhcnQgKCJBdCBsZWFzdCBv
bmUgcHJpb3JpdHkgbGV2ZWwgTVVTVCBiZSBhZHZlcnRpc2VkIikuIEl0J3MgdGhlIGVuZCBJIGRv
bid0IHVuZGVyc3RhbmQ6ICJ0aGF0LCB1bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ks
IFNIQUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuIiBXaGF0IGRvZXMgdGhhdCBtZWFuPw0KDQpb
RENdIEl0IG1lYW5zIHRoYXQgaWYgb25seSBvbmUgcHJpb3JpdHkgaXMgc3VwcG9ydGVkIGl0IGhh
cyB0byBiZSBwcmlvcml0eSAwLg0KDQpTbywgbGV0IG1lIHNlZSBpZiBJIGhhdmUgdGhpcyByaWdo
dDogSXQncyBPSyB0byBoYXZlIDAxMTAwMDAwIGJ1dCBub3QgMDEwMDAwMDAgb3IgMDAxMDAwMDA/
IElmIHNvLCB3aHkgaXMgdGhhdD8NCg0KRm9yIGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZl
IHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2libGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZh
bHVlLCBidXQgdGhhdCBzaG91bGRu4oCZdCBiZSBkb25lLg0KDQpXZWxsLCBpdCBkb2Vzbid0IHNh
eSB0aGF0IHNob3VsZG4ndCBiZSBkb25lLCBidXQgaXQgcHJvYmFibHkgZG9lc24ndCBuZWVkIHRv
IHNheSBhbnl0aGluZyBhYm91dCBsb2NhbCBjb25maWd1cmF0aW9ucy4NCg0KcHINCi0tDQpQZXRl
IFJlc25pY2sgaHR0cDovL3d3dy5xdWFsY29tbS5jb20vfnByZXNuaWNrLzxodHRwOi8vd3d3LnF1
YWxjb21tLmNvbS8lN0VwcmVzbmljay8+DQpRdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAr
MSAoODU4KTY1MS00NDc4DQo=

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IklUIiBsaW5rPSJibHVl
IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSBQZXRlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlRoaXMgaXMgYW4g4oCcaW5oZXJpdGFuY2XigJ0gZnJvbSBHTVBMUywgd2hlcmUgc3VwcG9ydGlu
ZyBhIHNpbmdsZSBwcmlvcml0eSBlcXVhbHMgbm90IHN1cHBvcnRpbmcgcHJpb3JpdGllcy4gSWYg
eW91IGRvbuKAmXQgd2FudCB0byBzdXBwb3J0DQogcHJpb3JpdGllcyB5b3UgZG9u4oCZdCB3YW50
IHlvdXIgdHJhZmZpYyB0byBiZSBwcmVlbXB0ZWTigKZoZW5jZSBwcmlvcml0eSAwLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+Jmd0O1dlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hv
dWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBwcm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRo
aW5nIGFib3V0IGxvY2FsIGNvbmZpZ3VyYXRpb25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBv
biB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlRoYW5rczxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRhbmllbGUmbmJzcDsNCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
IGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4w
cHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPiBQZXRlIFJlc25pY2sgW21haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tXQ0KPGJy
Pg0KPGI+U2VudDo8L2I+IG1hcnRlZMOsIDcgZmViYnJhaW8gMjAxNyAxODowNTxicj4NCjxiPlRv
OjwvYj4gRGFuaWVsZSBDZWNjYXJlbGxpICZsdDtkYW5pZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24u
Y29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7amFyaS5hcmtrb0BwaXVoYS5u
ZXQmZ3Q7OyBnZW4tYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRmLWNjYW1w
LWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj5IaSBEYW5pZWxlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFua3MgZm9y
IGFkZHJlc3NpbmcgZXZlcnl0aGluZy4gVGhlcmUncyBvbmx5IG9uZSBpc3N1ZSBsZWZ0IGluIHNl
Y3Rpb24gNC4xLjEgb24gUHJpb3JpdHksIGJlbG93LiBJJ3ZlIHRyaW1tZWQgb3V0IGFsbCB0aGUg
cmVzdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+T24gNyBGZWIgMjAxNywgYXQgMzozNiwgRGFu
aWVsZSBDZWNjYXJlbGxpIHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFy
Z2luLWJvdHRvbTozLjc1cHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJn
aW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojOTk5OTk5Ij5JIGdldCB0aGF0IHBhcnQgKCZxdW90O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBs
ZXZlbCBNVVNUIGJlIGFkdmVydGlzZWQmcXVvdDspLiBJdCdzIHRoZSBlbmQgSSBkb24ndCB1bmRl
cnN0YW5kOiAmcXVvdDt0aGF0LCB1bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNI
QUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuJnF1b3Q7IFdoYXQgZG9lcyB0aGF0IG1lYW4/PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+W0RDXSBJ
dCBtZWFucyB0aGF0IGlmIG9ubHkgb25lIHByaW9yaXR5IGlzIHN1cHBvcnRlZCBpdCBoYXMgdG8g
YmUgcHJpb3JpdHkgMC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+U28s
IGxldCBtZSBzZWUgaWYgSSBoYXZlIHRoaXMgcmlnaHQ6IEl0J3MgT0sgdG8gaGF2ZSAwMTEwMDAw
MCBidXQgbm90IDAxMDAwMDAwIG9yIDAwMTAwMDAwPyBJZiBzbywgd2h5IGlzIHRoYXQ/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4t
bGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
Nzc3Nzc3Ij5Gb3IgYW55IHBhcnRpY3VsYXIgYWRtaW5pc3RyYXRpdmUgcHVycG9zZSBpdCBjb3Vs
ZCBiZSBwb3NzaWJsZSB0byBzZXQgaXQgdG8gYSBkaWZmZXJlbnQgdmFsdWUsIGJ1dCB0aGF0IHNo
b3VsZG7igJl0IGJlIGRvbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PldlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBwcm9i
YWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFib3V0IGxvY2FsIGNvbmZpZ3VyYXRp
b25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5wcjxicj4NCi0tIDxicj4NClBldGUgUmVzbmlj
ayA8YSBocmVmPSJodHRwOi8vd3d3LnF1YWxjb21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0
eWxlPSJjb2xvcjojMzk4M0M0Ij5odHRwOi8vd3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9z
cGFuPjwvYT48YnI+DQpRdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2
NTEtNDQ3ODxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_--


From nobody Wed Feb  8 10:53:46 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B1D129D5A; Wed,  8 Feb 2017 10:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SnA9Qp83rIN; Wed,  8 Feb 2017 10:53:43 -0800 (PST)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C36912942F; Wed,  8 Feb 2017 10:53:40 -0800 (PST)
Received: by mail-wr0-x241.google.com with SMTP id 89so9580023wrr.1; Wed, 08 Feb 2017 10:53:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dSh5msw0htlLNOsZ/NeV73oOzEIZnCDE3zTnMjv/iQ8=; b=iI/ImBSHNj0YjSA7Cirb5WhKKkzGiqXhga3PfylThA4CRA4JphKtPYtVyuAqoVVVd4 u0kt1+h1c1Z8PHWF+cMVgm+MsEbeoM6N4IAFX9JPF6urM1T71sn/c2006omCXA80YLia PCSUI/WhXbDwY5hi/h0BQ2c9LLRrfNC76M3Y6j/8ATjfTV5EdPXzvsFkGSiphW1WyZZu YQPwY/hjYugiltGIOiN5nRcHlZKJ4hX1buV5MgOMoUt16x1dGPWJHXiNSOHZXJbDVxvM yySMyZAVNONSGT0aqy5IDH5OpfUkHW8EUh+9Wz6O0emF4D/vXIvdcpFPKHEflKiE76je Gwsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dSh5msw0htlLNOsZ/NeV73oOzEIZnCDE3zTnMjv/iQ8=; b=tTjV+Eyij9CKrf+tFyU0mpW0oSCiBnceDMfEBoXmcgMPHKftx+PRG8d5viTJgTwisr FaWx6VbxeLGhTuiGY+4uzJXadBTnKnsV7iZSaz8LVbqrzIuBDqf0w7KJpwR6eg9NCHBq moYEMQ0/r2MJh0JvFhpL/IO6uaovLCmt8PTjrmScjKoLgUuV1wginxFtjuXWFbxPEOqK bKLQ/1/1/5tnx03xswmyM6wZl44WvBRhRUbDN+iLCr8awfLLcTjiu8bl9hEqGQuqNv3R xmHgg3wkQuqtRtD3Qg9CzWYEVF0J9x2xPRGS9ZoBaE+f8t1UK/x11HmjH//Q6wnDCcWG BIvA==
X-Gm-Message-State: AIkVDXIHH8ojbzAQxZSk6NQVgMyZ6AXOFX4+K6DuCPZ3s8B1RT6QiAmWpirVLkW2d4htlQ==
X-Received: by 10.223.154.165 with SMTP id a34mr11930137wrc.193.1486580018862;  Wed, 08 Feb 2017 10:53:38 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id h3sm14502051wrb.31.2017.02.08.10.53.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 10:53:38 -0800 (PST)
To: Russ Housley <housley@vigilsec.com>, gen-art@ietf.org
References: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <baf6ae46-3d87-4930-9d9f-1e7febfb07e9@gmail.com>
Date: Wed, 8 Feb 2017 18:53:36 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Ve1sjTlCysAZ9Xt_P7yJ2ARu_d8>
Cc: draft-ietf-pals-mpls-tp-dual-homing-protection.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-pals-mpls-tp-dual-homing-protection-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 18:53:45 -0000

Hi Russ

Thank you for the review.

I would like to respond to one point:


> Notes:
>
> I see that draft-cheng-pwe3-mpls-tp-dual-homing-protection the
> earlier
> Internet-Draft file name for this document.  An IPR declaration was
> issued against that earlier name.  The shepherd write-up indicates
> that
> "The WG were not concerned about the IPR disclosure." However, it is
> unclear to me whether we should ask for the IPR declaration to be
> issued
> against the current Internet-Draft file name.
>

The authors all responded including of course the author from the 
company that
filed the IPR. All indicated that no additional IPR was known about.

The IPR disclosure shows up in datatracker.

We do not normally chase companies to update their IPR disclosures, as
documents progress, and indeed if we chase them to do this update we need
to chase them shortly for a further one as the draft becomes an RFC.

Since you pointed it out we have asked the author to ask his patent dept
to do the update, but I hope that this does not become an IETF policy
making it even harder to pass the IPR checks that we put in place in RTG.

Thanks

Stewart



From nobody Wed Feb  8 16:08:22 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F219129646; Wed,  8 Feb 2017 16:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gbShXwbGEuG0; Wed,  8 Feb 2017 16:08:19 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 327F812951A; Wed,  8 Feb 2017 16:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486598899; x=1518134899; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=vsOmJqEWO3Dkn6FYyIjWtwAwGu1JQVd5NmFCVSfsNII=; b=OlTz4wmSdYTw2dh6axqLoFi1amhqp47VapRBaCL3Fv9k+MtCbppr+FP6 aUz8sJhNuZK6DnAwZgenUDFdu066R8O80UN6d+/wN3tgmO3qtItmWxnrD R7/U7RGARIDPd0NF8UxSq2AtbHp9XGA2w4QmU8VygaUjqh2u70UmZumGE o=;
X-IronPort-AV: E=Sophos;i="5.35,348,1484035200";  d="scan'208,217";a="356687977"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by wolverine02.qualcomm.com with ESMTP; 08 Feb 2017 16:08:18 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8433"; a="1287154124"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Feb 2017 16:08:18 -0800
Received: from [10.64.105.176] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 8 Feb 2017 16:08:17 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Date: Wed, 8 Feb 2017 18:08:15 -0600
Message-ID: <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com> <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[990, 8654], "plain":[549, 1805], "uuid":"2C0D4566-962E-40A2-9EFA-EED3C8ED12CE"}]
X-Mailer: MailMate (1.9.6r5344)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oRTtPX1WvufKPPGP5nSCYE1qXZQ>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 00:08:21 -0000

--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

If that's what you mean, let me suggest simplifying:

OLD
                                                At least one priority
    level MUST be advertised that, unless overridden by local policy,
    SHALL be at priority level 0.
NEW
                                                At least one priority
    level MUST be advertised. If only one priority level is advertised,
    it MUST be at priority level 0.

Thanks for the extended discussion of this. It all looks fine.

pr

On 8 Feb 2017, at 4:14, Daniele Ceccarelli wrote:

> Hi Pete,
>
> This is an “inheritance” from GMPLS, where supporting a single 
> priority equals not supporting priorities. If you don’t want to 
> support priorities you don’t want your traffic to be 
> preempted…hence priority 0.
>
>
>> Well, it doesn't say that shouldn't be done, but it probably doesn't 
>> need to say anything about local configurations.
> For me it’s ok not to say anything on that.
>
> Thanks
> Daniele
>
> From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
> Sent: martedì 7 febbraio 2017 18:05
> To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
> Cc: Jari Arkko <jari.arkko@piuha.net>; gen-art@ietf.org; 
> draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org; ccamp@ietf.org; 
> ietf@ietf.org
> Subject: Re: [Gen-art] Review of 
> draft-ietf-ccamp-flexible-grid-ospf-ext-07
>
>
> Hi Daniele,
>
> Thanks for addressing everything. There's only one issue left in 
> section 4.1.1 on Priority, below. I've trimmed out all the rest.
>
> On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:
>
> I get that part ("At least one priority level MUST be advertised"). 
> It's the end I don't understand: "that, unless overridden by local 
> policy, SHALL be at priority level 0." What does that mean?
>
> [DC] It means that if only one priority is supported it has to be 
> priority 0.
>
> So, let me see if I have this right: It's OK to have 01100000 but not 
> 01000000 or 00100000? If so, why is that?
>
> For any particular administrative purpose it could be possible to set 
> it to a different value, but that shouldn’t be done.
>
> Well, it doesn't say that shouldn't be done, but it probably doesn't 
> need to say anything about local configurations.
>
> pr
> --
> Pete Resnick 
> http://www.qualcomm.com/~presnick/<http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478



--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><=
p dir=3D"auto">If that's what you mean, let me suggest simplifying:</p>
<p dir=3D"auto">OLD<br>
                                               At least one priority     =
 <br>
   level MUST be advertised that, unless overridden by local policy,     =
 <br>
   SHALL be at priority level 0. <br>
NEW<br>
                                               At least one priority     =
 <br>
   level MUST be advertised. If only one priority level is advertised,<br=
>
   it MUST be at priority level 0.</p>
<p dir=3D"auto">Thanks for the extended discussion of this. It all looks =
fine.</p>
<p dir=3D"auto">pr</p>
<p dir=3D"auto">On 8 Feb 2017, at 4:14, Daniele Ceccarelli wrote:</p>
</div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"2C0D4566-962E-40A2-9EFA-EED3C8ED12CE">
<div lang=3D"IT" link=3D"blue" vlink=3D"purple">
<div style=3D"page:WordSection1">
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Hi Pete,</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>This is an =E2=80=9Cinheritance=E2=80=9D from GMPLS=
, where supporting a single priority equals not supporting priorities. If=
 you don=E2=80=99t want to support
 priorities you don=E2=80=99t want your traffic to be preempted=E2=80=A6h=
ence priority 0.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span lang=3D"EN-US" style=3D'font-family:"Ari=
al",sans-serif'>&gt;Well, it doesn't say that shouldn't be done, but it p=
robably doesn't need to say anything about local configurations.</span></=
p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>For me it=E2=80=99s ok not to say anything on that.=
</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Thanks</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Daniele=C2=A0
</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0c=
m 4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0c=
m 0cm 0cm">
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><b><span lan=
g=3D"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>F=
rom:</span></b><span lang=3D"EN-US" style=3D'font-size:11.0pt;font-family=
:"Calibri",sans-serif'> Pete Resnick [mailto:presnick@qti.qualcomm.com]
<br>
<b>Sent:</b> marted=C3=AC 7 febbraio 2017 18:05<br>
<b>To:</b> Daniele Ceccarelli &lt;daniele.ceccarelli@ericsson.com&gt;<br>=

<b>Cc:</b> Jari Arkko &lt;jari.arkko@piuha.net&gt;; gen-art@ietf.org; dra=
ft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org; ccamp@ietf.org; ietf@i=
etf.org<br>
<b>Subject:</b> Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-os=
pf-ext-07</span></p>
</div>
</div>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'>=C2=A0</p>
<div>
<div>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Hi Daniele,</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Thanks for addressing everything. There's only one issue left in section=
 4.1.1 on Priority, below. I've trimmed out all the rest.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:</span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<blockquote style=3D"border:none;border-left:solid #999999 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#999999'>I get that part ("At least one priority level MUST be adve=
rtised"). It's the end I don't understand: "that, unless overridden by lo=
cal policy, SHALL be at priority level 0." What does that mean?</span></p=
>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#777777'>[DC] It means that if only one priority is supported it ha=
s to be priority 0.</span></p>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>So, let me see if I have this right: It's OK to have 01100000 but not 01=
000000 or 00100000? If so, why is that?</span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#777777'>For any particular administrative purpose it could be poss=
ible to set it to a different value, but that shouldn=E2=80=99t be done.<=
/span></p>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Well, it doesn't say that shouldn't be done, but it probably doesn't nee=
d to say anything about local configurations.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D":v=
isited{color:purple; mso-style-priority:99; text-decoration:underline} :l=
ink{color:blue; mso-style-priority:99; text-decoration:underline}"><span =
style=3D"color:#3983C4">http://www.qualcomm.com/~presnick/</span></a><br>=

Qualcomm Technologies, Inc. - +1 (858)651-4478</span></p>
</div>
</div>
</div>
</div>
</div></div></blockquote>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote></div>
</div>
</body>
</html>

--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=--


From nobody Wed Feb  8 22:40:39 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D3D1295B2; Wed,  8 Feb 2017 22:40:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148662243771.4350.16301638874361801946.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2017 22:40:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/7SiubGnXY--_wlkws67s7mUMpmQ>
Cc: draft-sgtatham-secsh-iutf8.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-sgtatham-secsh-iutf8-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 06:40:38 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-sgtatham-secsh-iutf8-??
Reviewer: Roni Even
Review Date: 2017-02-08
IETF LC End Date: 2017-02-27
IESG Telechat date: 2017-03-02

Summary: This draft is ready for publication as a standard track RFC.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Thu Feb  9 00:31:52 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D2812989D; Thu,  9 Feb 2017 00:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H_32o8dPqB_w; Thu,  9 Feb 2017 00:31:44 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5BAF1295FE; Thu,  9 Feb 2017 00:31:43 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-8c-589c28ed39f4
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id D9.3B.22993.DE82C985; Thu,  9 Feb 2017 09:31:42 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.81) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 9 Feb 2017 09:31:23 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Opzmum3vrTlDoMwN+f7/18te9S+O6jTfEreJn48V4qI=; b=Lx2iEP7y7jyLy+VS9kLNCJ04NPc12GfBaK3l3lK8TbL/wQOaBXCrFS29IvpThEVH1NYg/PvHdxS0A99DrynzXfxAImWgnPtAQaLaxJxvaR/bGmI76zII54GjhUGIVFT4BcXBwMq6Wu48u8de50JDNAkI1+Hv8yncx1NhBtPDuVU=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Thu, 9 Feb 2017 08:31:20 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Thu, 9 Feb 2017 08:31:20 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2AgACGiQCAARhlUIAA8DWAgACMNTA=
Date: Thu, 9 Feb 2017 08:31:20 +0000
Message-ID: <AM2PR07MB0994E21E54B10F7AC0416452F0450@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com> <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com> <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
In-Reply-To: <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 64df4e46-ed44-4eb4-2671-08d450c60665
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0994;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0994; 7:DNw9T7p5a3la330cgSesROo7dV2OVt4rPKmZGhsFy6LihfU6lv5Nc0cWuTJ7AxOJXRkWQ0WFnV0mNHqUyJHlno6KkLs/zolpxElDQwwhhIvtjDjzO4xfR6cy5wCPySCzw/gkIGnH+W7hf/AEp0yCQuvepCcqrGTJJOa60bVWdvqtBmLYjTtzow0Y4skp4BYm4142u7ZDWuZISsFCjRCom4TxBS2FE/iMzE3jsdAH0IzhLITU8hB/C1lm2YkwFkqPiQhgMkNny0ET2JNPgUKV1anf5oMLDrDf3bJZWkAC4rGgzCL3FMHo9L+Q7daB536laEDGEIZm3iWMrtZHWdN/IS/uL/iN0CNcv+53tyg3kiEIJl1BgAghGfc+NN+LIJIJf+3QzkowXhhZk6A/JkP+xJ/WCOKUhA2PCqIcHrryYU/zN8zusIB+zy+3JFXBXCtDycRGDH+Ym34GE+21e6qsbxMI/CA0yISUO3RGodbufOs3rNAKsiD1g6KxW+sPl/H+SI6hdJSGOa6XeepgSeWdgQ==
x-microsoft-antispam-prvs: <AM2PR07MB09941719747952AE384F01EDF0450@AM2PR07MB0994.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(20161123558025)(6072148); SRVR:AM2PR07MB0994; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0994; 
x-forefront-prvs: 02135EB356
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(51914003)(199003)(189002)(24454002)(101416001)(54356999)(74316002)(7696004)(3660700001)(81166006)(4326007)(7906003)(230783001)(7736002)(66066001)(93886004)(50986999)(105586002)(229853002)(54896002)(106356001)(81156014)(76176999)(55016002)(54906002)(33656002)(99286003)(5660300001)(236005)(8936002)(6306002)(9686003)(25786008)(122556002)(38730400002)(189998001)(102836003)(6436002)(77096006)(68736007)(6916009)(606005)(966004)(106116001)(6506006)(53936002)(8676002)(2950100002)(6116002)(6246003)(86362001)(92566002)(53546003)(97736004)(2900100001)(790700001)(110136004)(3280700002)(2906002)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0994; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Feb 2017 08:31:20.5246 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0994
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hTYRjHec852zlbTl6n5oNG5IjQSO1qM8rM+iCpVPRBi6hmHi95bUdN I2JoghqiqAWbtzJRvG0lajrMUtNIKsW8pWlWw/AWlaUsbznPBL/9n/f/e97n/7y8DCnVC+yZ 8Og4VhmtiJQJxZQ68Nk5lx9OBYF7tYNb5IaCIUpetKQl5P1Tc5R84mkxJe/rv0t6CXxKS42E T8n9CXSWuCg+GsxGhiewSjfPq+KwcW0yFZtdjBILU+sJFfqpQRlIxAA+CA+WiwQZSMxIsRaB oWdKyBevEeQMaAkTReFMEnoWQ3gjj4DFninEFx0Iet910RmIYYT4CBja/EwNNngP5BU2kSaG xF8R1L8y0ibDGvvCy4Famof8wNjUTfI6CGaHGkl+2k5Y1s2t55PgS5DTXWLOV0bB9+fzQtMw ET4F6k8eJgbhrbDQVb2elMR2MGwoJvjdMJQ28/cDtoXJbysCng8CXWqjmXGEnkqNWftDR1q1 cEM3vEinTXMBv6VANzIv4I0ImElpoHl9GvKHxgke0hDwfrDZ3L0NcheqzN3lQiibWVyPIcUs lNekIv4p7GG0Lx1lI2fNpuS8joH2/PZ1LcFW8EZtoDRrS5PYGXR6Nx5xhLx7X2heO0FqQSG9 +fwhoiuRLcdyXFTo/gOurDL8GsfFRLtGs3G1aO1HtdYtujSiqukTbQgzSGYheXI9P1AqUCRw SVFtCBhSZiNxXvtwUkmwIukWq4y5ooyPZLk25MBQMjuJe8XnACkOVcSxESwbyyo3XIIR2avQ ruQP/1qyxI+8LFdqxWrPLIfk82ma6TNjC0Wdv1SRZSEFTIuvuHSssn7wtv/JmrnHAXesnFrU 4xcO/XXTqOz0I8NBxsOaybqU7e6Z3uk7+umPrd6iWSdJZ7WXtV6/tFpRd3mVzS0hEi0Hjwe3 3jhmke1RFP/nd2VMy83e6jlWNSqjuDDFvt2kklP8B5E2LGdNAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/WvBRhWkSxZrRZxv7b1EgMker8qM>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 08:31:46 -0000

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

R29uZSEg4pi6DQoNClRoYW5rcyB0byB5b3UgZm9yIHRoZSBjYXJlZnVsIHJldmlldy4NCg0KQlIN
CkRhbmllbGUNCg0KRnJvbTogUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxj
b21tLmNvbV0NClNlbnQ6IGdpb3ZlZMOsIDkgZmViYnJhaW8gMjAxNyAwMTowOA0KVG86IERhbmll
bGUgQ2VjY2FyZWxsaSA8ZGFuaWVsZS5jZWNjYXJlbGxpQGVyaWNzc29uLmNvbT4NCkNjOiBkcmFm
dC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQuYWxsQGlldGYub3JnOyBnZW4tYXJ0
QGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtH
ZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0
LTA3DQoNCg0KSWYgdGhhdCdzIHdoYXQgeW91IG1lYW4sIGxldCBtZSBzdWdnZXN0IHNpbXBsaWZ5
aW5nOg0KDQpPTEQNCkF0IGxlYXN0IG9uZSBwcmlvcml0eQ0KbGV2ZWwgTVVTVCBiZSBhZHZlcnRp
c2VkIHRoYXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwNClNIQUxMIGJlIGF0
IHByaW9yaXR5IGxldmVsIDAuDQpORVcNCkF0IGxlYXN0IG9uZSBwcmlvcml0eQ0KbGV2ZWwgTVVT
VCBiZSBhZHZlcnRpc2VkLiBJZiBvbmx5IG9uZSBwcmlvcml0eSBsZXZlbCBpcyBhZHZlcnRpc2Vk
LA0KaXQgTVVTVCBiZSBhdCBwcmlvcml0eSBsZXZlbCAwLg0KDQpUaGFua3MgZm9yIHRoZSBleHRl
bmRlZCBkaXNjdXNzaW9uIG9mIHRoaXMuIEl0IGFsbCBsb29rcyBmaW5lLg0KDQpwcg0KDQpPbiA4
IEZlYiAyMDE3LCBhdCA0OjE0LCBEYW5pZWxlIENlY2NhcmVsbGkgd3JvdGU6DQoNCkhpIFBldGUs
DQoNCg0KDQpUaGlzIGlzIGFuIOKAnGluaGVyaXRhbmNl4oCdIGZyb20gR01QTFMsIHdoZXJlIHN1
cHBvcnRpbmcgYSBzaW5nbGUgcHJpb3JpdHkgZXF1YWxzIG5vdCBzdXBwb3J0aW5nIHByaW9yaXRp
ZXMuIElmIHlvdSBkb27igJl0IHdhbnQgdG8gc3VwcG9ydCBwcmlvcml0aWVzIHlvdSBkb27igJl0
IHdhbnQgeW91ciB0cmFmZmljIHRvIGJlIHByZWVtcHRlZOKApmhlbmNlIHByaW9yaXR5IDAuDQoN
Cg0KDQo+V2VsbCwgaXQgZG9lc24ndCBzYXkgdGhhdCBzaG91bGRuJ3QgYmUgZG9uZSwgYnV0IGl0
IHByb2JhYmx5IGRvZXNuJ3QgbmVlZCB0byBzYXkgYW55dGhpbmcgYWJvdXQgbG9jYWwgY29uZmln
dXJhdGlvbnMuDQoNCkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBvbiB0aGF0
Lg0KDQoNCg0KVGhhbmtzDQoNCkRhbmllbGUNCg0KDQoNCkZyb206IFBldGUgUmVzbmljayBbbWFp
bHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb21dDQpTZW50OiBtYXJ0ZWTDrCA3IGZlYmJyYWlv
IDIwMTcgMTg6MDUNClRvOiBEYW5pZWxlIENlY2NhcmVsbGkgPGRhbmllbGUuY2VjY2FyZWxsaUBl
cmljc3Nvbi5jb208bWFpbHRvOmRhbmllbGUuY2VjY2FyZWxsaUBlcmljc3Nvbi5jb20+Pg0KQ2M6
IEphcmkgQXJra28gPGphcmkuYXJra29AcGl1aGEubmV0PG1haWx0bzpqYXJpLmFya2tvQHBpdWhh
Lm5ldD4+OyBnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0QGlldGYub3JnPjsgZHJhZnQt
aWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJh
ZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZz47IGNjYW1w
QGlldGYub3JnPG1haWx0bzpjY2FtcEBpZXRmLm9yZz47IGlldGZAaWV0Zi5vcmc8bWFpbHRvOmll
dGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRm
LWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDcNCg0KDQoNCkhpIERhbmllbGUsDQoNClRo
YW5rcyBmb3IgYWRkcmVzc2luZyBldmVyeXRoaW5nLiBUaGVyZSdzIG9ubHkgb25lIGlzc3VlIGxl
ZnQgaW4gc2VjdGlvbiA0LjEuMSBvbiBQcmlvcml0eSwgYmVsb3cuIEkndmUgdHJpbW1lZCBvdXQg
YWxsIHRoZSByZXN0Lg0KDQpPbiA3IEZlYiAyMDE3LCBhdCAzOjM2LCBEYW5pZWxlIENlY2NhcmVs
bGkgd3JvdGU6DQoNCkkgZ2V0IHRoYXQgcGFydCAoIkF0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZl
bCBNVVNUIGJlIGFkdmVydGlzZWQiKS4gSXQncyB0aGUgZW5kIEkgZG9uJ3QgdW5kZXJzdGFuZDog
InRoYXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwgU0hBTEwgYmUgYXQgcHJp
b3JpdHkgbGV2ZWwgMC4iIFdoYXQgZG9lcyB0aGF0IG1lYW4/DQoNCltEQ10gSXQgbWVhbnMgdGhh
dCBpZiBvbmx5IG9uZSBwcmlvcml0eSBpcyBzdXBwb3J0ZWQgaXQgaGFzIHRvIGJlIHByaW9yaXR5
IDAuDQoNClNvLCBsZXQgbWUgc2VlIGlmIEkgaGF2ZSB0aGlzIHJpZ2h0OiBJdCdzIE9LIHRvIGhh
dmUgMDExMDAwMDAgYnV0IG5vdCAwMTAwMDAwMCBvciAwMDEwMDAwMD8gSWYgc28sIHdoeSBpcyB0
aGF0Pw0KDQpGb3IgYW55IHBhcnRpY3VsYXIgYWRtaW5pc3RyYXRpdmUgcHVycG9zZSBpdCBjb3Vs
ZCBiZSBwb3NzaWJsZSB0byBzZXQgaXQgdG8gYSBkaWZmZXJlbnQgdmFsdWUsIGJ1dCB0aGF0IHNo
b3VsZG7igJl0IGJlIGRvbmUuDQoNCldlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0
IGJlIGRvbmUsIGJ1dCBpdCBwcm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFi
b3V0IGxvY2FsIGNvbmZpZ3VyYXRpb25zLg0KDQpwcg0KLS0NClBldGUgUmVzbmljayBodHRwOi8v
d3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPGh0dHA6Ly93d3cucXVhbGNvbW0uY29tLyU3RXBy
ZXNuaWNrLz4NClF1YWxjb21tIFRlY2hub2xvZ2llcywgSW5jLiAtICsxICg4NTgpNjUxLTQ0NzgN
Cg==

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdp
bi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6
MGNtOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
c2VyaWY7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXtt
c28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFy
Z2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVm
dDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
IixzZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1y
ZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0
ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIu
MHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
SVQiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24x
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkdvbmUhDQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OldpbmdkaW5nczttc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+Sjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj5UaGFua3MgdG8geW91IGZvciB0aGUgY2FyZWZ1bCByZXZpZXcuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj5CUjxicj4NCkRhbmllbGUmbmJzcDsgJm5ic3A7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6
c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+IFBldGUgUmVzbmljayBbbWFpbHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb21d
DQo8YnI+DQo8Yj5TZW50OjwvYj4gZ2lvdmVkw6wgOSBmZWJicmFpbyAyMDE3IDAxOjA4PGJyPg0K
PGI+VG86PC9iPiBEYW5pZWxlIENlY2NhcmVsbGkgJmx0O2RhbmllbGUuY2U8L3NwYW4+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Y2NhcmVsbGlAZXJpY3Nzb24uY29tJmd0Ozxicj4NCjxi
PkNjOjwvYj4gZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRm
Lm9yZzsgZ2VuLWFydEBpZXRmLm9yZzsgY2NhbXBAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtHZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft
cC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA3PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+SWYgdGhhdCdzIHdoYXQgeW91IG1lYW4sIGxldCBtZSBzdWdnZXN0IHNpbXBs
aWZ5aW5nOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5PTEQ8YnI+DQpBdCBsZWFzdCBvbmUgcHJp
b3JpdHkgPGJyPg0KbGV2ZWwgTVVTVCBiZSBhZHZlcnRpc2VkIHRoYXQsIHVubGVzcyBvdmVycmlk
ZGVuIGJ5IGxvY2FsIHBvbGljeSwgPGJyPg0KU0hBTEwgYmUgYXQgcHJpb3JpdHkgbGV2ZWwgMC4g
PGJyPg0KTkVXPGJyPg0KQXQgbGVhc3Qgb25lIHByaW9yaXR5IDxicj4NCmxldmVsIE1VU1QgYmUg
YWR2ZXJ0aXNlZC4gSWYgb25seSBvbmUgcHJpb3JpdHkgbGV2ZWwgaXMgYWR2ZXJ0aXNlZCw8YnI+
DQppdCBNVVNUIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PlRoYW5rcyBmb3IgdGhlIGV4dGVuZGVkIGRpc2N1c3Npb24gb2YgdGhpcy4gSXQgYWxsIGxvb2tz
IGZpbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPnByPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
Pk9uIDggRmViIDIwMTcsIGF0IDQ6MTQsIERhbmllbGUgQ2VjY2FyZWxsaSB3cm90ZTo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7
bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0K
PGRpdiBpZD0iMkMwRDQ1NjYtOTYyRS00MEEyLTlFRkEtRUVEM0M4RUQxMkNFIj4NCjxkaXY+DQo8
cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPkhpIFBldGUsPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOzwvc3Bhbj48
c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5UaGlzIGlzIGFuIOKAnGluaGVyaXRhbmNl4oCdIGZyb20gR01QTFMsIHdoZXJl
IHN1cHBvcnRpbmcgYSBzaW5nbGUgcHJpb3JpdHkgZXF1YWxzIG5vdCBzdXBwb3J0aW5nIHByaW9y
aXRpZXMuIElmIHlvdSBkb27igJl0IHdhbnQgdG8gc3VwcG9ydCBwcmlvcml0aWVzDQogeW91IGRv
buKAmXQgd2FudCB5b3VyIHRyYWZmaWMgdG8gYmUgcHJlZW1wdGVk4oCmaGVuY2UgcHJpb3JpdHkg
MC48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3Nzttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3
Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+
Jmd0O1dlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBw
cm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFib3V0IGxvY2FsIGNvbmZpZ3Vy
YXRpb25zLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5Gb3IgbWUgaXTigJlzIG9rIG5vdCB0byBzYXkgYW55
dGhpbmcgb24gdGhhdC48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3Nzttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxl
PSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlRoYW5rczwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5EYW5pZWxlJm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3Nzttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj
bSAwY20gMGNtIj4NCjxwPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
Izc3Nzc3NyI+IFBldGUgUmVzbmljayBbPGEgaHJlZj0ibWFpbHRvOnByZXNuaWNrQHF0aS5xdWFs
Y29tbS5jb20iPm1haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPC9hPl0NCjxicj4NCjxi
PlNlbnQ6PC9iPiBtYXJ0ZWTDrCA3IGZlYmJyYWlvIDIwMTcgMTg6MDU8YnI+DQo8Yj5Ubzo8L2I+
IERhbmllbGUgQ2VjY2FyZWxsaSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRhbmllbGUuY2VjY2FyZWxs
aUBlcmljc3Nvbi5jb20iPmRhbmllbGUuY2VjY2FyZWxsaUBlcmljc3Nvbi5jb208L2E+Jmd0Ozxi
cj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmphcmkuYXJra29A
cGl1aGEubmV0Ij5qYXJpLmFya2tvQHBpdWhhLm5ldDwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRv
Omdlbi1hcnRAaWV0Zi5vcmciPmdlbi1hcnRAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86
ZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZyI+DQpk
cmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQuYWxsQGlldGYub3JnPC9hPjsg
PGEgaHJlZj0ibWFpbHRvOmNjYW1wQGlldGYub3JnIj4NCmNjYW1wQGlldGYub3JnPC9hPjsgPGEg
aHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3Vi
amVjdDo8L2I+IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtZmxleGli
bGUtZ3JpZC1vc3BmLWV4dC0wNzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cD48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM3Nzc3NzciPiZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+SGkgRGFuaWVsZSw8L3NwYW4+
PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiM3Nzc3NzciPlRoYW5rcyBmb3IgYWRkcmVzc2luZyBldmVyeXRoaW5nLiBUaGVyZSdzIG9ubHkg
b25lIGlzc3VlIGxlZnQgaW4gc2VjdGlvbiA0LjEuMSBvbiBQcmlvcml0eSwgYmVsb3cuIEkndmUg
dHJpbW1lZCBvdXQgYWxsIHRoZSByZXN0Ljwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3
NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+T24gNyBGZWIgMjAxNywg
YXQgMzozNiwgRGFuaWVsZSBDZWNjYXJlbGxpIHdyb3RlOjwvc3Bhbj48c3BhbiBzdHlsZT0iY29s
b3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzowY20gMGNt
IDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6
MGNtO21hcmdpbi1ib3R0b206My43NXB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjOTk5OTk5IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4w
cHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJn
aW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij5JIGdldCB0aGF0IHBhcnQgKCZxdW90
O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBNVVNUIGJlIGFkdmVydGlzZWQmcXVvdDspLiBJ
dCdzIHRoZSBlbmQgSSBkb24ndCB1bmRlcnN0YW5kOiAmcXVvdDt0aGF0LCB1bmxlc3Mgb3ZlcnJp
ZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNIQUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuJnF1b3Q7
IFdoYXQgZG9lcyB0aGF0IG1lYW4/PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5bRENd
IEl0IG1lYW5zIHRoYXQgaWYgb25seSBvbmUgcHJpb3JpdHkgaXMgc3VwcG9ydGVkIGl0IGhhcyB0
byBiZSBwcmlvcml0eSAwLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+U28sIGxldCBt
ZSBzZWUgaWYgSSBoYXZlIHRoaXMgcmlnaHQ6IEl0J3MgT0sgdG8gaGF2ZSAwMTEwMDAwMCBidXQg
bm90IDAxMDAwMDAwIG9yIDAwMTAwMDAwPyBJZiBzbywgd2h5IGlzIHRoYXQ/PC9zcGFuPjxzcGFu
IHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90
ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgIzc3Nzc3NyAxLjVwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjBjbTttYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+Rm9y
IGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZlIHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2li
bGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZhbHVlLCBidXQgdGhhdCBzaG91bGRu4oCZdCBi
ZSBkb25lLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+V2VsbCwgaXQgZG9lc24ndCBz
YXkgdGhhdCBzaG91bGRuJ3QgYmUgZG9uZSwgYnV0IGl0IHByb2JhYmx5IGRvZXNuJ3QgbmVlZCB0
byBzYXkgYW55dGhpbmcgYWJvdXQgbG9jYWwgY29uZmlndXJhdGlvbnMuPC9zcGFuPjxzcGFuIHN0
eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3
Ij5wcjxicj4NCi0tIDxicj4NClBldGUgUmVzbmljayA8YSBocmVmPSJodHRwOi8vd3d3LnF1YWxj
b21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0eWxlPSJjb2xvcjojMzk4M0M0Ij5odHRwOi8v
d3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9zcGFuPjwvYT48YnI+DQpRdWFsY29tbSBUZWNo
bm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2NTEtNDQ3ODwvc3Bhbj48c3BhbiBzdHlsZT0i
Y29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_--


From nobody Thu Feb  9 07:19:55 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4D6129AB7; Thu,  9 Feb 2017 07:19:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
Date: Thu, 09 Feb 2017 07:19:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tbmyh3on4TfH_QqhGmvzRE8tvIQ>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 15:19:54 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc1981bis-04
Reviewer: Stewart Bryant
Review Date: 9/Feb/2017
IETF LC End Date: 1/Mar/2017
IESG Telechat date: unknown

Summary: This draft is on the right track but has open issues,
described in the review.

This review together with the lengthy discussion on the IETF list
suggest that this draft has a number of issues that need to be
addressed  before publication.

I wonder if we would best serve both our future and our heritage
if we declared RFC1981 as historic, and either left the idea there,
or declared it as historic and wrote a new text from a clean start?
 

Major issues:

Nits points out a number of faults with the document, but the only
one of substance is:

The text has a lot of RFC2119 language, but no RFC2119 declaration.

The document could use a thorough RFC2119 scrub

The document lists the three original authors one with an affiliation

change, but no email addresses. Has this been agreed with the
original
authors, and have arrangements been put in place for the RFC editor 
to process auth48?

It is concerning that the draft does not talk in any detail about
how modern ECMP works, i.e. using the five tuple, and noting that
the PMTU may be different depending on the transport layer port
numbers.

Given that a very large fraction of packets will traverse an MPLS
network at some point, I am surprised that there is no text talking
about the importance of providing support for this feature in the 
MPLS domain. RFC3988 talks to this point, but is only experimental.

======

   If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
   could use the flow id as the local representation of a path. 
Packets
   sent to a particular destination but belonging to different flows
may
   use different paths, with the choice of path depending on the flow
   id.  This approach will result in the use of optimally sized
packets
   on a per-flow basis, providing finer granularity than PMTU values
   maintained on a per-destination basis.

SB> How widely is flow-id supported in networks? I thought that the 
SB> current position was that it was unreliable as an ECMP indicator
SB> and thus routers tended to glean information from the packet
themselves.

======

      Note: if the original packet contained a Routing header, the
      Routing header should be used to determine the location of the
      destination address within the original packet.  If Segments
Left
      is equal to zero, the destination address is in the Destination
      Address field in the IPv6 header.  If Segments Left is greater
      than zero, the destination address is the last address
      (Address[n]) in the Routing header.

SB> So this has the effect that a traffic engineered packet and
SB> a non-traffic engineered packet will have the lower of the 
SB> two PMTUs. This was all harmless when source routing was a
curiosity
SB> as far as mainstream networking was concerned, but may be
SB> more of a problem as a result of the SPRING work.

=======


5.3.  Purging stale PMTU information

   Internetwork topology is dynamic; routes change over time.  While
the
   local representation of a path may remain constant, the actual
   path(s) in use may change.  Thus, PMTU information cached by a
node
   can become stale.

   If the stale PMTU value is too large, this will be discovered
almost
   immediately once a large enough packet is sent on the path.  No
such
   mechanism exists for realizing that a stale PMTU value is too
small,
   so an implementation should "age" cached values.  When a PMTU
value
   has not been decreased for a while (on the order of 10 minutes),
the
   PMTU estimate should be set to the MTU of the first-hop link, and
the
   packetization layers should be notified of the change.  This will
   cause the complete Path MTU Discovery process to take place again.

SB> Should that be an RFC2119 SHOULD?
SB> The impact of this advice is going to be a disruption to what
might
SB> be a critical service every 10 mins.
SB> Should there be some advice along the lines of noting the 
SB> importance of service delivery as part of deciding whether to
SB> test for bigger PMTU vs improving efficiency?

=======


Minor issues:

   IPv6 defines a standard mechanism for a node to discover the
   PMTU of an arbitrary path.

SB> Do you mean "This document defines ....."? Otherwise this needs
SB> a reference.

=======

   An extension to Path MTU Discovery defined in this document can be
   found in [RFC4821].  It defines a method for Packetization Layer
Path
SB> Rather than have the reader figure out what "It" is, perhaps
SB> s/It/RFC4821/
=======


   Upon receipt of such a
   message, the source node reduces its assumed PMTU for the path
based
   on the MTU of the constricting hop as reported in the Packet Too
Big
   message.

SB> We should perhaps state up front that this procedure
SB> hunts for the worst case of the ECMP set associated with the 
SB> ingress nodes PMTU classifier.
=======

   If a node receives a Packet Too Big message reporting a next-hop
MTU
   that is less than the IPv6 minimum link MTU, it should discard it.

SB> Should that be an RFC2119 SHOULD?
=======

5.2.  Storing PMTU information

   Ideally, a PMTU value should be associated with a specific path
   traversed by packets exchanged between the source and destination
   nodes.  However, in most cases a node will not have enough
   information to completely and accurately identify such a path.
   Rather, a node must associate a PMTU value with some local
   representation of a path.  It is left to the implementation to
select
   the local representation of a path.

SB> Is it worth noting the five tuple since that is how a lot of
SB> load balancers work?
=======

   The set of paths in use to a
   particular destination is expected to be small, in many cases
   consisting of a single path.  

SB> I am not sure that remains true in modern networks.
=======

   One approach to implementing PMTU aging is to associate a
timestamp
   field with a PMTU value.  This field is initialized to a
"reserved"
   value, indicating that the PMTU is equal to the MTU of the first
hop
   link.  Whenever the PMTU is decreased in response to a Packet Too
Big
   message, the timestamp is set to the current time.

   Once a minute, a timer-driven procedure runs through all cached
PMTU
   values, and for each PMTU whose timestamp is not "reserved" and is
   older than the timeout interval:

   -  The PMTU estimate is set to the MTU of the first hop link.

   -  The timestamp is set to the "reserved" value.

   -  Packetization layers using this path are notified of the
increase.


SB> Such detailed implementation advice is uncommon in modern RFCs. It
has
SB> the disadvantage of de-facto standardizing something that should
be left to
SB> the innovation of the implementer.

=======

5.4.  TCP layer actions

SB> TCP implementations have moved on a lot since this section was
SB> written. Is this still current best practise?

=======

5.5.  Issues for other transport protocols

   Some transport protocols (such as ISO TP4 [ISOTP]) are not allowed
to
   repacketize when doing a retransmission.  

SB> How much TP4 is there going over IPv6? Doesn't this example 
SB> show the IETF as not being in the modern age?

=======

Nits/editorial comments: 

   upper layer         a protocol layer immediately above IPv6.
                       Examples are transport protocols such as TCP
and
                       UDP, control protocols such as ICMP, routing
                       protocols such as OSPF, and internet or lower-
                       layer protocols being "tunneled" over (i.e.,
                       encapsulated in) IPv6 such as IPX, AppleTalk,
or
                       IPv6 itself.

SB> Everything in the list above is in the well known list, except
SB> IPX, so technically it needs expansion. However it might be nice
SB> to use some modern example in common use.
=======

   link                a communication facility or medium over which
                       nodes can communicate at the link layer, i.e.,
                       the layer immediately below IPv6.  Examples
are
                       Ethernets (simple or bridged); PPP links;
X.25,
                       Frame Relay, or ATM networks; and internet (or
                       higher) layer "tunnels", such as tunnels over
                       IPv4 or IPv6 itself.

SB> Technically X.25 needs a reference, since it is not "well known"
=======

   path                the set of links traversed by a packet between
a
                       source node and a destination node.

SB> Is it a set of links, or a set of links and nodes?

========
 
    the value of MMS_S, the "maximum send transport-message size". 
SB> The modern convention is full-name(abbreviation)

========

   The Sun Network File System (NFS) uses a Remote Procedure Call
(RPC)
   protocol [RPC] that, when used over UDP, in many cases will
generate
   payloads that must be fragmented even for the first-hop link. 
This
   might improve performance in certain cases, but it is known to
cause
   reliability and performance problems, especially when the client
and
   server are separated by routers.

SB> Perhaps this should point to RFC7530 (the current NFS Spec),
assuming
SB> the behaviour description is still correct.

=========

   The former can be accomplished by associating a flag with the
path;
   when a packet is sent on a path with this flag set, the IP layer
does
   not send packets larger than the IPv6 minimum link MTU.

SB> We do not normally give this level of implementation advice

========================




From nobody Thu Feb  9 17:25:07 2017
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A05129514; Thu,  9 Feb 2017 17:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ka40HaEx2wZZ; Thu,  9 Feb 2017 17:25:00 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 572BC128AB0; Thu,  9 Feb 2017 17:24:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGD76232; Fri, 10 Feb 2017 01:24:56 +0000 (GMT)
Received: from SZXEMA412-HUB.china.huawei.com (10.82.72.71) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 10 Feb 2017 01:24:55 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.215]) by SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0235.001; Fri, 10 Feb 2017 09:24:48 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-ccamp-flexible-grid-ospf-ext-08.txt
Thread-Index: AdKDPEeY65yU2az6QZ6JJZOzxSoUZQ==
Date: Fri, 10 Feb 2017 01:24:48 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43988E212@SZXEMA504-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.57.78.114]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.589D1668.0084, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.7.215, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 85ed7eaa1c452aa22b1cbdb854638ffe
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/y9GwWiUqfdMZN2tGvClBfx6MGCM>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: [Gen-art] Fw: New Version Notification for draft-ietf-ccamp-flexible-grid-ospf-ext-08.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 01:25:02 -0000

RGVhciBBbGwsIA0KDQpQbGVhc2UgZmluZCB0aGUgZm9sbG93aW5nIGFzIGFuIHVwZGF0ZSBvZiB0
aGUgZmxleGktZ3JpZCBvc3BmIGV4dGVuc2lvbiBkcmFmdC4gQ29tbWVudHMgZnJvbSByZXZpZXdl
cnMgaGFzIGJlZW4gYWRkcmVzc2VkIGluIHRoaXMgdmVyc2lvbi4gDQoNClRoYW5rIHlvdSBhbGwg
Zm9yIHRoZSBlZmZvcnQuIA0KDQpCZXN0IHdpc2hlcywNCkhhb21pYW4gKG9uIGJlaGFsZiBvZiBh
bGwgdGhlIGF1dGhvcnMgJiBjb250cmlidXRvcnMpDQoNCi0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0N
CuWPkeS7tuS6ujogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnXSANCuWPkemAgeaXtumXtDogMjAxN+W5tDLmnIgxMOaXpSA5OjIyDQrmlLbk
u7bkuro6IERhbmllbGUgQ2VjY2FyZWxsaTsgY2NhbXAtY2hhaXJzQGlldGYub3JnOyBPc2NhciBH
b256YWxleiBkZSBEaW9zOyBPc2NhciBkZSBEaW9zOyBaaGFuZ3hpYW4gKFhpYW4pOyBSYW1vbiBD
YXNlbGxhczsgWmhlbmdoYW9taWFuOyBaaGVuZ2hhb21pYW4NCuS4u+mimDogTmV3IFZlcnNpb24g
Tm90aWZpY2F0aW9uIGZvciBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQt
MDgudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWlldGYtY2NhbXAtZmxleGli
bGUtZ3JpZC1vc3BmLWV4dC0wOC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQg
YnkgSGFvbWlhbiBaaGVuZyBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCk5h
bWU6CQlkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQNClJldmlzaW9uOgkw
OA0KVGl0bGU6CQlHTVBMUyBPU1BGLVRFIEV4dGVuc2lvbnMgaW4gc3VwcG9ydCBvZiBGbGV4aS1n
cmlkIERXRE0gbmV0d29ya3MNCkRvY3VtZW50IGRhdGU6CTIwMTctMDItMDgNCkdyb3VwOgkJY2Nh
bXANClBhZ2VzOgkJMTgNClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRl
cm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA4LnR4
dA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC8NCkh0bWxpemVkOiAgICAgICBodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9z
cGYtZXh0LTA4DQpEaWZmOiAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91
cmwyPWRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC0wOA0KDQpBYnN0cmFj
dDoNCiAgIFRoZSBJbnRlcm5hdGlvbmFsIFRlbGVjb21tdW5pY2F0aW9uIFVuaW9uIFRlbGVjb21t
dW5pY2F0aW9uDQogICBTdGFuZGFyZGl6YXRpb24gU2VjdG9yIChJVFUtVCkgaGFzIGV4dGVuZGVk
IGl0cyBSZWNvbW1lbmRhdGlvbnMNCiAgIEcuNjk0LjEgYW5kIEcuODcyIHRvIGluY2x1ZGUgYSBu
ZXcgRGVuc2UgV2F2ZWxlbmd0aCBEaXZpc2lvbg0KICAgTXVsdGlwbGV4aW5nIChEV0RNKSBncmlk
IGJ5IGRlZmluaW5nIGEgc2V0IG9mIG5vbWluYWwgY2VudHJhbA0KICAgZnJlcXVlbmNpZXMsIGNo
YW5uZWwgc3BhY2luZ3MsIGFuZCB0aGUgY29uY2VwdCBvZiB0aGUgImZyZXF1ZW5jeQ0KICAgc2xv
dCIuIENvcnJlc3BvbmRpbmcgdGVjaG5pcXVlcyBmb3IgZGF0YS1wbGFuZSBjb25uZWN0aW9ucyBh
cmUga25vd24NCiAgIGFzIGZsZXhpLWdyaWQuDQoNCiAgIEJhc2VkIG9uIHRoZSBjaGFyYWN0ZXJp
c3RpY3Mgb2YgZmxleGktZ3JpZCBkZWZpbmVkIGluIEcuNjk0LjEsIFJGQw0KICAgNzY5OCBhbmQg
NzY5OSwgdGhpcyBkb2N1bWVudCBkZXNjcmliZXMgdGhlIE9TUEYtVEUgZXh0ZW5zaW9ucyBpbg0K
ICAgc3VwcG9ydCBvZiBHTVBMUyBjb250cm9sIG9mIG5ldHdvcmtzIHRoYXQgaW5jbHVkZSBkZXZp
Y2VzIHRoYXQgdXNlDQogICB0aGUgbmV3IGZsZXhpYmxlIG9wdGljYWwgZ3JpZC4NCg0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBj
b3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0
bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4N
Cg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K


From nobody Thu Feb  9 19:25:43 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2BC129551; Thu,  9 Feb 2017 19:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALuGlDn1513o; Thu,  9 Feb 2017 19:25:41 -0800 (PST)
Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74B04129562; Thu,  9 Feb 2017 19:25:41 -0800 (PST)
Received: by mail-pg0-x244.google.com with SMTP id 204so1932190pge.2; Thu, 09 Feb 2017 19:25:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=89bACYfdmEgrzwwGqzFQd3SxqiJopAme6V1HW2kHR44=; b=mVjv3EyVupQlq20a1Xd9fSLGEhmLmsibWdm1DMZgUEYh5Fefypuwbhp47tbQTIEgFp nqGp0wOgQpmExKymVKnOb+GgNBg3evy1caSzuoIYwPlnVDfLAJmb8/MqZUTVYc03uyUP UGMpm33AqxLHowgLXN0nTaf2JjVvC9oNKKFPqKJjtD6xSoZLhZzxTmOqd9ZHwp6Kvddx Hd7bS5Zl1irpz4101HC1m49T1lCx5fXoagVG3iIgrJuWv4SG0RCo0iJJsqDRLV0ajK78 D41wg1RDuFE9AKPO1jbXcJFsWJLedPLjXunf0sAXrkZFBq9KSdvTIYqMSB40QmN1fONd C0sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=89bACYfdmEgrzwwGqzFQd3SxqiJopAme6V1HW2kHR44=; b=tJhbVzVujApFtelBW3PJjWq4lx8o/wue5gZrHkd/Sr/Ie/AwbttO8M08zl/N8tpCNY 1KzFaohLxB0pHGkPgscja4J7nTD41bEwQTu4FWnm+kS43AyyLLDANaaioLp1fuWogz5z Us4YmuL7rJu1HFIUyT1GEUL1RpL9gmfWCMFductkP+6ZAAFH4Atyoms4kAd/O0lEn1t6 hMkLdv7rWj6Rk4favHAO1u0kEKTFjKTZqQyYrjzujrmzYWPtP5dy9yoz+LdR5qP4KGXk GqlgvpYszNPmCewDYjSlVVS7l1LvXutj0w26+hS93/6hWlJRnxDqefP644x0xeMRjO8t EX6A==
X-Gm-Message-State: AMke39nOPOoODV+f+nFt4zGWesN0NjB7AkFZr/xJH4uRWgUKlG9SOWfrDzqw3ykOAN1xZg==
X-Received: by 10.98.19.145 with SMTP id 17mr7590435pft.26.1486697140821; Thu, 09 Feb 2017 19:25:40 -0800 (PST)
Received: from ?IPv6:2406:e007:7ac3:1:28cc:dc4c:9703:6781? ([2406:e007:7ac3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k184sm521569pgc.23.2017.02.09.19.25.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 19:25:40 -0800 (PST)
To: Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
Date: Fri, 10 Feb 2017 16:25:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Td_uph7pLZpfa2prWx2abvcy4GI>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 03:25:42 -0000

Stewart,

On 10/02/2017 04:19, Stewart Bryant wrote:
...
> I wonder if we would best serve both our future and our heritage
> if we declared RFC1981 as historic, and either left the idea there,
> or declared it as historic and wrote a new text from a clean start?

I don't see that. It's a stable, widely deployed, interoperable
mechanism. That is rather orthogonal to the issue that has been raised,
which is that faulty ICMPv6 filtering blocks it on many, many paths
across the Internet.

...
> It is concerning that the draft does not talk in any detail about
> how modern ECMP works, i.e. using the five tuple, and noting that
> the PMTU may be different depending on the transport layer port
> numbers.

Has this problem been analysed for, say, IPv4? And does the real world
contain ECMP setups with different MTUs on different paths?

> Given that a very large fraction of packets will traverse an MPLS
> network at some point, I am surprised that there is no text talking
> about the importance of providing support for this feature in the 
> MPLS domain. RFC3988 talks to this point, but is only experimental.

I don't understand. How does the fact that there might be some MPLS
segments along the path affect end-to-end PMTUD?

> 
> ======
> 
>    If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>    could use the flow id as the local representation of a path. Packets
>    sent to a particular destination but belonging to different flows may
>    use different paths, with the choice of path depending on the flow
>    id.  This approach will result in the use of optimally sized packets
>    on a per-flow basis, providing finer granularity than PMTU values
>    maintained on a per-destination basis.
> 
> SB> How widely is flow-id supported in networks? I thought that the 
> SB> current position was that it was unreliable as an ECMP indicator
> SB> and thus routers tended to glean information from the packet themselves.

This is future-proofing. Agreed, usage today is limited.

(But it would be better to call it the Flow Label for consistency with other
recent RFCs.)

I think your other comments are all valuable.

Regards
    Brian


From nobody Fri Feb 10 02:20:43 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB87129487; Fri, 10 Feb 2017 02:20:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaH7n7hUjY3r; Fri, 10 Feb 2017 02:20:41 -0800 (PST)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA3E6128E18; Fri, 10 Feb 2017 02:20:40 -0800 (PST)
Received: by mail-wm0-x241.google.com with SMTP id u63so6667232wmu.2; Fri, 10 Feb 2017 02:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dBektC9JHSm51JDgOcNkfp/fJv0IMVc5kIf7BSf0igA=; b=K2i3aNiBcyPWxLBpT2wMcFXcJ82i5AeU0a/hjguTWeI+mTasyOJg8I0hzVXgLAmjec gMvlO+H8Fj32dmi8eXGeCzHaox9W355L1AC2ujrcxKNDGreqTVNuyCYQyXqbzPvHBPnu kboriHMn2rJWhb/vKSncm0jSsYoomgHkti7Z9gfyq11IMF1S/RK9gS2MULZSymplcwKf bmCvTtQaBO0YJeMF9Wqdcx/h6hxQXELKasUSJF1fLgsqkd776B6JlU6cM4fepAB42O1e lj8HOBEiuIOgsBxqrBDlNkpdW9Magn4UsGisXwPhrUEZGw2T+7UzRXc0jBarqtSbqPlS 1q1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dBektC9JHSm51JDgOcNkfp/fJv0IMVc5kIf7BSf0igA=; b=nlaRx13bQZEoIkd0GgNjNQqpOlndtS1BaZKG5OxXyN7+UHvag8jMdsNPQto/vPfTN6 mDnj26Y6SRW/T2wgStfP870m58KhLLyz+nmManioBTCZ06UcL/tjgqJLkdDJD+ZzQQkG 8IXStWz3hMhXkJkHH90IMrqaQ/h9gonO52pG1lRaZsNmezhjxlWkWtvoNg5vI1uV/IMX 4qtJ01fmZXo8KZzvCjj1Ep9nN69MBs/T6sBycNd+qkRu+aHDsy4hgg7zl/Mms1GDFwJ5 cToy9jbEe2SqspHsbsPeM1crIPrEDBJowz7v2/pt2fAq8v8pzvSaSD0Mk+3NzfIzBU93 kq4w==
X-Gm-Message-State: AMke39nCU+NcCxK6IIzKoUx1mEKa7Tdalz1mjRuCMdqS5VnS5oC6mEtYb2jL8hsActNZag==
X-Received: by 10.28.224.213 with SMTP id x204mr6399819wmg.82.1486722038995; Fri, 10 Feb 2017 02:20:38 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id n13sm1976907wrn.40.2017.02.10.02.20.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 02:20:38 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Date: Fri, 10 Feb 2017 10:20:35 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/lbsUfIwxjcntX9VUuTTMDizDHVQ>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 10:20:42 -0000

On 10/02/2017 03:25, Brian E Carpenter wrote:
> Stewart,
>
> On 10/02/2017 04:19, Stewart Bryant wrote:
> ...
>> I wonder if we would best serve both our future and our heritage
>> if we declared RFC1981 as historic, and either left the idea there,
>> or declared it as historic and wrote a new text from a clean start?
> I don't see that. It's a stable, widely deployed, interoperable
> mechanism. That is rather orthogonal to the issue that has been raised,
> which is that faulty ICMPv6 filtering blocks it on many, many paths
> across the Internet.

I will not debate whether it is faulty or not, but it seems that in 
practice the
Internet breaks the mechanism. However it breaks it is a way that seems
disruptive to some user traffic. The document is really guidance
one how hosts might use  ICMP for optimization, and arguable need
not be a standard at all.

My remark about heritage is that this vintage draft is very much a 
product of
its time, and really needs modernizing, and after modernizing ought to
look quite different, and thus maybe we should employ a procedure
other than a simple replacement.


> ...
>> It is concerning that the draft does not talk in any detail about
>> how modern ECMP works, i.e. using the five tuple, and noting that
>> the PMTU may be different depending on the transport layer port
>> numbers.
> Has this problem been analysed for, say, IPv4? And does the real world
> contain ECMP setups with different MTUs on different paths?

I don't know if anyone has looked. Since the mechanism is 
self-correcting albeit
with some disruption to user traffic it looks to the application and the 
application
user, just like the Internet not working for a few moments.

In a well managed SP network there should not be, but neither should there
be asymmetric path costs, but there are. The less well manage private
networks are less well managed.


>
>> Given that a very large fraction of packets will traverse an MPLS
>> network at some point, I am surprised that there is no text talking
>> about the importance of providing support for this feature in the
>> MPLS domain. RFC3988 talks to this point, but is only experimental.
> I don't understand. How does the fact that there might be some MPLS
> segments along the path affect end-to-end PMTUD?

The point that RFC3988 makes is that MPLS looks like a single hop to IP 
and the
PE has to fragment or has to reply with an ICMP error message to support
PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to 
result
in the right response at the end node.

My point is that the draft is silent on the subject, and perhaps it 
should not be.

However your question make me ask a further question. The draft is also 
silent
on NATs. Is there any advice needed for people designing and configuring 
NATs?

>
>> ======
>>
>>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>     could use the flow id as the local representation of a path. Packets
>>     sent to a particular destination but belonging to different flows may
>>     use different paths, with the choice of path depending on the flow
>>     id.  This approach will result in the use of optimally sized packets
>>     on a per-flow basis, providing finer granularity than PMTU values
>>     maintained on a per-destination basis.
>>
>> SB> How widely is flow-id supported in networks? I thought that the
>> SB> current position was that it was unreliable as an ECMP indicator
>> SB> and thus routers tended to glean information from the packet themselves.
> This is future-proofing. Agreed, usage today is limited.
>
> (But it would be better to call it the Flow Label for consistency with other
> recent RFCs.)

Well the question is whether it is simply limited today, or broken today 
in a manner that
is irrecoverable? I don't know, but I do know that the mainstream ECMP 
approach
is the five-tuple. There is something akin to the flow label being 
deployed in MPLS. However
what distinguishes the MPLS Entropy Label is that it is inserted (and 
removed) by the
service provider and is therefore trusted by the service provider.

>
> I think your other comments are all valuable.
Thank you.

Stewart


From nobody Fri Feb 10 06:17:36 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2382B129614; Fri, 10 Feb 2017 06:17:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11cTzIcZstsh; Fri, 10 Feb 2017 06:17:27 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32BF212998D; Fri, 10 Feb 2017 06:17:18 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-dc-589d8518899b
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id 0C.3B.02566.8158D985; Fri, 10 Feb 2017 10:17:14 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 09:17:14 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Charlie Perkins <charles.perkins@earthlink.net>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSe/j/cjYYsQbutUCsVh56ND0V9aFVgPUAgAAQ6gCADSuDgA==
Date: Fri, 10 Feb 2017 14:17:13 +0000
Message-ID: <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
In-Reply-To: <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F92523113235A438CA26F0B60E987E7@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsUyuXRPuK5U69wIgwd7jSzu37nGZnH/UY3F /9lb2C2uvvrMYvFs43wWi4N/trFZvDxR5sDuMXn/V2aPKb83snqs+jKB2WPJkp9MASxRXDYp qTmZZalF+nYJXBn3Xk5jK3hxkrHi/IITjA2MF44wdjFycEgImEg8PVvZxcjFISSwnlHi7J49 7BDOckaJhnkdQEWcHGxARRt2fmYCSYgIbGKUuPrlJxuIwywwnVFixc8pbCBVwgIWEjOnXwbr EBGwlJg44yIzhO0kcex6LyuIzSKgKnH++T6wel4Be4meWVuYIdatZpQ40LMa7CZOAUeJ1tX6 IDWMAmIS30+tYQKxmQXEJW49mQ9mSwgISCzZc54ZwhaVePn4H9h8UQE9iY0XprFDxJUk5ry+ xgwykllAU2L9Ln2IMdYSN+4cghqpKDGl+yE7xDmCEidnPmGZwCg+C8m2WQjds5B0z0LSPQtJ 9wJG1lWMHKXFBTm56UaGmxiBsXlMgs1xB+PeXs9DjAIcjEo8vBu850QIsSaWFVfmHmKU4GBW EuGdcGhuhBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHe6yH3w4UE0hNLUrNTUwtSi2CyTBycUg2M 0Y8uhrRu/LdaKGlVfdTcIOYLZguOSW59m+RnsH2hqFfqZMW4BRMi+l0a3+S+d5cUs1Lsa82/ zyHVLjpj/mP2K0krYtf7T5z3i1tJrPRtQNi8Z2KK7UVHZzFx3foo0r1+s35XugdHwyOBuJem a9Tk5JqXvN5/aHfAPPdwDePdGg87Dx86ZbpViaU4I9FQi7moOBEA0ffDPckCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/5AsBSfLx38TulrGPKxNMwyQgcXE>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 14:17:30 -0000

SGkgQ2hhcmxpZSwNCiAgSSBoYXZlIG5vdCB5ZXQgc2VlbiBhIHJlc3BvbnNlIHRvIHRoaXMgcmV2
aWV3LiBEbyB5b3UgdGhpbmsgeW91IHdpbGwgYmUgYWJsZSB0byBnZXQgdG8gdGhpcyBpbiB0aGUg
bmV4dCBkYXkgb3IgdHdvPyBUaGUgZG9jdW1lbnQgaXMgb24gdGhlIEZlYnJ1YXJ5IDE2IDIwMTcg
dGVsZWNoYXQgYW5kIEkgd291bGQgbGlrZSB0byBzZWUgcmVzb2x1dGlvbiB0byB0aGVzZSBpc3N1
ZXMgaW4gdGltZSBmb3IgdGhlIG90aGVyIEFEcyB0byBiYWxsb3QuDQoNClRoYW5rcw0KU3VyZXNo
DQoNCk9uIDIvMi8xNywgMToxMCBBTSwgIkNoYXJsaWUgUGVya2lucyIgPGNoYXJsZXMucGVya2lu
c0BlYXJ0aGxpbmsubmV0PiB3cm90ZToNCg0KICAgIEhlbGxvIFNyaSwNCiAgICANCiAgICBUaGUg
cmV2aWV3IHdhcyBpbmRlZWQgc3VwZXIuICBJJ2xsIHJlc3BvbmQgc29tZXRpbWUgaW4gdGhlIG5l
eHQgZmV3IGRheXMuDQogICAgDQogICAgUmVnYXJkcywNCiAgICBDaGFybGllIFAuDQogICAgDQog
ICAgDQogICAgT24gMi8xLzIwMTcgOTowOSBQTSwgU3JpIEd1bmRhdmVsbGkgKHNndW5kYXZlKSB3
cm90ZToNCiAgICA+IFRoYW5rIHlvdSBEYWxlIGZvciBhIGdyZWF0IHJldmlldy4NCiAgICA+DQog
ICAgPg0KICAgID4gQ2hhcmxpZS9BdXRob3JzIC0gQ2FuIHlvdSBwbGVhc2UgcmVzcG9uZCB0byBE
YWxlIGFuZCBhZGRyZXNzIHRoZXNlDQogICAgPiBjb21tZW50cy4NCiAgICA+DQogICAgPg0KICAg
ID4gUmVnYXJkcw0KICAgID4gU3JpDQogICAgPg0KICAgID4NCiAgICA+IE9uIDEvMzEvMTcsIDEx
OjM0IEFNLCAiZG1tIG9uIGJlaGFsZiBvZiBEYWxlIFdvcmxleSIgPGRtbS1ib3VuY2VzQGlldGYu
b3JnDQogICAgPiBvbiBiZWhhbGYgb2Ygd29ybGV5QGFyaWFkbmUuY29tPiB3cm90ZToNCiAgICA+
DQogICAgPj4gUmV2aWV3ZXI6IERhbGUgV29ybGV5DQogICAgPj4gUmV2aWV3IHJlc3VsdDogUmVh
ZHkgd2l0aCBJc3N1ZXMNCiAgICA+Pg0KICAgID4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuICBUaGUgR2VuZXJhbCBBcmVhDQogICAgPj4gUmV2aWV3
IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3Nl
ZA0KICAgID4+IGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0
aGVzZSBjb21tZW50cyBqdXN0DQogICAgPj4gbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1l
bnRzLg0KICAgID4+DQogICAgPj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhl
IEZBUSBhdA0KICAgID4+IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFj
L3dpa2kvR2VuQXJ0ZmFxPi4NCiAgICA+Pg0KICAgID4+IERvY3VtZW50OiAgZHJhZnQtaWV0Zi1k
bW0tNDI4M21uaWRzLTA0DQogICAgPj4gUmV2aWV3ZXI6ICBEYWxlIFIuIFdvcmxleQ0KICAgID4+
IFJldmlldyBEYXRlOiAgMzEgSmFuIDIwMTcNCiAgICA+PiBJRVRGIExDIEVuZCBEYXRlOiAgMiBG
ZWIgMjAxNw0KICAgID4+IElFU0cgVGVsZWNoYXQgZGF0ZTogIDE2IEZlYiAyMDE3DQogICAgPj4N
CiAgICA+PiBTdW1tYXJ5Og0KICAgID4+DQogICAgPj4gICAgICAgIFRoaXMgZHJhZnQgaXMgb24g
dGhlIHJpZ2h0IHRyYWNrIGJ1dCBoYXMgb3BlbiBpc3N1ZXMsDQogICAgPj4gZGVzY3JpYmVkDQog
ICAgPj4gICAgICAgIGluIHRoZSByZXZpZXcuDQogICAgPj4NCiAgICA+PiBUZWNobmljYWwgaXNz
dWVzOg0KICAgID4+DQogICAgPj4gMS4gVGhlIEludHJvZHVjdGlvbiBzdGF0ZXMNCiAgICA+Pg0K
ICAgID4+ICAgIE90aGVyIHR5cGVzIG9mIGlkZW50aWZpZXJzIGFyZSBpbg0KICAgID4+ICAgIGNv
bW1vbiB1c2UsIGFuZCBldmVuIHJlZmVyZW5jZWQgaW4gUkZDIDQyODMuDQogICAgPj4NCiAgICA+
PiBGb3IgdGhlIHJlYWRlcidzIHNhbml0eSwgc29tZSBzb3J0IG9mIGFjY291bnRpbmcgbmVlZHMg
dG8gYmUgbWFkZSBvZg0KICAgID4+IHRoZXNlICJvdGhlciB0eXBlcyBvZiBpZGVudGlmaWVycyIs
IGVzcGVjaWFsbHkgYmVjYXVzZSBlYWNoIHR5cGUgb2YNCiAgICA+PiBpZGVudGlmaWVyIG5lZWRz
IGFuIGlkZW50aWZpZXIgdHlwZSBudW1iZXIuICBUaGUgdGV4dCBpbiA0MjgzIGlzDQogICAgPj4N
CiAgICA+PiAgICBTb21lIGV4YW1wbGVzIG9mIGlkZW50aWZpZXJzDQogICAgPj4gICAgaW5jbHVk
ZSBOZXR3b3JrIEFjY2VzcyBJZGVudGlmaWVyIChOQUkpLCBGdWxseSBRdWFsaWZpZWQgRG9tYWlu
DQogICAgPj4gTmFtZQ0KICAgID4+ICAgIChGUUROKSwgSW50ZXJuYXRpb25hbCBNb2JpbGUgU3Rh
dGlvbiBJZGVudGlmaWVyIChJTVNJKSwgYW5kIE1vYmlsZQ0KICAgID4+ICAgIFN1YnNjcmliZXIg
TnVtYmVyIChNU0lTRE4pLg0KICAgID4+DQogICAgPj4gQXJlIHRoZXJlIGFueSBvdGhlciB0eXBl
cyAiaW4gY29tbW9uIHVzZSI/DQogICAgPj4NCiAgICA+PiAtIE5BSSAodHlwZSAxKSBpcyBkZWZp
bmVkIGJ5IDQyODMuDQogICAgPj4gLSBGdWxseSBRdWFsaWZpZWQgRG9tYWluIE5hbWUgKEZRRE4p
IHNlZW1zIG5vdCB0byBiZSBzcGVjaWZpZWQNCiAgICA+PiAtIEludGVybmF0aW9uYWwgTW9iaWxl
IFN0YXRpb24gSWRlbnRpZmllciAoSU1TSSkgKHR5cGUgMykgaXMgZGVmaW5lZA0KICAgID4+IGlu
DQogICAgPj4gICB0aGlzIGRyYWZ0DQogICAgPj4gLSBNb2JpbGUgU3Vic2NyaWJlciBOdW1iZXIg
KE1TSVNETikgc2VlbXMgbm90IHRvIGJlIHNwZWNpZmllZA0KICAgID4+DQogICAgPj4gMi4gSXMg
aXQgaW50ZW5kZWQgdG8gaGF2ZSBhbiBJTUVJIGlkZW50aWZpZXIgdHlwZT8gIFRoZSBpbnRyb2R1
Y3Rpb24NCiAgICA+PiBtZW50aW9ucyBhbiBJTUVJIHR5cGUsIGJ1dCB0aGVyZSBpcyBubyBzcGVj
aWZpY2F0aW9uIGZvciBpdCwgbm9yIGlzDQogICAgPj4gdGhlcmUgYW4gaWRlbnRpZmllciB0eXBl
IG51bWJlciBhc3NpZ25lZCBmb3IgaXQuDQogICAgPj4NCiAgICA+PiAgICAuLi4gdHlwZXMgZm9y
IElNU0kNCiAgICA+PiAgICBbVGhyZWVHUFAtSURTXSwgUC1UTVNJIFtUaHJlZUdQUC1JRFNdLCBJ
TUVJIFtUaHJlZUdQUC1JRFNdLCBhbmQNCiAgICA+PiBHVVRJDQogICAgPj4gICAgW1RocmVlR1BQ
LUlEU10uDQogICAgPj4NCiAgICA+PiBJbml0aWFsbHkgSSBzdXNwZWN0ZWQgaXQgd2FzIGl0IHdh
cyBwcmVzZW50IGluIGFuIGVhcmxpZXIgcmV2aXNpb24NCiAgICA+PiBhbmQNCiAgICA+PiB0aGVu
IGxhdGVyIGRlbGV0ZWQgd2l0aG91dCB0aGlzIHJlZmVyZW5jZSBiZWluZyB1cGRhdGVkLiAgQnV0
IGFsbA0KICAgID4+IHZlcnNpb25zIG9mIGRyYWZ0LWlldGYtZG1tLTQyODNtbmlkcyBhbmQgaXRz
IHByZWRlY2Vzc29yDQogICAgPj4gZHJhZnQtcGVya2lucy1kbW0tNDI4M21uaWRzIG1lbnRpb24g
SU1FSSBpbiB0aGlzIHdheSBhcyBvbmUNCiAgICA+PiBpZGVudGlmaWVyDQogICAgPj4gdHlwZSwg
YnV0IG5vbmUgc3BlY2lmeSBpdCBpbiBhbnkgd2F5LiAgVGhlIG9ubHkgZGlzY3Vzc2lvbiBJIGNh
biBmaW5kDQogICAgPj4gb24gdGhlIERNTSBtYWlsaW5nIGxpc3Qgb2YgSU1FSSBpczoNCiAgICA+
Pg0KICAgID4+ICAgIA0KICAgID4+IGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9t
c2cvZG1tL3BObXRhcTYtSk9RNFJ1WHlfRDdaYzJKZ3ZZay8/cWlkDQogICAgPj4gPWQyOTU3NWY3
NjdjZTY3YTFlNjdhNzc2NzAwOGVlNmFmDQogICAgPj4NCiAgICA+PiAgICAgRnJvbTogTWFyY28g
TGllYnNjaCA8TWFyY28uTGllYnNjaEBuZWNsYWIuZXU+DQogICAgPj4gICAgIFRvOiBETU0NCiAg
ICA+PiAgICAgRGF0ZTogV2VkLCAxMCBTZXB0ZW1iZXIgMjAxNCAxMzoyOSBVVEMNCiAgICA+PiAg
ICAgUmU6IFtETU1dIHJlZ2FyZGluZyB0aGUgcmUtY2hhcnRlcmluZy4uDQogICAgPj4NCiAgICA+
PiAgICAgSXQgc2VlbXMgdGhlIE1OSUQgaXMgc29tZWhvdyBvdmVybG9hZGVkIHRvIGNhcnJ5IGJv
dGgsDQogICAgPj4gbm9kZS1zcGVjaWZpYw0KICAgID4+ICAgICBJRHMsIGUuZy4gTUFDLCBhcyB3
ZWxsIGFzIHN1YnNjcmliZXIgSURzLCB3aGljaCBpcyB0aGUgSU1TSS4NCiAgICA+PiAgICAgVGhl
cmUgbWF5IGJlIHZhbHVlIGluIGFkZGluZyB0aGUgSU1FSSB0byB0aGUgbGlzdCBvZiBwb3NzaWJs
ZQ0KICAgID4+IHR5cGVzIG9mDQogICAgPj4gICAgIG5vZGUtc3BlY2lmaWMgSURzLg0KICAgID4+
DQogICAgPj4gRWl0aGVyIHRoZSBwcmVzZW5jZSBvZiBJTUVJIGluIHRoaXMgbGlzdCBpcyBhIHNp
bXBsZSBtaXN0YWtlIHRoYXQgaGFzDQogICAgPj4gcGVyc2lzdGVkIGluIGFsbCB2ZXJzaW9ucyBv
ZiB0aGUgZHJhZnQsIG9yIHNwZWNpZnlpbmcgSU1FSSBoYXMgYWx3YXlzDQogICAgPj4gYmVlbiBp
bnRlbmRlZCBidXQgaGFzIGFsd2F5cyBiZWVuIG92ZXJsb29rZWQuDQogICAgPj4NCiAgICA+PiAz
LiBUaGUgZGVmaW5pdGlvbiBvZiBpZGVudGlmaWVyIHR5cGVzIGZvciBib3RoIEVVSS00OCBhbmQg
RVVJLTY0DQogICAgPj4gc3VnZ2VzdHMgdGhhdCBpdCBtaWdodCBiZSBkZXNpcmFibGUgdG8gZGVm
aW5lIGFuIGlkZW50aWZpZXIgdHlwZSBmb3INCiAgICA+PiBhcmJpdHJhcnkgaGFyZHdhcmUgKGxp
bmstbGV2ZWwpIGFkZHJlc3Nlcy4gIEl0IHNlZW1zIHRoYXQgdGhlIG5hdHVyYWwNCiAgICA+PiBk
aWZmZXJlbnRpYXRvciBmb3IgdGhhdCBwdXJwb3NlIGlzIHRoZSAiaGFyZHdhcmUgdHlwZSIgdXNl
ZCBpbiBBUlAsDQogICAgPj4gc28NCiAgICA+PiBhIEVVSS00OCBhZGRyZXNzIHdvdWxkIGJlIHJl
cHJlc2VudGVkIGFzDQogICAgPj4NCiAgICA+PiAgICAgTU4gaWRlbnRpZmllciB0eXBlIChvbmUg
b2N0ZXQpIDUgKHNheSkNCiAgICA+PiAgICAgaGFyZHdhcmUgdHlwZSAodHdvIG9jdGV0cykgMQ0K
ICAgID4+ICAgICBFVUktNDggKHNpeCBvY3RldHMpDQogICAgPj4NCiAgICA+PiBhbmQgYW4gRVVJ
LTY0IHNpbWlsYXJseSwgd2l0aCBoYXJkd2FyZSB0eXBlIDI3Lg0KICAgID4+DQogICAgPj4gQWx0
aG91Z2ggd2l0aCBvbmx5IHR3byBzdWJ0eXBlcyBpbiBjb21tb24gdXNlLCBnZW5lcmFsaXppbmcg
dGhpcw0KICAgID4+IG1pZ2h0DQogICAgPj4gbm90IGJlIHdvcnRoIHRoZSBlZmZvcnQuDQogICAg
Pj4NCiAgICA+PiA0LiBTZXZlcmFsIG9mIHRoZSBpZGVudGlmaWVyIHR5cGVzIGNhbiBiZSByZXBy
ZXNlbnRlZCBhcyBVUk5zOg0KICAgID4+DQogICAgPj4gLSBJTUVJIGNhbiBiZSByZXByZXNlbnRl
ZCBhcyBhIFVSTiBhcyB1cm46Z3NtYTppbWVpOi4uLg0KICAgID4+IC0gYWxsIG9mIHRoZSBSRklE
IHR5cGVzIGhhdmUgYSBVUk4gcmVwcmVzZW50YXRpb24gKGNhbGxlZCB0aGUNCiAgICA+PiAgICJw
dXJlLWlkZW50aXR5IFVSSSIgaW4gdGhlIFJGSUQgc3BlY2lmaWNhdGlvbnMpLCB3aGljaCBzdGFy
dHMNCiAgICA+PiAgIHVybjplcGM6aWQ6Li4uDQogICAgPj4NCiAgICA+PiBTaW5jZSBhbGwgVVJO
IHR5cGVzIGFyZSBlbnN1cmVkIG9mIGJlaW5nIHVuaXF1ZSBhbmQgcGVyc2lzdGVudCwgaXQNCiAg
ICA+PiBzZWVtcyB0aGF0IHdlIGNvdWxkIGRlZmluZSBhIE1OSUQgdHlwZSBmb3IgVVJOcyBnZW5l
cmFsbHksIGFuZCB0aGVuDQogICAgPj4gYW55IFJGSUQgVVJJIG9yIGFuIElNRUkgKGFzIGEgVVJO
KSBjb3VsZCBiZSB1c2VkIGFzIGEgdmFsdWUgb2YgdGhhdA0KICAgID4+IHR5cGUuDQogICAgPj4N
CiAgICA+PiBJZiB0aGlzIGlkZWEgaXMgYWRvcHRlZCwgaXQgc2VlbXMgdGhhdCB0aGUgb3RoZXIg
M0dQUCB0eXBlcyAoSU1TSSwNCiAgICA+PiBQLVRNU0ksIGFuZCBHVVRJKSBzaG91bGQgYmUgZ2l2
ZW4gZGVmaW5lZCBlbmNvZGluZ3MgYXMgVVJOcyBpbiBuZXcNCiAgICA+PiBzdWItbmFtZXNwYWNl
cyBvZiB0aGUgImdzbWEiIFVSTiBuYW1lc3BhY2UsIHRvIHBhcmFsbGVsIHRoZSBlbmNvZGluZw0K
ICAgID4+IG9mIElNRUlzIGRlZmluZWQgaW4gUkZDIDcyNTQuDQogICAgPj4NCiAgICA+PiBUaGlz
IGNvbnNvbGlkYXRpb24gY291bGQgYmUgc2lnbmlmaWNhbnRseSBiZW5lZmljaWFsLiAgSXQgYWxs
b3dzIE1OSUQNCiAgICA+PiB0byB1c2UgYW55IFVSTiBzY2hlbWUgYXMgYW4gaWRlbnRpZmllci4g
IEl0IHJlZHVjZXMgdGhlIHRocmVlDQogICAgPj4gZGlmZmVyZW50IFJGSUQgcmVwcmVzZW50YXRp
b25zIHRvIG9uZS4gIEl0IGluY29ycG9yYXRlcyBhbnkgZnV0dXJlDQogICAgPj4gZXhwYW5zaW9u
IG9mIFJGSUQgc2NoZW1lcyAoYmVjYXVzZSBhbGwgc2NoZW1lcyB3aWxsIGhhdmUgYQ0KICAgID4+
IHB1cmUtaWRlbnRpdHkgVVJOIHJlcHJlc2VudGF0aW9uKS4gIEEgZGlzYWR2YW50YWdlIGlzIHRo
YXQgdGhlIFVSTg0KICAgID4+IGVuY29kaW5ncyBhcmUgbG9uZywgYnV0IHRoZSBzZWN1cml0eSBj
b25zaWRlcmF0aW9ucyBzZWN0aW9uIHN0YXRlcw0KICAgID4+IHRoYXQgTU5JRHMgYXJlIHVzZWQg
b25seSBvbiB0aGUgZmlyc3QgcmVnaXN0cmF0aW9uIGF0IHRoZSBob21lIGFnZW50LA0KICAgID4+
IHNvIHRoZXJlIGlzbid0IG11Y2ggbmVlZCBmb3IgYnJldml0eS4NCiAgICA+Pg0KICAgID4+IFNp
bWlsYXJseSwgdGhpcyBhcHByb2FjaCBpbmNvcnBvcmF0ZXMgYW55IGZ1dHVyZSBleHBhbnNpb24g
b2YgbW9iaWxlDQogICAgPj4gaWRlbnRpZmllcnMgdGhhdCBHU01BIGRlY2lkZXMgdG8gZGVmaW5l
LCBhcyBsb25nIGFzIEdTTUEgcHJvdmlkZXMgYQ0KICAgID4+IFVSTiByZXByZXNlbnRhdGlvbiBm
b3IgaXQuDQogICAgPj4NCiAgICA+PiBUaGUgbW9zdCBzaWduaWZpY2FudCBkaXNhZHZhbnRhZ2Ug
aXMgdGhhdCBzb21lIFVSTiBzY2hlbWVzIGFsbG93DQogICAgPj4gc2V2ZXJhbCBjaGFyYWN0ZXIg
c3RyaW5ncyB0byAibWVhbiIgdGhlIHNhbWUgVVJOLiAgSW4gbW9zdCBVUk4NCiAgICA+PiBzY2hl
bWVzLCB0aGUgYWxsb3dlZCB2YXJpYXRpb24gaXMgbGltaXRlZCB0byB0aGUgY2FzZSBvZiBsZXR0
ZXJzLCBhbmQNCiAgICA+PiB0aGUgY29tbW9uIGNvbnZlbnRpb24gaXMgdG8gYWx3YXlzIHVzZSBs
b3dlci1jYXNlIHdoZW4gdGhlcmUgaXMgYQ0KICAgID4+IGNob2ljZSwgbGVhZGluZyB0byBhIHVu
aXF1ZSBjb252ZW50aW9uYWwgY2Fub25pY2FsIGZvcm0gZm9yIHRoZSBVUk4uDQogICAgPj4NCiAg
ICA+PiA1LiBSZWdhcmRpbmcgdGhlIGVuY29kaW5nIG9mIGEgc3RyaW5nIG9mIGRpZ2l0cyBpbnRv
IG9jdGV0cywgaXQgaXMNCiAgICA+PiBzdGF0ZWQgdGhhdCAiVGhlIGxhc3QgZGlnaXQgTVVTVCBi
ZSB6ZXJvIHBhZGRlZCwgaWYgbmVlZGVkLCBmb3IgZnVsbA0KICAgID4+IG9jdGV0IHNpemUuIiAg
VGhpcyBzZWVtcyB2ZXJ5IHVud2lzZSB1bmxlc3MgdGhlcmUgaXMgYSAzR1BQIGRlY3JlZQ0KICAg
ID4+IHRoYXQgaWYgYSB6ZXJvIGlzIGFwcGVuZGVkIHRvIGEgdmFsaWQgSU1TSSwgdGhlIHJlc3Vs
dGluZyBzdHJpbmcgaXMNCiAgICA+PiBuZXZlciBhIHZhbGlkIElNU0kuICBJbnN0ZWFkLCBJIHdv
dWxkIHNwZWNpZnkgdGhhdCBwYWRkaW5nIGlzIGJ5DQogICAgPj4gZmlsbGluZyB0aGUgbG93LW9y
ZGVyIDQgYml0cyBvZiB0aGUgZmluYWwgb2N0ZXQgd2l0aCAweEYuICBUaGF0DQogICAgPj4gZW5z
dXJlcyB0aGF0IHRoZSBlbmNvZGluZyBjYW4gYmUgdW5pcXVlbHkgZGVjb2RlZCBpbnRvIGFuIElN
U0kuDQogICAgPj4NCiAgICA+PiA2LiBUaGVyZSBhcmUgZm91ciB0eXBlcyBvZiBEVUlEIHNwZWNp
ZmllZCwgZWFjaCB3aXRoIGEgZGlzdGluY3QgTU5JRA0KICAgID4+IHZhbHVlLiAgSG93ZXZlciwg
RFVJRHMgY29udGFpbiBhbiBpbml0aWFsIHR3by1vY3RldCB0eXBlIGZpZWxkIHdoaWNoDQogICAg
Pj4gZGlzdGluZ3Vpc2hlcyB0aGUgdmFyaW91cyB0eXBlcyBvZiBEVUlELCBzbyBwcm92aWRpbmcg
dGhlbSB3aXRoDQogICAgPj4gZGlzdGluY3QgTU5JRCB2YWx1ZXMgaXMgcmVkdW5kYW50Lg0KICAg
ID4+DQogICAgPj4gRGlzdGluZ3Vpc2hpbmcgdGhlIHR5cGVzIGFuZCBhbGxvd2luZyBvbmx5IGZv
dXIgb2YgdGhlbSB0byBiZSB1c2VkIGFzDQogICAgPj4gTU5JRHMgc2VlbXMgdG8gYmUgY29udHJh
cnkgdG8gdGhlIHBoaWxvc29waHkgb2YgRFVJRCBjb25zdHJ1Y3Rpb24NCiAgICA+PiAoUkZDDQog
ICAgPj4gMzMxNSBzZWN0aW9uIDkpOg0KICAgID4+DQogICAgPj4gICAgQ2xpZW50cyBhbmQgc2Vy
dmVycyBNVVNUIHRyZWF0IERVSURzIGFzIG9wYXF1ZSB2YWx1ZXMgYW5kIE1VU1QNCiAgICA+PiBv
bmx5DQogICAgPj4gICAgY29tcGFyZSBEVUlEcyBmb3IgZXF1YWxpdHkuICBDbGllbnRzIGFuZCBz
ZXJ2ZXJzIE1VU1QgTk9UIGluIGFueQ0KICAgID4+ICAgIG90aGVyIHdheSBpbnRlcnByZXQgRFVJ
RHMuICBDbGllbnRzIGFuZCBzZXJ2ZXJzIE1VU1QgTk9UIHJlc3RyaWN0DQogICAgPj4gICAgRFVJ
RHMgdG8gdGhlIHR5cGVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCwgYXMgYWRkaXRpb25hbCBE
VUlEDQogICAgPj4gdHlwZXMNCiAgICA+PiAgICBtYXkgYmUgZGVmaW5lZCBpbiB0aGUgZnV0dXJl
Lg0KICAgID4+DQogICAgPj4gT2YgY291cnNlLCBNTklEIGlzbid0IGEgREhDUCBvcGVyYXRpb24s
IHNvIGl0IGlzbid0IHN1YmplY3QgdG8gdGhvc2UNCiAgICA+PiByZXF1aXJlbWVudHMsIGJ1dCBJ
IGV4cGVjdCB0aGF0IGRldmljZXMgd2lsbCB1c2UgdGhlIHNhbWUgRFVJRCBmb3INCiAgICA+PiBi
b3RoIG1vYmlsZSBpZGVudGlmaWNhdGlvbiwgYW5kIHdlIGRvbid0IHdhbnQgbW9iaWxlIGlkZW50
aWZpY2F0aW9uDQogICAgPj4gdG8NCiAgICA+PiByZXN0cmljdCBmdXR1cmUgZGV2ZWxvcG1lbnRz
IG9mIERIQ1AuDQogICAgPj4NCiAgICA+PiBJIHRoaW5rIHRoaXMgc3BlY2lmaWNhdGlvbiBtdXN0
IHRyZWF0IERVSURzIGFzIG9wYXF1ZSBhbmQgdXNlIG9ubHkNCiAgICA+PiBvbmUNCiAgICA+PiBN
TklEIHR5cGUgdGhhdCBhbGxvd3MgYWxsIHR5cGVzIG9mIERVSURzIGFzIHZhbHVlcy4NCiAgICA+
Pg0KICAgID4+IEVkaXRvcmlhbCBpc3N1ZXM6DQogICAgPj4NCiAgICA+PiBBYnN0cmFjdA0KICAg
ID4+DQogICAgPj4gICAgQWRkaXRpb25hbCBJZGVudGlmaWVyIFR5cGVzIGFyZSBwcm9wb3NlZCBm
b3IgdXNlIHdpdGggdGhlIE1vYmlsZQ0KICAgID4+IE5vZGUNCiAgICA+PiAgICBJZGVudGlmaWVy
IE9wdGlvbiBmb3IgSVB2NiAoUkZDIDQyODMpLg0KICAgID4+DQogICAgPj4gcy9wcm9wb3NlZC9k
ZWZpbmVkLw0KICAgID4+IFRoaXMgZG9jdW1lbnQgd2lsbCBkZWZpbmUgdGhlIG5ldyB0eXBlcyAo
b25jZSBpdCBpcyBhcHByb3ZlZCkhDQogICAgPj4NCiAgICA+PiAxLiAgSW50cm9kdWN0aW9uDQog
ICAgPj4NCiAgICA+PiAgICAuLi4gdHlwZXMgZm9yIElNU0kNCiAgICA+PiAgICBbVGhyZWVHUFAt
SURTXSwgUC1UTVNJIFtUaHJlZUdQUC1JRFNdLCBJTUVJIFtUaHJlZUdQUC1JRFNdLCBhbmQNCiAg
ICA+PiBHVVRJDQogICAgPj4gICAgW1RocmVlR1BQLUlEU10uDQogICAgPj4NCiAgICA+PiBUaGVy
ZSBpcyBubyBkZXNjcmlwdGlvbiBvZiBQLVRNU0kgaWRlbnRpZmllcnMsIGFsdGhvdWdoIGl0IGlz
DQogICAgPj4gYXNzaWduZWQNCiAgICA+PiBpZGVudGlmaWVyIHR5cGUgNC4NCiAgICA+Pg0KICAg
ID4+IFRoZXJlIGlzIG5vIGRlc2NyaXB0aW9uIG9mIEdVVEkgaWRlbnRpZmllcnMsIGFsdGhvdWdo
IGl0IGlzIGFzc2lnbmVkDQogICAgPj4gaWRlbnRpZmllciB0eXBlIDcuDQogICAgPj4NCiAgICA+
PiAzLiAgTmV3IE1vYmlsZSBOb2RlIElkZW50aWZpZXIgVHlwZXMNCiAgICA+Pg0KICAgID4+ICAg
IFRoZSBmb2xsb3dpbmcgdHlwZXMgb2YgaWRlbnRpZmllcnMgYXJlIGNvbW1vbmx5IHVzZWQgdG8g
aWRlbnRpZnkNCiAgICA+PiAgICBtb2JpbGUgbm9kZXMuICBGb3IgZWFjaCB0eXBlLCByZWZlcmVu
Y2VzIGFyZSBwcm92aWRlZCB3aXRoIGZ1bGwNCiAgICA+PiAgICBkZXRhaWxzIG9uIHRoZSBmb3Jt
YXQgb2YgdGhlIHR5cGUgb2YgaWRlbnRpZmllci4NCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcg
RGF0YSBzdGFuZGFyZCBwcm9tb3RlZCBieSBFbGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAg
ICA+PiAgICAoYWJicmV2aWF0ZWQgRVBDKSBzdXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3Rl
bXMgb3Igc2NoZW1lcw0KICAgID4+ICAgIGluY2x1ZGluZw0KICAgID4+DQogICAgPj4gICAgbyAg
UkZJRC1HSUQgKEdsb2JhbCBJZGVudGlmaWVyKSwNCiAgICA+PiAgICBvICBSRklELVNHVElOIChT
ZXJpYWxpemVkIEdsb2JhbCBUcmFkZSBJdGVtIE51bWJlciksDQogICAgPj4gICAgbyAgUkZJRC1T
U0NDIChTZXJpYWwgU2hpcHBpbmcgQ29udGFpbmVyKSwNCiAgICA+PiAgICBvICBSRklELVNHTE4g
KEdsb2JhbCBMb2NhdGlvbiBOdW1iZXIpLA0KICAgID4+ICAgIG8gIFJGSUQtR1JBSSAoR2xvYmFs
IFJldHVybmFibGUgQXNzZXQgSWRlbnRpZmllciksDQogICAgPj4gICAgbyAgUkZJRC1ET0QgKERl
cGFydG1lbnQgb2YgRGVmZW5zZSBJRCksIGFuZA0KICAgID4+ICAgIG8gIFJGSUQtR0lBSSAoR2xv
YmFsIEluZGl2aWR1YWwgQXNzZXQgSWRlbnRpZmllcikuDQogICAgPj4NCiAgICA+PiAgICBGb3Ig
ZWFjaCBSRklEIHNjaGVtZSBleGNlcHQgR0lELCB0aGVyZSBhcmUgdHdvIHZhcmlhdGlvbnM6IGEN
CiAgICA+PiA2NC1iaXQNCiAgICA+PiAgICBzY2hlbWUgKGZvciBleGFtcGxlLCBTR0xOLTY0KSBh
bmQgYSA5Ni1iaXQgc2NoZW1lIChTR0xOLTk2KS4gIEdJRA0KICAgID4+IGhhcw0KICAgID4+ICAg
IG9ubHkgYSA5Ni1iaXQgc2NoZW1lLiAgV2l0aGluIGVhY2ggc2NoZW1lLCBhbiBFUEMgaWRlbnRp
ZmllciBjYW4NCiAgICA+PiBiZQ0KICAgID4+ICAgIHJlcHJlc2VudGVkIGluIGEgYmluYXJ5IGZv
cm0gb3Igb3RoZXIgZm9ybXMgc3VjaCBhcyBVUkkuDQogICAgPj4NCiAgICA+PiAgICBUaGUgZm9s
bG93aW5nIGxpc3QgaW5jbHVkZXMgdGhlIGFib3ZlIFJGSUQgdHlwZXMgYXMgd2VsbCBhcw0KICAg
ID4+IHZhcmlvdXMNCiAgICA+PiAgICBvdGhlciBjb21tb24gaWRlbnRpZmllcnMgYW5kIHNldmVy
YWwgZGlmZmVyZW50IHR5cGVzIG9mIERVSURzLg0KICAgID4+DQogICAgPj4gVGhlIG9yZ2FuaXph
dGlvbiBvZiB0aGUgdGV4dCBoZXJlIHNlZW1zIHRvIGJlIHBvb3IgLS0gc2VjdGlvbiAzDQogICAg
Pj4gZW51bWVyYXRlcyB0aGUgbmV3IGlkZW50aWZpZXIgdHlwZXMsIGJ1dCBtdWNoIG9mIHRoZSB0
ZXh0IGF0IHRoZQ0KICAgID4+IGJlZ2lubmluZyBvZiB0aGUgc2VjdGlvbiBpcyBhYm91dCB0aGUg
UkZJRC1FUEMgc2V0IG9mIHR5cGVzLiAgSXQNCiAgICA+PiBzZWVtcw0KICAgID4+IGxpa2UgYSBi
ZXR0ZXIgb3JnYW5pemF0aW9uIGlzIHRvIHVzZSBqdXN0IHBhcmFncmFwaCAxIGZvbGxvd2VkIGJ5
DQogICAgPj4gdGFibGUgMSwgYW5kIG1vdmUgcGFyYWdyYXBocyAyLTUgaW50byBzZWN0aW9uIDQu
OS4NCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcgRGF0YSBzdGFuZGFyZCBwcm9tb3RlZCBieSBF
bGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAgICA+PiAgICAoYWJicmV2aWF0ZWQgRVBDKSBz
dXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3RlbXMgb3Igc2NoZW1lcw0KICAgID4+ICAgIGlu
Y2x1ZGluZw0KICAgID4+DQogICAgPj4gVGhlIHRleHQgaXMgdXNpbmcgIlRhZyBEYXRhIiwgIkVQ
QyIsIGFuZCAiUkZJRCIgaW4gYSB3YXkgdGhhdCBpcw0KICAgID4+IGludGVydHdpbmVkIGJ1dCBu
b3QgZXhwbGFpbmVkLiAgSSBjYW4gc2VlIHRoYXQgaXQgbWlnaHQgYmUgdXNlZnVsIHRvDQogICAg
Pj4gdXNlIGFsbCBvZiB0aGUgdGVybXMgaWYgdGhleSBjb21tb25seSB1c2VkIGluIHRoZSBmaWVs
ZCAoZG9uJ3QgZm9yZ2V0DQogICAgPj4gdG8gbWFrZSB0aGVtIGtleXdvcmRzIGZvciB0aGUgUkZD
ISksIGJ1dCB5b3UgbmVlZCB0byBleHBsYWluIHRoZWlyDQogICAgPj4gY29ubmVjdGlvbiBhbmQg
ZGlzdGluY3Rpb24gdG8gdGhlIHJlYWRlciBvciBtYWtlIGl0IGNsZWFyIHRoYXQgdGhlDQogICAg
Pj4gcmVhZGVyIGRvZXMgbm90IG5lZWQgdG8gdW5kZXJzdGFuZCB0aGUgZGlmZmVyZW5jZXMgYW1v
bmcgdGhlIHRlcm1zLg0KICAgID4+IEUuZy4sIHRoaXMgZm9ybXVsYXRpb24gdGllcyBhbGwgdGhy
ZWUgdGVybXMgdG9nZXRoZXINCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcgRGF0YSBzdGFuZGFy
ZCBwcm9tb3RlZCBieSBFbGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAgICA+PiAgICAoYWJi
cmV2aWF0ZWQgRVBDKSBzdXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3RlbXMgb3Igc2NoZW1l
cw0KICAgID4+ICAgIHdoaWNoIGFyZSBjb21tb25seSB1c2VkIGluIFJGSUQgKHJhZGlvLWZyZXF1
ZW5jeSBpZGVudGlmaWNhdGlvbikNCiAgICA+PiAgICBhcHBsaWNhdGlvbnMsIGluY2x1ZGluZw0K
ICAgID4+DQogICAgPj4gLS0NCiAgICA+Pg0KICAgID4+ICAgIEZvciBlYWNoIFJGSUQgc2NoZW1l
IGV4Y2VwdCBHSUQsIHRoZXJlIGFyZSB0d28gdmFyaWF0aW9uczogYQ0KICAgID4+IDY0LWJpdA0K
ICAgID4+ICAgIHNjaGVtZSAoZm9yIGV4YW1wbGUsIFNHTE4tNjQpIGFuZCBhIDk2LWJpdCBzY2hl
bWUgKFNHTE4tOTYpLiAgR0lEDQogICAgPj4gaGFzDQogICAgPj4gICAgb25seSBhIDk2LWJpdCBz
Y2hlbWUuICBXaXRoaW4gZWFjaCBzY2hlbWUsIGFuIEVQQyBpZGVudGlmaWVyIGNhbg0KICAgID4+
IGJlDQogICAgPj4gICAgcmVwcmVzZW50ZWQgaW4gYSBiaW5hcnkgZm9ybSBvciBvdGhlciBmb3Jt
cyBzdWNoIGFzIFVSSS4NCiAgICA+Pg0KICAgID4+IFRoZSB0ZXh0IHVzZXMgInNjaGVtZSIgdG8g
bWVhbiB0aGUgZGlzdGluY3Rpb24gYmV0d2VlbiBlbmNvZGluZw0KICAgID4+IHN5c3RlbXMgKEdJ
RCwgU0dUSU4sIGV0Yy4pIGFuZCBhbmQgYWxzbyB0byBtZWFuIHRoZSBkaXN0aW5jdGlvbg0KICAg
ID4+IGJldHdlZW4gdGhlIDY0LWJpdCBhbmQgOTYtYml0IHZhcmlhdGlvbnMuICBUaGlzIGFtYmln
dWl0eSBpcyB1bndpc2UuDQogICAgPj4gSXQgbWF0dGVycyBoZXJlLCBiZWNhdXNlIHlvdSBzYXkg
IndpdGhpbiBlYWNoIHNjaGVtZSAuLi4gY2FuIGJlDQogICAgPj4gcmVwcmVzZW50ZWQgaW4gYSBi
aW5hcnkgZm9ybSBvciAuLi4gVVJJIi4gIFdoaWNoIG1lYW5pbmcgb2YgInNjaGVtZSINCiAgICA+
PiBhcmUgeW91IHVzaW5nIGhlcmU/ICBJIHRob3VnaHQgeW91IG1lYW50IHRoZSBzZWNvbmQgbWVh
bmluZyB3aGVuIEkNCiAgICA+PiBmaXJzdCByZWFkIHRoZSBwYXJhZ3JhcGgsIGJ1dCBhZnRlciBy
ZWFkaW5nIGV4dGVybmFsIGRvY3VtZW50cyBhYm91dA0KICAgID4+IEVQQywgSSBub3cgdW5kZXJz
dGFuZCB0aGF0IHRoYXQgbGFzdCBzZW50ZW5jZSB1c2VzICJzY2hlbWUiIHRvIGluIHRoZQ0KICAg
ID4+IGZpcnN0IHNlbnNlLg0KICAgID4+DQogICAgPj4gWW91IG5lZWQgdG8gYmUgY2xlYXJlciBo
ZXJlIHRoYXQgdGhlcmUgYXJlIHRocmVlIHJlcHJlc2VudGF0aW9ucw0KICAgID4+IHVzZWQsDQog
ICAgPj4gNjQtYml0IGJpbmFyeSwgOTYtYml0IGJpbmFyeSwgYW5kIFVSSSAoVVJOLCBhY3R1YWxs
eSksIGFuZA0KICAgID4+IHJlcHJlc2VudGF0aW9uIGlzIG9ydGhvZ29uYWwgdG8gdGhlIHNldmVu
IFJGSUQgc2NoZW1lcywgd2l0aCB0aGUNCiAgICA+PiBleGNlcHRpb24gdGhhdCBSRklELUdJRCBk
b2VzIG5vdCBoYXZlIGEgOTYtYml0IGJpbmFyeSByZXByZXNlbnRhdGlvbi4NCiAgICA+Pg0KICAg
ID4+IEknbSBhc3N1bWluZyB0aGF0IHRoZSBUYWcgRGF0YSBzdGFuZGFyZCB1bmFtYmlndW91c2x5
IGRlZmluZXMgdGhlDQogICAgPj4gc2VyaWFsaXphdGlvbiBvZiB0aGUgYmluYXJ5IHJlcHJlc2Vu
dGF0aW9ucyBhcyBhIHNlcXVlbmNlIG9mIG9jdGV0cy4NCiAgICA+PiBJZiBpdCBkb2VzIG5vdCwg
dGhpcyBkb2N1bWVudCBNVVNUIGRvIHRoYXQsIG9yIHlvdSB3aWxsIGhhdmUgYW4NCiAgICA+PiBl
bmRsZXNzIG5pZ2h0bWFyZSBvZiBieXRlLW9yZGVyIHByb2JsZW1zLg0KICAgID4+DQogICAgPj4g
NC4gIERlc2NyaXB0aW9ucyBvZiBNTklEIHR5cGVzDQogICAgPj4NCiAgICA+PiBJZGVudGlmaWVy
IG93bmVyc2hpcCBpcyBhIGdlbmVyYWwgY29uY2VybiAtLSBpdCdzIHdvcnRoIG1lbnRpb25pbmcN
CiAgICA+PiBmb3INCiAgICA+PiBlYWNoIHR5cGUgb2YgaWRlbnRpZmllciB3aGVyZSB0aGUgYXNz
aWduZXIgb2YgdGhlIGlkZW50aWZpZXIgb2J0YWlucw0KICAgID4+IGRlbGVnYXRpb24uICBGb3Ig
YW4gRVVJLCBJIGV4cGVjdCB0aGUgcmVhZGVyIHdpbGwgYXNzdW1lIHRoYXQgaXQncyBhbg0KICAg
ID4+IEVVSSBhc3NpZ25lZCB0byB0aGUgZGV2aWNlIHVuZGVyIElFRUUgcnVsZXMsIGFuZCBzaW1p
bGFybHkgZm9yIFJGSUQNCiAgICA+PiBhbmQgM0dQUCBpZGVudGlmaWVycy4gIEJ1dCBmb3IgRFVJ
RCBpZGVudGlmaWVycywgaXQncyBsZXNzIGNsZWFyLg0KICAgID4+IEknbQ0KICAgID4+IGd1ZXNz
aW5nIHRoYXQgdGhlIERVSUQgaXMgb25lIHRoYXQgaXMsIG9yIGNvdWxkIGJlLCB1c2VkIGJ5IHRo
ZQ0KICAgID4+IGRldmljZQ0KICAgID4+IGZvciBESENQIHB1cnBvc2VzLiAgRm9yIElQdjYgYWRk
cmVzc2VzLCBpdCdzIGV2ZW4gbGVzcyBjbGVhciwgc2luY2UNCiAgICA+PiB0aGUgSVB2NiBhcmNo
aXRlY3R1cmUgZG9lc24ndCBhc3N1bWUgdGhhdCB0aGUgYXNzb2NpYXRpb24gb2YNCiAgICA+PiBh
ZGRyZXNzZXMNCiAgICA+PiB3aXRoIGRldmljZXMgaXMgcGVybWFuZW50Lg0KICAgID4+DQogICAg
Pj4gNC4xLiAgRGVzY3JpcHRpb24gb2YgdGhlIElQdjYgYWRkcmVzcyB0eXBlDQogICAgPj4NCiAg
ICA+PiBJdCB3b3VsZCBiZSBnb29kIGlmIHRoZSBkb2N1bWVudCBkZXNjcmliZWQgd2hhdCB0aGUg
c2VtYW50aWNzIG9mIHRoaXMNCiAgICA+PiBJRCBhcmUuICBZZXMsIGl0J3MgYSB1bmljYXN0IElQ
djYgYWRkcmVzcywgYnV0IHdoYXQgaXMgdGhlIGNvbm5lY3Rpb24NCiAgICA+PiBiZXR3ZWVuIHRo
YXQgYWRkcmVzcyBhbmQgdGhlIGRldmljZT8gIEkgc3VzcGVjdCB0aGUgY29ubmVjdGlvbiBpcw0K
ICAgID4+ICJ0aGUNCiAgICA+PiBkZXZpY2UgaGFzIGJlZW4gY29uZmlndXJlZCB0byBleHBlY3Qg
dGhhdCBpdCB3aWxsIGJlIGFzc2lnbmVkIHRoaXMNCiAgICA+PiBhZGRyZXNzIGFzIGEgbG9uZy10
ZXJtIGludGVyZmFjZSBhZGRyZXNzIiwgYnV0IHRoZXJlIGFyZSBvdGhlcg0KICAgID4+IHBvc3Np
YmlsaXRpZXMuICBFLmcuLCBJIGNhbiBpbWFnaW5lIGEgbW9iaWxlIGNhcnJpZXIgb2J0YWluaW5n
IGEgLzY0DQogICAgPj4gcHJlZml4ICh0aGVyZSBhcmUgcGxlbnR5IG9mIHRoZW0hKSBhbmQgdGhl
biBhc3NpZ25pbmcgYWRkcmVzc2VzIG91dA0KICAgID4+IG9mDQogICAgPj4gaXQgc2ltcGx5IHRv
IGNyZWF0ZSBhIHNlcXVlbmNlIG9mIHVuaXF1ZSBpZGVudGlmaWVycyBmb3IgZGV2aWNlcywgYnV0
DQogICAgPj4gbm90IHVzaW5nIHRob3NlIGFkZHJlc3NlcyBvbiBwYWNrZXRzLg0KICAgID4+DQog
ICAgPj4gVGhlbiBhZ2FpbiwgcGVyaGFwcyB5b3Ugd2FudCB0byBhbGxvdyBmbGV4aWJpbGl0eS4g
IEJ1dCBpbiBhbnkgY2FzZSwNCiAgICA+PiBJDQogICAgPj4gdGhpbmsgeW91IG5lZWQgdG8gc3Bl
Y2lmeSB3aGF0IHRoZSBydWxlcyBhcmUgZm9yIHdoYXQgYWRkcmVzcyBpcw0KICAgID4+IGFzc29j
aWF0ZWQgd2l0aCB3aGF0IGRldmljZS4NCiAgICA+Pg0KICAgID4+IDQuMi4gIERlc2NyaXB0aW9u
IG9mIHRoZSBJTVNJIE1OSUQgdHlwZQ0KICAgID4+DQogICAgPj4gV2hhdCBkb2VzICJpbiBuZXR3
b3JrIG9yZGVyIiBtZWFuIGhlcmU/ICBBcyBmYXIgYXMgSSBrbm93LCB0aGVyZSBpcw0KICAgID4+
IG5vDQogICAgPj4gZGVmaW5lZCAibmV0d29yayBvcmRlciIgZm9yIDQtYml0IHF1YW50aXRpZXMs
IG9ubHkgZm9yIGRpdmlkaW5nDQogICAgPj4gaW50ZWdlcnMgaW50byBvY3RldHMgYW5kIHBsYWNp
bmcgc2VxdWVuY2VzIG9mIGJpdHMgaW50byBvY3RldHMuICBJDQogICAgPj4gYXNzdW1lIHlvdSBt
ZWFuIHRoYXQgaW4gYW55IG9jdGV0LCB0aGUgaGlnaC1vcmRlciA0IGJpdHMgYXJlIHRoZQ0KICAg
ID4+IGZpcnN0DQogICAgPj4gZGlnaXQgYW5kIHRoZSBsb3ctb3JkZXIgNCBiaXRzIGFyZSB0aGUg
c2Vjb25kIGRpZ2l0LCBidXQgSSB0aGluayB5b3UNCiAgICA+PiBuZWVkIHRvIHN0YXRlIHRoYXQg
ZXhwbGljaXRseS4NCiAgICA+Pg0KICAgID4+IDQuMy4gIERlc2NyaXB0aW9uIG9mIHRoZSBFVUkt
NDggYWRkcmVzcyB0eXBlDQogICAgPj4NCiAgICA+PiAgICBUaGUgSUVFRSBFVUktNDggYWRkcmVz
cyBbSUVFRTgwMi1ldWk0OF0gaXMgZW5jb2RlZCBhcyBhIDYgb2N0ZXQNCiAgICA+PiAgICBzdHJp
bmcgY29udGFpbmluZyB0aGUgSUVFRSBFVUktNDggYWRkcmVzcy4NCiAgICA+Pg0KICAgID4+IElz
ICJzdHJpbmciIHRoZSBjb3JyZWN0IHdvcmQsIHRoaXMgbm90IGJlaW5nIGEgc2VxdWVuY2Ugb2YN
CiAgICA+PiBjaGFyYWN0ZXJzPw0KICAgID4+IEkgd291bGQgc2F5ICJzZXF1ZW5jZSBvZiA2IG9j
dGV0cyIgb3Igc2ltcGx5ICJlbmNvZGVkIGFzIDYgb2N0ZXRzIi4NCiAgICA+Pg0KICAgID4+IDQu
OS4gIERlc2NyaXB0aW9uIG9mIHRoZSBSRklEIHR5cGVzDQogICAgPj4NCiAgICA+PiBUaGlzIHNl
Y3Rpb24gbmVlZHMgdG8gYmUgcmV2aXNlZC4gIEl0IHByb3ZpZGVzIGEgbG90IG9mIGRldGFpbCBh
Ym91dA0KICAgID4+IHRoZSBSRklEIHR5cGVzLCBidXQgaXQncyBub3QgZW5vdWdoIGRldGFpbCBm
b3IgYSByZWFkZXIgd2hvIGRvZXNuJ3QNCiAgICA+PiB1bmRlcnN0YW5kIFJGSUQgdG8gbGVhcm4g
aG93IGFueSBwYXJ0aWN1bGFyIFJGSUQgc2NoZW1lIHdvcmtzLiAgRS5nLiwNCiAgICA+PiB0aGUg
Zmlyc3QgcGFyYWdyYXBoIHNheXMgdGhhdCBHSUQgY29udGFpbnMgdGhyZWUgZmllbGRzIGluIHRo
ZSBmaXJzdA0KICAgID4+IHNlbnRlbmNlLCBhbmQgdGhhdCBpdCBjb250YWlucyBmb3VyIGZpZWxk
cyBpbiB0aGUgdGhpcmQgc2VudGVuY2UuDQogICAgPj4gRGVzcGl0ZSB0aGlzLCB0aGUgZGVzY3Jp
cHRpb24gaXNuJ3QgZW5vdWdoIHRvIGFsbG93IHRoZSByZWFkZXIgdG8NCiAgICA+PiBjb25zdHJ1
Y3QgR0lEIGlkZW50aWZpZXJzIG1hbnVhbGx5Lg0KICAgID4+DQogICAgPj4gT24gdGhlIG90aGVy
IGhhbmQsIHJlYWRlcnMgd2hvIGFscmVhZHkgdW5kZXJzdGFuZCB0aGUgUkZJRCBzY2hlbWVzDQog
ICAgPj4gd2lsbCBmaW5kIHRoaXMgdGV4dCByZWR1bmRhbnQuDQogICAgPj4NCiAgICA+PiBJIHRo
aW5rIHRoYXQgYWxtb3N0IGFsbCBvZiB0aGlzIHRleHQgY2FuIGJlIHJlcGxhY2VkIGJ5IHJlZmVy
ZW5jZXMgdG8NCiAgICA+PiB0aGUgRVBDIGRvY3VtZW50cywgc2luY2UgdGhlc2UgaWRlbnRpZmll
cnMgYXJlIG9wYXF1ZSBmcm9tIHRoZSBwb2ludA0KICAgID4+IG9mIHZpZXcgb2YgbW9iaWxlIGlk
ZW50aWZpY2F0aW9uLg0KICAgID4+DQogICAgPj4gNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
DQogICAgPj4NCiAgICA+PiBUaGUgYmFzZSBNTklEIHNwZWNpZmljYXRpb24sIFJGQyA0MjgzLCBn
aXZlcyB0aGVzZSBzZWN1cml0eQ0KICAgID4+IGNvbnNpZGVyYXRpb25zIChzZWMgNCksIHdoaWNo
IG91Z2h0IHRvIGJlIHJlZmVyZW5jZWQgYW5kIHByb2JhYmx5DQogICAgPj4gc3VtbWFyaXplZCBp
biB0aGlzIHNlY3Rpb246DQogICAgPj4NCiAgICA+PiAgICBNb3Jlb3ZlciwgTU5JRHMgY29udGFp
bmluZyBzZW5zaXRpdmUgaWRlbnRpZmllcnMgbWlnaHQgb25seSBiZQ0KICAgID4+IHVzZWQNCiAg
ICA+PiAgICBmb3Igc2lnbmFsaW5nIGR1cmluZyBpbml0aWFsIG5ldHdvcmsgZW50cnkuICBTdWJz
ZXF1ZW50IGJpbmRpbmcNCiAgICA+PiAgICB1cGRhdGUgZXhjaGFuZ2VzIG1pZ2h0IHRoZW4gcmVs
eSBvbiBhIHRlbXBvcmFyeSBpZGVudGlmaWVyDQogICAgPj4gYWxsb2NhdGVkDQogICAgPj4gICAg
ZHVyaW5nIHRoZSBpbml0aWFsIG5ldHdvcmsgZW50cnksIHBlcmhhcHMgdXNpbmcgbWVjaGFuaXNt
cyBub3QNCiAgICA+PiAgICBzdGFuZGFyZGl6ZWQgd2l0aGluIHRoZSBJRVRGLiAgTWFuYWdpbmcg
dGhlIGFzc29jaWF0aW9uIGJldHdlZW4NCiAgICA+PiBsb25nLQ0KICAgID4+ICAgIGxpdmVkIGFu
ZCB0ZW1wb3JhcnkgaWRlbnRpZmllcnMgaXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcw0KICAg
ID4+ICAgIGRvY3VtZW50Lg0KICAgID4+DQogICAgPj4gV2hhdCBpcyB0aGUgbWVhbmluZyBvZiB0
aGUgd29yZCAibWlnaHQiIGluIHBhcmFncmFwaCAzPyAgSSBzdXNwZWN0DQogICAgPj4gdGhhdCB0
aGUgcHVycG9zZSBpcyB0byBxdWFsaWZ5IHRoaXMgcGFyYWdyYXBoIHdpdGggIk9uZSB3YXkgdG8N
CiAgICA+PiBhZGRyZXNzDQogICAgPj4gdGhlc2UgdnVsbmVyYWJpbGl0aWVzIGlzIHRvIG9ubHkg
dXNlIE1OSURzIGNvbnRhaW5pbmcgLi4uIi4gIEJ1dCBpZg0KICAgID4+IHRoYXQgaXMgdGhlIG1l
YW5pbmcsIHRoYXQgZXhwYW5kZWQgd29yZGluZyBzaG91bGQgYmUgdXNlZC4gIE90aGVyd2lzZQ0K
ICAgID4+IHRoZSB0ZXh0IHJlYWRzIGFzIGlmIGl0IGlzIGh5cG90aGV0aWNhbC4NCiAgICA+Pg0K
ICAgID4+IFtFTkRdDQogICAgPj4NCiAgICA+Pg0KICAgID4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgPj4gZG1tIG1haWxpbmcgbGlzdA0KICAg
ID4+IGRtbUBpZXRmLm9yZw0KICAgID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vZG1tDQogICAgPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KICAgID4gZG1tIG1haWxpbmcgbGlzdA0KICAgID4gZG1tQGlldGYub3JnDQogICAg
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RtbQ0KICAgID4NCiAgICAN
CiAgICANCg0K


From nobody Fri Feb 10 07:00:25 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A20AE12998D for <gen-art@ietf.org>; Fri, 10 Feb 2017 07:00:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Jean Mahoney" <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148673882466.29207.14828580901659737996.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 07:00:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Jjs2YBkwi9BZkklMBqRM9qgg8x4>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: mahoney@nostrum.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:00:24 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-02-16

Reviewer               Type      LC end     Draft
Brian Carpenter        Telechat  2017-02-09 draft-ietf-mmusic-sctp-sdp-23 *
Francis Dupont         Last Call 2017-02-14 draft-freytag-lager-variant-rules-03 *
Orit Levin             Last Call 2017-01-31 draft-ietf-sidr-delta-protocol-06
Pete Resnick           Telechat  2017-01-31 draft-ietf-ccamp-flexible-grid-ospf-ext-08 *
Lucy Yong              Last Call 2017-01-30 draft-ietf-sidr-rpki-rtr-rfc6810-bis-08

For telechat 2017-03-02

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-02-20 draft-ietf-httpbis-rfc5987bis-04
Francis Dupont         Last Call 2017-02-24 draft-kivinen-802-15-ie-04
Francis Dupont         Telechat  2017-02-24 draft-kivinen-802-15-ie-04
Jouni Korhonen         Last Call 2017-02-13 draft-ietf-pals-mpls-tp-dual-homing-coordination-05
Meral Shirazipour      Last Call 2017-02-10 draft-ietf-dmm-hnprenum-05
Robert Sparks          Last Call 2017-03-01 draft-ietf-6man-rfc4291bis-07
Robert Sparks          Telechat  2017-01-17 draft-ietf-mpls-residence-time-13 *
Peter Yee              Last Call 2017-03-01 draft-ietf-6man-rfc2460bis-08

Last calls:

Reviewer               Type      LC end     Draft
Fernando Gont          Last Call 2017-01-23 draft-ietf-dime-agent-overload-09
Vijay Gurbani          Last Call 2017-02-15 draft-ietf-grow-mrt-add-paths-03
Robert Sparks          Last Call 2017-03-09 draft-leiba-rfc2119-update-01
Dale Worley            Last Call 2017-02-20 draft-ietf-slim-negotiating-human-language-06

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Francis Dupont
  Roni Even
  Fernando Gont
  Vijay Gurbani
  Wassim Haddad
  Joel Halpern
  Christer Holmberg
  Russ Housley
  Jouni Korhonen
  Paul Kyzivat

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Fri Feb 10 07:30:45 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E769A1293EB; Fri, 10 Feb 2017 07:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.588
X-Spam-Level: 
X-Spam-Status: No, score=-4.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9BLFZ4OUA8K; Fri, 10 Feb 2017 07:30:38 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38111299D4; Fri, 10 Feb 2017 07:30:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486740637; bh=p9ZgACpUrg2s7MwHvTkWa+7J+uZMDVMgyJiL jYlugjU=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=D5ICUNk 1SX3xY2/5Ie5bnRitY3jP2yi6QbTnImgQuldB4JelPtvjRhlHd/Kv/KtrSs8E6vRKpt oimF6fGct7Cn1jiOG2HWkX5HHh88Iu2EJItM4eyr9RWTfdXOu02ZxDQPW/fc0UVmfEU TEygHfFmLCHfRMTu9yIWje7JiwjKpYyRpv0IKzyTi06l6du3Qs443fafZFgU54ue/Em qrKi/St8BqEM9IdEJhldd1YeikvQRH2EQQe+wxWW3XtvLxs7PEe5hab72d7r5JTIxl+ vDJferAZ+Sko/as8XtsK1QVFdcBJU7mxfq77E4Me1Ebss2FY3LvPhwkE3g03NtUUVuw ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=DAiyh7HSTtebU4N3mdop2M8MqUGLKU2O5ZHPIKEH5WxQ7QhNQ/PtiugXjZFMLi76TJKZa8XPhLa8wdFhAf2ixNS9d18ss44oj4Xe2u6U+p/wlKohHaZA561df+OisnyGDYLPXGDIOOpQyuqs+H5DsZ6GOItUh4cNQIS/iAb0vemRRWQjMHRZnrmptzL4Hb6LM4WuYZYCliCsBgySvIkQaNKMc4eC9Nw8xiNFl+4V4rB5SUWw4sL/tur0kekoeLfUGJXABo24Tya7hCPx0E0FTZmJOM+TT69L9JGfLHsrNSzE2/9E/4rvZCnAkNSlmNRtQYoO+cz1Zh4yt0wdlMPeSw==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ccD9A-0001KY-SL; Fri, 10 Feb 2017 10:30:05 -0500
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net> <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
Date: Fri, 10 Feb 2017 07:30:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7b153f6b79f77d65ed61c86f789d10901350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Xb1WivWez5zC9G3jmGnwlEZ_CL4>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:30:42 -0000

Hello folks,

The last two days have been crammed full with other urgent work 
requirements.  I will respond to these comments today.

Suresh, do you mean to ask if I can submit a revised document before Monday?

Regards,
Charlie P.


On 2/10/2017 6:17 AM, Suresh Krishnan wrote:
> Hi Charlie,
>    I have not yet seen a response to this review. Do you think you will be able to get to this in the next day or two? The document is on the February 16 2017 telechat and I would like to see resolution to these issues in time for the other ADs to ballot.
>
> Thanks
> Suresh
>
> On 2/2/17, 1:10 AM, "Charlie Perkins" <charles.perkins@earthlink.net> wrote:
>
>      Hello Sri,
>      
>      The review was indeed super.  I'll respond sometime in the next few days.
>      
>      Regards,
>      Charlie P.
>      
>      
>      On 2/1/2017 9:09 PM, Sri Gundavelli (sgundave) wrote:
>      > Thank you Dale for a great review.
>      >
>      >
>      > Charlie/Authors - Can you please respond to Dale and address these
>      > comments.
>      >
>      >
>      > Regards
>      > Sri
>      >
>      >
>      > On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
>      > on behalf of worley@ariadne.com> wrote:
>      >
>      >> Reviewer: Dale Worley
>      >> Review result: Ready with Issues
>      >>
>      >> I am the assigned Gen-ART reviewer for this draft.  The General Area
>      >> Review Team (Gen-ART) reviews all IETF documents being processed
>      >> by the IESG for the IETF Chair.  Please treat these comments just
>      >> like any other last call comments.
>      >>
>      >> For more information, please see the FAQ at
>      >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>      >>
>      >> Document:  draft-ietf-dmm-4283mnids-04
>      >> Reviewer:  Dale R. Worley
>      >> Review Date:  31 Jan 2017
>      >> IETF LC End Date:  2 Feb 2017
>      >> IESG Telechat date:  16 Feb 2017
>      >>
>      >> Summary:
>      >>
>      >>        This draft is on the right track but has open issues,
>      >> described
>      >>        in the review.
>      >>
>      >> Technical issues:
>      >>
>      >> 1. The Introduction states
>      >>
>      >>    Other types of identifiers are in
>      >>    common use, and even referenced in RFC 4283.
>      >>
>      >> For the reader's sanity, some sort of accounting needs to be made of
>      >> these "other types of identifiers", especially because each type of
>      >> identifier needs an identifier type number.  The text in 4283 is
>      >>
>      >>    Some examples of identifiers
>      >>    include Network Access Identifier (NAI), Fully Qualified Domain
>      >> Name
>      >>    (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>      >>    Subscriber Number (MSISDN).
>      >>
>      >> Are there any other types "in common use"?
>      >>
>      >> - NAI (type 1) is defined by 4283.
>      >> - Fully Qualified Domain Name (FQDN) seems not to be specified
>      >> - International Mobile Station Identifier (IMSI) (type 3) is defined
>      >> in
>      >>   this draft
>      >> - Mobile Subscriber Number (MSISDN) seems not to be specified
>      >>
>      >> 2. Is it intended to have an IMEI identifier type?  The introduction
>      >> mentions an IMEI type, but there is no specification for it, nor is
>      >> there an identifier type number assigned for it.
>      >>
>      >>    ... types for IMSI
>      >>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>      >> GUTI
>      >>    [ThreeGPP-IDS].
>      >>
>      >> Initially I suspected it was it was present in an earlier revision
>      >> and
>      >> then later deleted without this reference being updated.  But all
>      >> versions of draft-ietf-dmm-4283mnids and its predecessor
>      >> draft-perkins-dmm-4283mnids mention IMEI in this way as one
>      >> identifier
>      >> type, but none specify it in any way.  The only discussion I can find
>      >> on the DMM mailing list of IMEI is:
>      >>
>      >>
>      >> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>      >> =d29575f767ce67a1e67a7767008ee6af
>      >>
>      >>     From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>      >>     To: DMM
>      >>     Date: Wed, 10 September 2014 13:29 UTC
>      >>     Re: [DMM] regarding the re-chartering..
>      >>
>      >>     It seems the MNID is somehow overloaded to carry both,
>      >> node-specific
>      >>     IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>      >>     There may be value in adding the IMEI to the list of possible
>      >> types of
>      >>     node-specific IDs.
>      >>
>      >> Either the presence of IMEI in this list is a simple mistake that has
>      >> persisted in all versions of the draft, or specifying IMEI has always
>      >> been intended but has always been overlooked.
>      >>
>      >> 3. The definition of identifier types for both EUI-48 and EUI-64
>      >> suggests that it might be desirable to define an identifier type for
>      >> arbitrary hardware (link-level) addresses.  It seems that the natural
>      >> differentiator for that purpose is the "hardware type" used in ARP,
>      >> so
>      >> a EUI-48 address would be represented as
>      >>
>      >>     MN identifier type (one octet) 5 (say)
>      >>     hardware type (two octets) 1
>      >>     EUI-48 (six octets)
>      >>
>      >> and an EUI-64 similarly, with hardware type 27.
>      >>
>      >> Although with only two subtypes in common use, generalizing this
>      >> might
>      >> not be worth the effort.
>      >>
>      >> 4. Several of the identifier types can be represented as URNs:
>      >>
>      >> - IMEI can be represented as a URN as urn:gsma:imei:...
>      >> - all of the RFID types have a URN representation (called the
>      >>   "pure-identity URI" in the RFID specifications), which starts
>      >>   urn:epc:id:...
>      >>
>      >> Since all URN types are ensured of being unique and persistent, it
>      >> seems that we could define a MNID type for URNs generally, and then
>      >> any RFID URI or an IMEI (as a URN) could be used as a value of that
>      >> type.
>      >>
>      >> If this idea is adopted, it seems that the other 3GPP types (IMSI,
>      >> P-TMSI, and GUTI) should be given defined encodings as URNs in new
>      >> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>      >> of IMEIs defined in RFC 7254.
>      >>
>      >> This consolidation could be significantly beneficial.  It allows MNID
>      >> to use any URN scheme as an identifier.  It reduces the three
>      >> different RFID representations to one.  It incorporates any future
>      >> expansion of RFID schemes (because all schemes will have a
>      >> pure-identity URN representation).  A disadvantage is that the URN
>      >> encodings are long, but the security considerations section states
>      >> that MNIDs are used only on the first registration at the home agent,
>      >> so there isn't much need for brevity.
>      >>
>      >> Similarly, this approach incorporates any future expansion of mobile
>      >> identifiers that GSMA decides to define, as long as GSMA provides a
>      >> URN representation for it.
>      >>
>      >> The most significant disadvantage is that some URN schemes allow
>      >> several character strings to "mean" the same URN.  In most URN
>      >> schemes, the allowed variation is limited to the case of letters, and
>      >> the common convention is to always use lower-case when there is a
>      >> choice, leading to a unique conventional canonical form for the URN.
>      >>
>      >> 5. Regarding the encoding of a string of digits into octets, it is
>      >> stated that "The last digit MUST be zero padded, if needed, for full
>      >> octet size."  This seems very unwise unless there is a 3GPP decree
>      >> that if a zero is appended to a valid IMSI, the resulting string is
>      >> never a valid IMSI.  Instead, I would specify that padding is by
>      >> filling the low-order 4 bits of the final octet with 0xF.  That
>      >> ensures that the encoding can be uniquely decoded into an IMSI.
>      >>
>      >> 6. There are four types of DUID specified, each with a distinct MNID
>      >> value.  However, DUIDs contain an initial two-octet type field which
>      >> distinguishes the various types of DUID, so providing them with
>      >> distinct MNID values is redundant.
>      >>
>      >> Distinguishing the types and allowing only four of them to be used as
>      >> MNIDs seems to be contrary to the philosophy of DUID construction
>      >> (RFC
>      >> 3315 section 9):
>      >>
>      >>    Clients and servers MUST treat DUIDs as opaque values and MUST
>      >> only
>      >>    compare DUIDs for equality.  Clients and servers MUST NOT in any
>      >>    other way interpret DUIDs.  Clients and servers MUST NOT restrict
>      >>    DUIDs to the types defined in this document, as additional DUID
>      >> types
>      >>    may be defined in the future.
>      >>
>      >> Of course, MNID isn't a DHCP operation, so it isn't subject to those
>      >> requirements, but I expect that devices will use the same DUID for
>      >> both mobile identification, and we don't want mobile identification
>      >> to
>      >> restrict future developments of DHCP.
>      >>
>      >> I think this specification must treat DUIDs as opaque and use only
>      >> one
>      >> MNID type that allows all types of DUIDs as values.
>      >>
>      >> Editorial issues:
>      >>
>      >> Abstract
>      >>
>      >>    Additional Identifier Types are proposed for use with the Mobile
>      >> Node
>      >>    Identifier Option for IPv6 (RFC 4283).
>      >>
>      >> s/proposed/defined/
>      >> This document will define the new types (once it is approved)!
>      >>
>      >> 1.  Introduction
>      >>
>      >>    ... types for IMSI
>      >>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>      >> GUTI
>      >>    [ThreeGPP-IDS].
>      >>
>      >> There is no description of P-TMSI identifiers, although it is
>      >> assigned
>      >> identifier type 4.
>      >>
>      >> There is no description of GUTI identifiers, although it is assigned
>      >> identifier type 7.
>      >>
>      >> 3.  New Mobile Node Identifier Types
>      >>
>      >>    The following types of identifiers are commonly used to identify
>      >>    mobile nodes.  For each type, references are provided with full
>      >>    details on the format of the type of identifier.
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    including
>      >>
>      >>    o  RFID-GID (Global Identifier),
>      >>    o  RFID-SGTIN (Serialized Global Trade Item Number),
>      >>    o  RFID-SSCC (Serial Shipping Container),
>      >>    o  RFID-SGLN (Global Location Number),
>      >>    o  RFID-GRAI (Global Returnable Asset Identifier),
>      >>    o  RFID-DOD (Department of Defense ID), and
>      >>    o  RFID-GIAI (Global Individual Asset Identifier).
>      >>
>      >>    For each RFID scheme except GID, there are two variations: a
>      >> 64-bit
>      >>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>      >> has
>      >>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>      >> be
>      >>    represented in a binary form or other forms such as URI.
>      >>
>      >>    The following list includes the above RFID types as well as
>      >> various
>      >>    other common identifiers and several different types of DUIDs.
>      >>
>      >> The organization of the text here seems to be poor -- section 3
>      >> enumerates the new identifier types, but much of the text at the
>      >> beginning of the section is about the RFID-EPC set of types.  It
>      >> seems
>      >> like a better organization is to use just paragraph 1 followed by
>      >> table 1, and move paragraphs 2-5 into section 4.9.
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    including
>      >>
>      >> The text is using "Tag Data", "EPC", and "RFID" in a way that is
>      >> intertwined but not explained.  I can see that it might be useful to
>      >> use all of the terms if they commonly used in the field (don't forget
>      >> to make them keywords for the RFC!), but you need to explain their
>      >> connection and distinction to the reader or make it clear that the
>      >> reader does not need to understand the differences among the terms.
>      >> E.g., this formulation ties all three terms together
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    which are commonly used in RFID (radio-frequency identification)
>      >>    applications, including
>      >>
>      >> --
>      >>
>      >>    For each RFID scheme except GID, there are two variations: a
>      >> 64-bit
>      >>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>      >> has
>      >>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>      >> be
>      >>    represented in a binary form or other forms such as URI.
>      >>
>      >> The text uses "scheme" to mean the distinction between encoding
>      >> systems (GID, SGTIN, etc.) and and also to mean the distinction
>      >> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>      >> It matters here, because you say "within each scheme ... can be
>      >> represented in a binary form or ... URI".  Which meaning of "scheme"
>      >> are you using here?  I thought you meant the second meaning when I
>      >> first read the paragraph, but after reading external documents about
>      >> EPC, I now understand that that last sentence uses "scheme" to in the
>      >> first sense.
>      >>
>      >> You need to be clearer here that there are three representations
>      >> used,
>      >> 64-bit binary, 96-bit binary, and URI (URN, actually), and
>      >> representation is orthogonal to the seven RFID schemes, with the
>      >> exception that RFID-GID does not have a 96-bit binary representation.
>      >>
>      >> I'm assuming that the Tag Data standard unambiguously defines the
>      >> serialization of the binary representations as a sequence of octets.
>      >> If it does not, this document MUST do that, or you will have an
>      >> endless nightmare of byte-order problems.
>      >>
>      >> 4.  Descriptions of MNID types
>      >>
>      >> Identifier ownership is a general concern -- it's worth mentioning
>      >> for
>      >> each type of identifier where the assigner of the identifier obtains
>      >> delegation.  For an EUI, I expect the reader will assume that it's an
>      >> EUI assigned to the device under IEEE rules, and similarly for RFID
>      >> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>      >> I'm
>      >> guessing that the DUID is one that is, or could be, used by the
>      >> device
>      >> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>      >> the IPv6 architecture doesn't assume that the association of
>      >> addresses
>      >> with devices is permanent.
>      >>
>      >> 4.1.  Description of the IPv6 address type
>      >>
>      >> It would be good if the document described what the semantics of this
>      >> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>      >> between that address and the device?  I suspect the connection is
>      >> "the
>      >> device has been configured to expect that it will be assigned this
>      >> address as a long-term interface address", but there are other
>      >> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>      >> prefix (there are plenty of them!) and then assigning addresses out
>      >> of
>      >> it simply to create a sequence of unique identifiers for devices, but
>      >> not using those addresses on packets.
>      >>
>      >> Then again, perhaps you want to allow flexibility.  But in any case,
>      >> I
>      >> think you need to specify what the rules are for what address is
>      >> associated with what device.
>      >>
>      >> 4.2.  Description of the IMSI MNID type
>      >>
>      >> What does "in network order" mean here?  As far as I know, there is
>      >> no
>      >> defined "network order" for 4-bit quantities, only for dividing
>      >> integers into octets and placing sequences of bits into octets.  I
>      >> assume you mean that in any octet, the high-order 4 bits are the
>      >> first
>      >> digit and the low-order 4 bits are the second digit, but I think you
>      >> need to state that explicitly.
>      >>
>      >> 4.3.  Description of the EUI-48 address type
>      >>
>      >>    The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>      >>    string containing the IEEE EUI-48 address.
>      >>
>      >> Is "string" the correct word, this not being a sequence of
>      >> characters?
>      >> I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>      >>
>      >> 4.9.  Description of the RFID types
>      >>
>      >> This section needs to be revised.  It provides a lot of detail about
>      >> the RFID types, but it's not enough detail for a reader who doesn't
>      >> understand RFID to learn how any particular RFID scheme works.  E.g.,
>      >> the first paragraph says that GID contains three fields in the first
>      >> sentence, and that it contains four fields in the third sentence.
>      >> Despite this, the description isn't enough to allow the reader to
>      >> construct GID identifiers manually.
>      >>
>      >> On the other hand, readers who already understand the RFID schemes
>      >> will find this text redundant.
>      >>
>      >> I think that almost all of this text can be replaced by references to
>      >> the EPC documents, since these identifiers are opaque from the point
>      >> of view of mobile identification.
>      >>
>      >> 5.  Security Considerations
>      >>
>      >> The base MNID specification, RFC 4283, gives these security
>      >> considerations (sec 4), which ought to be referenced and probably
>      >> summarized in this section:
>      >>
>      >>    Moreover, MNIDs containing sensitive identifiers might only be
>      >> used
>      >>    for signaling during initial network entry.  Subsequent binding
>      >>    update exchanges might then rely on a temporary identifier
>      >> allocated
>      >>    during the initial network entry, perhaps using mechanisms not
>      >>    standardized within the IETF.  Managing the association between
>      >> long-
>      >>    lived and temporary identifiers is outside the scope of this
>      >>    document.
>      >>
>      >> What is the meaning of the word "might" in paragraph 3?  I suspect
>      >> that the purpose is to qualify this paragraph with "One way to
>      >> address
>      >> these vulnerabilities is to only use MNIDs containing ...".  But if
>      >> that is the meaning, that expanded wording should be used.  Otherwise
>      >> the text reads as if it is hypothetical.
>      >>
>      >> [END]
>      >>
>      >>
>      >> _______________________________________________
>      >> dmm mailing list
>      >> dmm@ietf.org
>      >> https://www.ietf.org/mailman/listinfo/dmm
>      > _______________________________________________
>      > dmm mailing list
>      > dmm@ietf.org
>      > https://www.ietf.org/mailman/listinfo/dmm
>      >
>      
>      
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>


From nobody Fri Feb 10 07:35:17 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA56D1299F1; Fri, 10 Feb 2017 07:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJrhxPbwcbF7; Fri, 10 Feb 2017 07:35:10 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3599A1299EB; Fri, 10 Feb 2017 07:35:09 -0800 (PST)
X-AuditID: c6180641-c53ff70000000a06-31-589d9756878f
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id 96.0E.02566.6579D985; Fri, 10 Feb 2017 11:35:06 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 10:35:05 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSe/j/cjYYsQbutUCsVh56ND0V9aFVgPUAgAAQ6gCADSuDgIAAA5SAgAABaIA=
Date: Fri, 10 Feb 2017 15:35:04 +0000
Message-ID: <54184D70-CFE4-4BCF-A7BA-075D2EC767FE@ericsson.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net> <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com> <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
In-Reply-To: <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrEIsWRmVeSWpSXmKPExsUyuXRPrG7U9LkRBltu8ljcv3ONzeL+oxqL /7O3sFtcffWZxeLZxvksFgf/bGOzeHmizIHdY/L+r8weU35vZPVY9WUCs8eSJT+ZAliiuGxS UnMyy1KL9O0SuDL2/njFWrDEqGLa1YvMDYwf9LsYOTkkBEwkZuxYx9bFyMUhJLCeUWLByzvs EM5yRon5u5ezgVSxAVVt2PmZCcQWETCWaOi9xwxiMwv8Y5TYeNkYxBYWsJCYOf0yI0SNpcTE GReZIWw/ie9/V4DZLAKqEsv6vgPN4eDgFbCXuHTEAGLXDCaJ3a1PwHZxCjhKXOs7BFbPKCAm 8f3UGiaIXeISt57MZ4K4WkTi4cXTbBC2qMTLx/9YIWwliY+/54M9wCwwhVFiyr/TYA28AoIS J2c+YZnAKDILyaxZyOpmIamDKNKWWLbwNfMsoGOZBXQkJi9khAibSrw++hHKtpaY8esgG4St KDGl+yH7AkaOVYwcpcUFObnpRoabGIGxeUyCzXEH495ez0OMAhyMSjy8G7znRAixJpYVV+Ye YlQBan20YfUFRimWvPy8VCUR3sc35kYI8aYkVlalFuXHF5XmpBYfYpTmYFES570ecj9cSCA9 sSQ1OzW1ILUIJsvEwSnVwJj8qYDpgvfRfXZZx6b6zDyy//9jHduVZ6dsucdz6V1ewts/zFf/ L5aPqZ3RXVfS/vbSxUA/y9Wt8oET35c/C1913qtyn6K07IbVl0SLmmy/Wc6Meyig9N5iWpLr Hz9+kx+RsnGBfF+cOgL4Ny5fW8vx4aR01JpJC2Pmvr4SflyvdU2Utm1aZLgSS3FGoqEWc1Fx IgCJjE+E1QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_hAHrcGE8U-14NZ3s51UUgOvms0>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Gen art <gen-art@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, Sri Gundavelli <sgundave@cisco.com>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:35:12 -0000

--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Charlie,

> On Feb 10, 2017, at 10:30 AM, Charlie Perkins =
<charles.perkins@earthlink.net> wrote:
>=20
> Hello folks,
>=20
> The last two days have been crammed full with other urgent work =
requirements.  I will respond to these comments today.

Great.

>=20
> Suresh, do you mean to ask if I can submit a revised document before =
Monday?

No. If you can agree on the changes to be applied with Dale by =
Monday/Tuesday I think it would be great. If there are other comments in =
IESG eval, you can address them as well in a new revision.

Thanks
Suresh


--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjEwMTUzNTA0WjAjBgkqhkiG9w0B
CQQxFgQUF8FHCP6B39DJNK3w7EZmBO66BG4wXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQAaxZykHmGn669je599n3IJWdMlQOL9Ged26nK8NP10IwJVkwedvzEKFfaqkpC7
MOvs4hnztmdlpKGOZAQq57iimbJXRXaeypExikciCQtm04r3GnxAIB58Glp2qlhxoAKGZJVDKht5
FhkmwewHbE83Xz5VQ2cXde4tR4HjJrdxWizk+WARERwbL4cZtJbFMZ2uv8byf/Dz60W5djUYnt09
gOzvEY0PCyTMjjGC/lepSC/rEqMUudv1PgmtPOjFDxbDy1Gm8fWhf4sB8BFTKx1GCpjU+L8jxQR7
vT6fyyn4TqRV8npy5VzJkcr4GsEV8jBUzcQpqx3P2kxzdfN2dUoFAAAAAAAA

--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199--


From nobody Fri Feb 10 07:39:15 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1514E1299F2; Fri, 10 Feb 2017 07:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qb4IaPqc8krZ; Fri, 10 Feb 2017 07:39:04 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D4561299EB; Fri, 10 Feb 2017 07:39:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1AFd3wx045561; Fri, 10 Feb 2017 08:39:03 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1AFcw40045152 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 10 Feb 2017 08:38:58 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 10 Feb 2017 07:38:57 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Fri, 10 Feb 2017 07:38:57 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXA=
Date: Fri, 10 Feb 2017 15:38:57 +0000
Message-ID: <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
In-Reply-To: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0E7-yUFX8EN84KoU-yPziW76mvQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:39:06 -0000

Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
converge to the minimum MTU of all paths in the multipath, and so it is
still OK to store the MTU in the network layer where it would be shared
by all flows.

ECMP does present challenges for RFC4821, however. If a first transport
session discovers a large MTU and shares it with a second transport
session, the second session may take a very different path where there
is a smaller MTU and encounter a black hole. IMHO, it might be a good
idea to file an erratum to RFC4821 explaining how ECMP might cause
problems if discovered MTUs are shared between sessions.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Friday, February 10, 2017 2:21 AM
> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stew=
art@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
>=20
>=20
> On 10/02/2017 03:25, Brian E Carpenter wrote:
> > Stewart,
> >
> > On 10/02/2017 04:19, Stewart Bryant wrote:
> > ...
> >> I wonder if we would best serve both our future and our heritage
> >> if we declared RFC1981 as historic, and either left the idea there,
> >> or declared it as historic and wrote a new text from a clean start?
> > I don't see that. It's a stable, widely deployed, interoperable
> > mechanism. That is rather orthogonal to the issue that has been raised,
> > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > across the Internet.
>=20
> I will not debate whether it is faulty or not, but it seems that in
> practice the
> Internet breaks the mechanism. However it breaks it is a way that seems
> disruptive to some user traffic. The document is really guidance
> one how hosts might use  ICMP for optimization, and arguable need
> not be a standard at all.
>=20
> My remark about heritage is that this vintage draft is very much a
> product of
> its time, and really needs modernizing, and after modernizing ought to
> look quite different, and thus maybe we should employ a procedure
> other than a simple replacement.
>=20
>=20
> > ...
> >> It is concerning that the draft does not talk in any detail about
> >> how modern ECMP works, i.e. using the five tuple, and noting that
> >> the PMTU may be different depending on the transport layer port
> >> numbers.
> > Has this problem been analysed for, say, IPv4? And does the real world
> > contain ECMP setups with different MTUs on different paths?
>=20
> I don't know if anyone has looked. Since the mechanism is
> self-correcting albeit
> with some disruption to user traffic it looks to the application and the
> application
> user, just like the Internet not working for a few moments.
>=20
> In a well managed SP network there should not be, but neither should ther=
e
> be asymmetric path costs, but there are. The less well manage private
> networks are less well managed.
>=20
>=20
> >
> >> Given that a very large fraction of packets will traverse an MPLS
> >> network at some point, I am surprised that there is no text talking
> >> about the importance of providing support for this feature in the
> >> MPLS domain. RFC3988 talks to this point, but is only experimental.
> > I don't understand. How does the fact that there might be some MPLS
> > segments along the path affect end-to-end PMTUD?
>=20
> The point that RFC3988 makes is that MPLS looks like a single hop to IP
> and the
> PE has to fragment or has to reply with an ICMP error message to support
> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
> result
> in the right response at the end node.
>=20
> My point is that the draft is silent on the subject, and perhaps it
> should not be.
>=20
> However your question make me ask a further question. The draft is also
> silent
> on NATs. Is there any advice needed for people designing and configuring
> NATs?
>=20
> >
> >> =3D=3D=3D=3D=3D=3D
> >>
> >>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
> >>     could use the flow id as the local representation of a path. Packe=
ts
> >>     sent to a particular destination but belonging to different flows =
may
> >>     use different paths, with the choice of path depending on the flow
> >>     id.  This approach will result in the use of optimally sized packe=
ts
> >>     on a per-flow basis, providing finer granularity than PMTU values
> >>     maintained on a per-destination basis.
> >>
> >> SB> How widely is flow-id supported in networks? I thought that the
> >> SB> current position was that it was unreliable as an ECMP indicator
> >> SB> and thus routers tended to glean information from the packet thems=
elves.
> > This is future-proofing. Agreed, usage today is limited.
> >
> > (But it would be better to call it the Flow Label for consistency with =
other
> > recent RFCs.)
>=20
> Well the question is whether it is simply limited today, or broken today
> in a manner that
> is irrecoverable? I don't know, but I do know that the mainstream ECMP
> approach
> is the five-tuple. There is something akin to the flow label being
> deployed in MPLS. However
> what distinguishes the MPLS Entropy Label is that it is inserted (and
> removed) by the
> service provider and is therefore trusted by the service provider.
>=20
> >
> > I think your other comments are all valuable.
> Thank you.
>=20
> Stewart
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



From nobody Fri Feb 10 11:45:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE3B1295A2; Fri, 10 Feb 2017 11:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOxZ3dYvUwbD; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E7E5129540; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id 19so3069934pfo.3; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=swUDx54phvfF0lOJ8hCltKAaJz4Je2hRCpTLONbFpxE=; b=lZ9rxZpcxBgBycFYjYudiE8smtLoEKuo6uJhdWncUj/jY9FvtZw6xMUyYHVkBFB5wN WmITLo/bmNhptJKVrNYYpyse9pHvJo3/hfXRY/3FnnOa14cRHYqb6B7fAftGxEvb81t3 jm92G8ndxKQmjm7yXa3F7hNw4xiAjqw5iQomRGcjGm5WkzloTZiY3eGMSdVVM0Z4pMUx j3Cu6vUGU4ttPIbmrnIcYg+9yKqJpXCOwfoSSsVlV4O8BEVrVQpJFVBn4zeEQ7CNbhMs ObPnlEloaM10GI8y0ERq/7m4lw+IOIcADRscnbA8oSJ71Dr/wQrkPweoQIA7ubMSpVFM qibg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=swUDx54phvfF0lOJ8hCltKAaJz4Je2hRCpTLONbFpxE=; b=Rdm/4tHvDHgDGlet7UAb8LXOK728NTmvWqdLXMgoCFWi2fI0dbkVu2/vzJiX+W5uHU e84Gfpl5ebz2862DZoH9LPEV5YelHCZSgc/0m9E8G8pBOf1fNVx8J3eTUWHMYqaUZwPM vhdYqir2Bvh1OmzwGVc/oodKRNUkiHgRCmvo1sDPgkxkmbq/k5Ic+qOEaxbpOTjIdWod sQt72/GTL+tl+tMZ9Nj9JLXoFloIgOuHt3vupm0XFT51C/d8j1K0TroY21PzbUUA2/cb qyILRpBQwb3+TcE/T6Szv0aVbSQR3XHnt2JxZITs9Drmy+fA2NVlG51HUMkA/qtrfFeu 5cmQ==
X-Gm-Message-State: AMke39nbKoqJl/w80yPTzdf2nru48VoswBBke/MHKhfCEsZhsKIh+9ozCvU8xEgxgyX63w==
X-Received: by 10.99.109.143 with SMTP id i137mr12712107pgc.11.1486755936371;  Fri, 10 Feb 2017 11:45:36 -0800 (PST)
Received: from ?IPv6:2406:e007:769c:1:28cc:dc4c:9703:6781? ([2406:e007:769c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g70sm7160051pfb.50.2017.02.10.11.45.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 11:45:35 -0800 (PST)
To: Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
Date: Sat, 11 Feb 2017 08:45:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6Wr4FieY97fJ20uic4_S_lmV8Sk>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 19:45:38 -0000

On 10/02/2017 23:20, Stewart Bryant wrote:
> 
> 
> On 10/02/2017 03:25, Brian E Carpenter wrote:
>> Stewart,
>>
>> On 10/02/2017 04:19, Stewart Bryant wrote:
>> ...
>>> I wonder if we would best serve both our future and our heritage
>>> if we declared RFC1981 as historic, and either left the idea there,
>>> or declared it as historic and wrote a new text from a clean start?
>> I don't see that. It's a stable, widely deployed, interoperable
>> mechanism. That is rather orthogonal to the issue that has been raised,
>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>> across the Internet.
> 
> I will not debate whether it is faulty or not, but it seems that in 

It's faulty by the standard of RFC4890 (which is Informational).

> practice the
> Internet breaks the mechanism. However it breaks it is a way that seems
> disruptive to some user traffic. The document is really guidance
> one how hosts might use  ICMP for optimization, and arguable need
> not be a standard at all.

I think that's a mischaracterisation of the mechanism (and the draft).
PMTUD is not an optimisation. Without it, you get black holes.

> 
> My remark about heritage is that this vintage draft is very much a 
> product of
> its time, and really needs modernizing, and after modernizing ought to
> look quite different, and thus maybe we should employ a procedure
> other than a simple replacement.

It's proposed for Internet Standard. That means it must replace the
PS document and must specify the same thing, plus corrections, minus
unused features.

>> ...
>>> It is concerning that the draft does not talk in any detail about
>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>> the PMTU may be different depending on the transport layer port
>>> numbers.
>> Has this problem been analysed for, say, IPv4? And does the real world
>> contain ECMP setups with different MTUs on different paths?
> 
> I don't know if anyone has looked. Since the mechanism is 
> self-correcting albeit
> with some disruption to user traffic it looks to the application and the 
> application
> user, just like the Internet not working for a few moments.
> 
> In a well managed SP network there should not be, but neither should there
> be asymmetric path costs, but there are. The less well manage private
> networks are less well managed.
> 
> 
>>
>>> Given that a very large fraction of packets will traverse an MPLS
>>> network at some point, I am surprised that there is no text talking
>>> about the importance of providing support for this feature in the
>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>> I don't understand. How does the fact that there might be some MPLS
>> segments along the path affect end-to-end PMTUD?
> 
> The point that RFC3988 makes is that MPLS looks like a single hop to IP 
> and the
> PE has to fragment or has to reply with an ICMP error message to support
> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to 
> result
> in the right response at the end node.
> 
> My point is that the draft is silent on the subject, and perhaps it 
> should not be.

Well, in general it's silent on tunnels. They have to emulate links,
as stated in section 2. I still don't see why an MPLS tunnel is a special case.

> 
> However your question make me ask a further question. The draft is also 
> silent
> on NATs. Is there any advice needed for people designing and configuring 
> NATs?

Yes, for NAT64/NAT46 - in RFC6145. For NAT66, the advice is "don't".

>>
>>> ======
>>>
>>>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>     could use the flow id as the local representation of a path. Packets
>>>     sent to a particular destination but belonging to different flows may
>>>     use different paths, with the choice of path depending on the flow
>>>     id.  This approach will result in the use of optimally sized packets
>>>     on a per-flow basis, providing finer granularity than PMTU values
>>>     maintained on a per-destination basis.
>>>
>>> SB> How widely is flow-id supported in networks? I thought that the
>>> SB> current position was that it was unreliable as an ECMP indicator
>>> SB> and thus routers tended to glean information from the packet themselves.
>> This is future-proofing. Agreed, usage today is limited.
>>
>> (But it would be better to call it the Flow Label for consistency with other
>> recent RFCs.)
> 
> Well the question is whether it is simply limited today, or broken today 
> in a manner that
> is irrecoverable? 

Nothing's broken. It's just underused.

> I don't know, but I do know that the mainstream ECMP
> approach is the five-tuple.

Sure, but see RFC6438 for some of the difficulties that
causes with IPv6.

> There is something akin to the flow label being
> deployed in MPLS. However
> what distinguishes the MPLS Entropy Label is that it is inserted (and 
> removed) by the
> service provider and is therefore trusted by the service provider.

Exactly the same for ECMP tunnels, in RFC6438. Guess what, my co-author
was from a provider.

   Brian

>>
>> I think your other comments are all valuable.
> Thank you.
> 
> Stewart
> .
> 


From nobody Fri Feb 10 14:04:25 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312871295BC for <gen-art@ietfa.amsl.com>; Fri, 10 Feb 2017 14:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2phDAIUyo_6 for <gen-art@ietfa.amsl.com>; Fri, 10 Feb 2017 14:04:22 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5573912947F for <gen-art@ietf.org>; Fri, 10 Feb 2017 14:04:22 -0800 (PST)
X-AuditID: c618062d-d73ff700000009d8-68-589e48b7f697
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id 64.1A.02520.8B84E985; Sat, 11 Feb 2017 00:11:53 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 17:04:20 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
Thread-Index: AdKD6ZEOEm2JbixvTNGh/9pedfA2UQ==
Date: Fri, 10 Feb 2017 22:04:19 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DA@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DAeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyuXRPgu5Oj3kRBk8nilmcP9/LbHH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj97np7AW3dSu+r33N1sA4X6OLkZNDQsBE 4uOLRWxdjFwcQgLrGSUWbnvNDJIQEljOKPH/XDWIzSZgIbH993NWkCIRgQ5Gid5vu9lBEsIC 9hKn9y8EsjmAEi4Sc9dVgoRFBPQkNnw8zgISZhFQlTj2Ug8kzCvgKzH/01QWEJtRQEzi+6k1 TCA2s4C4xK0n85kg7hGQWLLnPDOELSrx8vE/VghbSWLS0nOsEPX5Ev/2HGSEmCkocXLmE5YJ jIKzkIyahaRsFpIyiLiOxILdn9ggbG2JZQtfM8PYZw48ZkIWX8DIvoqRo7S4ICc33chgEyMw 5I9JsOnuYLw/3fMQowAHoxIP7wbeeRFCrIllxZW5hxglOJiVRHjbjIBCvCmJlVWpRfnxRaU5 qcWHGKU5WJTEeeNW3w8XEkhPLEnNTk0tSC2CyTJxcEo1MNadSZHfH6WZvqEj5Vj6JLElj8/k zOxukJzkIp/MsFPYtvSK6yULe63/r2886rp2INdmKU9ngLZ1T/pd7l1id3TyQmYs32B41UJ9 g+ylbx2iRX2Oez0u3KkS2rN7Tc7ndY9u1dT/vXopZtcqsZn8qw5O+xywyW7nsewV15O3/JFx Vvkk9No/8LISS3FGoqEWc1FxIgBF4vB3dQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_2Pd7TLsRaR1FKqXXgLFBSNfuMs>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 22:04:24 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DAeusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.
For more information, please see the FAQ at <http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq>.


Document: draft-ietf-dmm-hnprenum-05
Reviewer: Meral Shirazipour
Review Date: 2017-02-10
IETF LC End Date:   2017-02-10
IESG Telechat date: -


Summary:
This draft is ready to be published as Standards Track RFC but I have comme=
nts.

Major issues:
Minor issues:
Nits/editorial comments:
-Abstract:
Current:
"However, the current PMIPv6 specification does not specify related operati=
ons when an HNP renumbering is happened.".
Suggestion for more clarity:
"However, the current PMIPv6 specification does not specify related operati=
ons when an HNP renumbering has happened (e.g. due to change of service pro=
vider, change of site topology, etc.).".
-[Page 3], "to an MAG"---->"to a MAG"

-[Page 7], "the proceduer"--->"the procedure"

Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DAeusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair.&nbsp; Please treat these comments jus=
t like any other last call comments.<o:p></o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-dmm-hnprenum-05<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-02-10<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp;&nbsp; 2017-02-10<o:p></o:p><=
/p>
<p class=3D"MsoNormal">IESG Telechat date: -<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-Abstract:<o:p></o:p></p>
<p class=3D"MsoNormal">Current: <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;However, the current PMIPv6 specification does=
 not specify related operations when an HNP renumbering is happened.&quot;.=
<o:p></o:p></p>
<p class=3D"MsoNormal">Suggestion for more clarity:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;However, the current PMIPv6 specification does=
 not specify related operations when an HNP renumbering has happened (e.g. =
due to change of service provider, change of site topology, etc.).&quot;.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 3], &quot;to an MAG&quot;----&gt;&quot;to a M=
AG&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 7], &quot;the proceduer&quot;---&gt;&quot;the=
 procedure&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DAeusaamb107erics_--


From nobody Fri Feb 10 14:29:31 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0144129E75; Fri, 10 Feb 2017 14:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7TRqykg-poB; Fri, 10 Feb 2017 14:29:21 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A3E129DC6; Fri, 10 Feb 2017 14:29:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486765760; bh=NBBNkzcneukveGKcrKonaU2IS7LMOzfY0+d3 FZQv7d0=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace: X-Originating-IP; b=IjEREYXu4O7MDECgGGbRE9OHLV6ZqnpaZNXxRE5HIOH1D4 x/2LeAt0ZCjA7yTVE0pD2IR4LrYEA5uNMbJC1BFzs9/uc+tU6e8tgvTEeNtwuXZHsQK zgVwJYwAfAtBaVx5lqvGNkVT/mrk82qxh6Cc2NZvvK+G8zC2YDOEtZ7OrjIbB0oRfHV B3ZYCXaokGnrjkd9WLZb38dWQyicHxO6EGehXO4xSgkiUX92LAJ216OWXhdaZuVojKP 4mxhCWsRzbtH5778gR5vg8/igY8nmbnpVA9NQashz0eSVH0U64OCycs3bbNpvn/2m1I rmVvaAp9PE7uKevtvV+sp4mcYfAA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=N97Z4iuHYnUdyuL3brNQuX2cJmdnw8+Vdl4mWLdxftcXqOlPeJsTSEPifxh5v6JK1rkMQN13Naj1apqf7u+IfE96JFH6ReH/HrfRhKz4kAbgOMaOIechYkVoo9omkrMKoLavxkhHPN5jhj6n4E1xpV/3lj0z60d6X6VHRpf5YXNbP3K9z7CRJAoN0rAYEbQ7TtfWf6BGgP/o4lt0hgEaG9/2FZt9eSuSGkXy776hzogY1IR7+oodeaSCI9UKMf0U+CXmbFKY+L88uWTJTPVwOJHwd4dxtEg7Ypzlk9lbC04dbewhRFYH7JSmdmvQeRShNEe4k0gUWCmUzldFRqlWag==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ccJgP-0006un-JW; Fri, 10 Feb 2017 17:28:49 -0500
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
Date: Fri, 10 Feb 2017 14:28:45 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------34D9108758E61C1C73F50279"
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac788c72805e4d8e22a6c46c4a40f98dc8c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nWCSmS52czmcrng0XHS5aQ1HBao>
Cc: draft-ietf-dmm-4283mnids.all@ietf.org, ietf@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 22:29:26 -0000

This is a multi-part message in MIME format.
--------------34D9108758E61C1C73F50279
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello Dale,

Thanks for the thorough review.  My follow-up comments are inline below.


On 1/31/2017 11:34 AM, Dale Worley wrote:
> 1. The Introduction states
>
>     Other types of identifiers are in
>     common use, and even referenced in RFC 4283.
>
> For the reader's sanity, some sort of accounting needs to be made of
> these "other types of identifiers", especially because each type of
> identifier needs an identifier type number.  The text in 4283 is
>
>     Some examples of identifiers
>     include Network Access Identifier (NAI), Fully Qualified Domain
> Name
>     (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>     Subscriber Number (MSISDN).
>
> Are there any other types "in common use"?

I will add some text according to your suggestion.  My criterion for 
whether the identifier type was included in the document was whether or 
not anyone had asked for it to be included.

>
> - NAI (type 1) is defined by 4283.
> - Fully Qualified Domain Name (FQDN) seems not to be specified
> - International Mobile Station Identifier (IMSI) (type 3) is defined
> in
>    this draft
> - Mobile Subscriber Number (MSISDN) seems not to be specified

It is not the jurisdiction of the MNIDs document to specify these 
identifiers, but citations for the specifications are located elsewhere 
in the document.  I will also include those citations here.

>
> 2. Is it intended to have an IMEI identifier type?  The introduction
> mentions an IMEI type, but there is no specification for it, nor is
> there an identifier type number assigned for it.
>
>     ... types for IMSI
>     [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
> GUTI
>     [ThreeGPP-IDS].
>
> Initially I suspected it was it was present in an earlier revision
> and
> then later deleted without this reference being updated.  But all
> versions of draft-ietf-dmm-4283mnids and its predecessor
> draft-perkins-dmm-4283mnids mention IMEI in this way as one
> identifier
> type, but none specify it in any way.  The only discussion I can find
> on the DMM mailing list of IMEI is:
>
>     
> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af
>
>      From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>      To: DMM
>      Date: Wed, 10 September 2014 13:29 UTC
>      Re: [DMM] regarding the re-chartering..
>
>      It seems the MNID is somehow overloaded to carry both,
> node-specific
>      IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>      There may be value in adding the IMEI to the list of possible
> types of
>      node-specific IDs.
>
> Either the presence of IMEI in this list is a simple mistake that has
> persisted in all versions of the draft, or specifying IMEI has always
> been intended but has always been overlooked.

I don't know why this happened, but I am happy to include an identifier 
type for IMEI as well as a citation for it.  Thanks for catching this 
and looking through the archives!

>
> 3. The definition of identifier types for both EUI-48 and EUI-64
> suggests that it might be desirable to define an identifier type for
> arbitrary hardware (link-level) addresses.  It seems that the natural
> differentiator for that purpose is the "hardware type" used in ARP,
> so
> a EUI-48 address would be represented as
>
>      MN identifier type (one octet) 5 (say)
>      hardware type (two octets) 1
>      EUI-48 (six octets)
>
> and an EUI-64 similarly, with hardware type 27.
>
> Although with only two subtypes in common use, generalizing this
> might
> not be worth the effort.

Actually, I am O.K. either way on this matter.  However, at this point 
in time it does not seem that we are likely to see any other link 
hardware address types to be used as MNIDs.

>
> 4. Several of the identifier types can be represented as URNs:
>
> - IMEI can be represented as a URN as urn:gsma:imei:...
> - all of the RFID types have a URN representation (called the
>    "pure-identity URI" in the RFID specifications), which starts
>    urn:epc:id:...
>
> Since all URN types are ensured of being unique and persistent, it
> seems that we could define a MNID type for URNs generally, and then
> any RFID URI or an IMEI (as a URN) could be used as a value of that
> type.
>
> If this idea is adopted, it seems that the other 3GPP types (IMSI,
> P-TMSI, and GUTI) should be given defined encodings as URNs in new
> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
> of IMEIs defined in RFC 7254.
>
> This consolidation could be significantly beneficial.  It allows MNID
> to use any URN scheme as an identifier.  It reduces the three
> different RFID representations to one.  It incorporates any future
> expansion of RFID schemes (because all schemes will have a
> pure-identity URN representation).  A disadvantage is that the URN
> encodings are long, but the security considerations section states
> that MNIDs are used only on the first registration at the home agent,
> so there isn't much need for brevity.
>
> Similarly, this approach incorporates any future expansion of mobile
> identifiers that GSMA decides to define, as long as GSMA provides a
> URN representation for it.
>
> The most significant disadvantage is that some URN schemes allow
> several character strings to "mean" the same URN.  In most URN
> schemes, the allowed variation is limited to the case of letters, and
> the common convention is to always use lower-case when there is a
> choice, leading to a unique conventional canonical form for the URN.

There is a sort of "hidden" disadvantage to long names, especially for 
tiny devices using constrained link layers.  Namely, a longer name makes 
it more likely to require lower-layer fragmentation.  I'm not sure that 
it should be the job of a layer-3 mobility entity to parse URNs and 
determine if two different flavors are supposed to be equivalent.

Other than that, I don't have any real objection to reorganizing the 
namespace, but I'd like some additional confirmation that it's a good idea.

>
> 5. Regarding the encoding of a string of digits into octets, it is
> stated that "The last digit MUST be zero padded, if needed, for full
> octet size."  This seems very unwise unless there is a 3GPP decree
> that if a zero is appended to a valid IMSI, the resulting string is
> never a valid IMSI.  Instead, I would specify that padding is by
> filling the low-order 4 bits of the final octet with 0xF.  That
> ensures that the encoding can be uniquely decoded into an IMSI.

I am O.K. with this.  I need to go find out where I got that language 
from, because I don't think I was the person who crafted it.

>
> 6. There are four types of DUID specified, each with a distinct MNID
> value.  However, DUIDs contain an initial two-octet type field which
> distinguishes the various types of DUID, so providing them with
> distinct MNID values is redundant.
>
> Distinguishing the types and allowing only four of them to be used as
> MNIDs seems to be contrary to the philosophy of DUID construction
> (RFC
> 3315 section 9):
>
>     Clients and servers MUST treat DUIDs as opaque values and MUST
> only
>     compare DUIDs for equality.  Clients and servers MUST NOT in any
>     other way interpret DUIDs.  Clients and servers MUST NOT restrict
>     DUIDs to the types defined in this document, as additional DUID
> types
>     may be defined in the future.
>
> Of course, MNID isn't a DHCP operation, so it isn't subject to those
> requirements, but I expect that devices will use the same DUID for
> both mobile identification, and we don't want mobile identification
> to
> restrict future developments of DHCP.
>
> I think this specification must treat DUIDs as opaque and use only
> one
> MNID type that allows all types of DUIDs as values.

Thanks for this observation.  I will make the corresponding revisions to 
the text.

>
> Editorial issues:
>
> Abstract
>
>     Additional Identifier Types are proposed for use with the Mobile
> Node
>     Identifier Option for IPv6 (RFC 4283).
>
> s/proposed/defined/
> This document will define the new types (once it is approved)!

O.K. with your modification.  The document just defines numbers for the 
types, not the types.

>
> 1.  Introduction
>
>     ... types for IMSI
>     [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
> GUTI
>     [ThreeGPP-IDS].
>
> There is no description of P-TMSI identifiers, although it is
> assigned
> identifier type 4.
>
> There is no description of GUTI identifiers, although it is assigned
> identifier type 7.

I will insert text from the relevant 3GPP documents to describe these 
identifiers.

>
> 3.  New Mobile Node Identifier Types
>
>     The following types of identifiers are commonly used to identify
>     mobile nodes.  For each type, references are provided with full
>     details on the format of the type of identifier.
>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     including
>
>     o  RFID-GID (Global Identifier),
>     o  RFID-SGTIN (Serialized Global Trade Item Number),
>     o  RFID-SSCC (Serial Shipping Container),
>     o  RFID-SGLN (Global Location Number),
>     o  RFID-GRAI (Global Returnable Asset Identifier),
>     o  RFID-DOD (Department of Defense ID), and
>     o  RFID-GIAI (Global Individual Asset Identifier).
>
>     For each RFID scheme except GID, there are two variations: a
> 64-bit
>     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
> has
>     only a 96-bit scheme.  Within each scheme, an EPC identifier can
> be
>     represented in a binary form or other forms such as URI.
>
>     The following list includes the above RFID types as well as
> various
>     other common identifiers and several different types of DUIDs.
>
> The organization of the text here seems to be poor -- section 3
> enumerates the new identifier types, but much of the text at the
> beginning of the section is about the RFID-EPC set of types.  It
> seems
> like a better organization is to use just paragraph 1 followed by
> table 1, and move paragraphs 2-5 into section 4.9.

O.K.  Thanks for the suggestion.

>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     including
>
> The text is using "Tag Data", "EPC", and "RFID" in a way that is
> intertwined but not explained.  I can see that it might be useful to
> use all of the terms if they commonly used in the field (don't forget
> to make them keywords for the RFC!), but you need to explain their
> connection and distinction to the reader or make it clear that the
> reader does not need to understand the differences among the terms.
> E.g., this formulation ties all three terms together
>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     which are commonly used in RFID (radio-frequency identification)
>     applications, including

Thanks for the text.  I will use it.

> --
>
>     For each RFID scheme except GID, there are two variations: a
> 64-bit
>     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
> has
>     only a 96-bit scheme.  Within each scheme, an EPC identifier can
> be
>     represented in a binary form or other forms such as URI.
>
> The text uses "scheme" to mean the distinction between encoding
> systems (GID, SGTIN, etc.) and and also to mean the distinction
> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
> It matters here, because you say "within each scheme ... can be
> represented in a binary form or ... URI".  Which meaning of "scheme"
> are you using here?  I thought you meant the second meaning when I
> first read the paragraph, but after reading external documents about
> EPC, I now understand that that last sentence uses "scheme" to in the
> first sense.
>
> You need to be clearer here that there are three representations
> used,
> 64-bit binary, 96-bit binary, and URI (URN, actually), and
> representation is orthogonal to the seven RFID schemes, with the
> exception that RFID-GID does not have a 96-bit binary representation.

This is a good idea.  How about the following:

>    For each RFID scheme except GID, there are three representations:
>     - a 64-bit binary representation (for example, SGLN-64)
>     - a 96-bit binary representation (SGLN-96).
>     - a representation as a URI

I didn't originate the use of URI for the non-binary representation. The 
EPC document has the following language:

> All categories of URIs are represented as Uniform Reference Names 
> (URNs) as defined by [RFC2141], where the URN Namespace is epc.
>

If I were to change it to URN, then I would have to go into some detail 
about why this document somehow disagrees with the EPC-Tag-Data 
document.  Do you think that is necessary?

>
> I'm assuming that the Tag Data standard unambiguously defines the
> serialization of the binary representations as a sequence of octets.
> If it does not, this document MUST do that, or you will have an
> endless nightmare of byte-order problems.

I read through some relevant text in the EPC-Tag-Data document and it 
seems O.K. to me, but nontrivial and it relies on digging through other 
even more arcane documents to be absolutely sure.  I am pretty sure that 
the IETF document should not get into the business of augmenting the 
standards already in place from the external SDOs.

>
> 4.  Descriptions of MNID types
>
> Identifier ownership is a general concern -- it's worth mentioning
> for
> each type of identifier where the assigner of the identifier obtains
> delegation.  For an EUI, I expect the reader will assume that it's an
> EUI assigned to the device under IEEE rules, and similarly for RFID
> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
> I'm
> guessing that the DUID is one that is, or could be, used by the
> device
> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
> the IPv6 architecture doesn't assume that the association of
> addresses
> with devices is permanent.

I hope that this document does not have to specify allocation procedures 
for the MNIDs.  It seems to me that if a system designer wants to use 
one of the MNID types, that person will already know about how to 
request the allocation and would not need to rely on the MNIDs document 
for that information.  Plus it's really out of scope.  This document was 
always intended to be a simple tabulation of types already in use 
elsewhere and enabling IETF mobility management protocols to use the 
most natural identifier available for a mobile node.  I hope that citing 
the defining documents for the identifier types will be enough to 
satisfy that.

>
> 4.1.  Description of the IPv6 address type
>
> It would be good if the document described what the semantics of this
> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
> between that address and the device?  I suspect the connection is
> "the
> device has been configured to expect that it will be assigned this
> address as a long-term interface address", but there are other
> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
> prefix (there are plenty of them!) and then assigning addresses out
> of
> it simply to create a sequence of unique identifiers for devices, but
> not using those addresses on packets.
>
> Then again, perhaps you want to allow flexibility.  But in any case,
> I
> think you need to specify what the rules are for what address is
> associated with what device.

As far as I have understood, the unicast IPv6 address in use as a MNID 
is already assigned to the device.  I have not heard anyone asking for 
this to be an address for future assignment.  I'll try to make that 
clear in the text.

>
> 4.2.  Description of the IMSI MNID type
>
> What does "in network order" mean here?  As far as I know, there is
> no
> defined "network order" for 4-bit quantities, only for dividing
> integers into octets and placing sequences of bits into octets.  I
> assume you mean that in any octet, the high-order 4 bits are the
> first
> digit and the low-order 4 bits are the second digit, but I think you
> need to state that explicitly.

I probably lifted that language directly from the IMSI spec, but I can 
make further clarification according to your suggestion.

>
> 4.3.  Description of the EUI-48 address type
>
>     The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>     string containing the IEEE EUI-48 address.
>
> Is "string" the correct word, this not being a sequence of
> characters?
> I would say "sequence of 6 octets" or simply "encoded as 6 octets".

O.K.  I also lifted that language from elsewhere.
>
> 4.9.  Description of the RFID types
>
> This section needs to be revised.  It provides a lot of detail about
> the RFID types, but it's not enough detail for a reader who doesn't
> understand RFID to learn how any particular RFID scheme works.  E.g.,
> the first paragraph says that GID contains three fields in the first
> sentence, and that it contains four fields in the third sentence.
> Despite this, the description isn't enough to allow the reader to
> construct GID identifiers manually.
>
> On the other hand, readers who already understand the RFID schemes
> will find this text redundant.
>
> I think that almost all of this text can be replaced by references to
> the EPC documents, since these identifiers are opaque from the point
> of view of mobile identification.

Here I am at a loss, because I was specifically requested to insert some 
descriptive but not normative text.  I will ask the person who made the 
request to provide their feedback on the mailing list.  For myself, I am 
more than happy to delete the text.

>
> 5.  Security Considerations
>
> The base MNID specification, RFC 4283, gives these security
> considerations (sec 4), which ought to be referenced and probably
> summarized in this section:
>
>     Moreover, MNIDs containing sensitive identifiers might only be
> used
>     for signaling during initial network entry.  Subsequent binding
>     update exchanges might then rely on a temporary identifier
> allocated
>     during the initial network entry, perhaps using mechanisms not
>     standardized within the IETF.  Managing the association between
> long-
>     lived and temporary identifiers is outside the scope of this
>     document.
>
> What is the meaning of the word "might" in paragraph 3?  I suspect
> that the purpose is to qualify this paragraph with "One way to
> address
> these vulnerabilities is to only use MNIDs containing ...".  But if
> that is the meaning, that expanded wording should be used.  Otherwise
> the text reads as if it is hypothetical.

This text was meant to be generally descriptive, so that people wanting 
to include the Mobile Node Identifier Option with the relevant MNIDs 
could understand how the identifiers are actually used in various 
circumstances.  I could replace constructions using "might" with "in 
some specifications" or "in some situations" if needed.  Is it also 
necessary to include citations to the relevant documents of the external 
SDO?


Regards,
Charlie P.


--------------34D9108758E61C1C73F50279
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hello Dale,</p>
    <p>Thanks for the thorough review.  My follow-up comments are inline
      below.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 1/31/2017 11:34 AM, Dale Worley
      wrote:<br>
    </div>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
1. The Introduction states

   Other types of identifiers are in
   common use, and even referenced in RFC 4283.

For the reader's sanity, some sort of accounting needs to be made of
these "other types of identifiers", especially because each type of
identifier needs an identifier type number.  The text in 4283 is

   Some examples of identifiers
   include Network Access Identifier (NAI), Fully Qualified Domain
Name
   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
   Subscriber Number (MSISDN).

Are there any other types "in common use"?</pre>
    </blockquote>
    <br>
    I will add some text according to your suggestion.  My criterion for
    whether the identifier type was included in the document was whether
    or not anyone had asked for it to be included.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

- NAI (type 1) is defined by 4283.
- Fully Qualified Domain Name (FQDN) seems not to be specified
- International Mobile Station Identifier (IMSI) (type 3) is defined
in
  this draft
- Mobile Subscriber Number (MSISDN) seems not to be specified</pre>
    </blockquote>
    <br>
    It is not the jurisdiction of the MNIDs document to specify these
    identifiers, but citations for the specifications are located
    elsewhere in the document.  I will also include those citations
    here.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

2. Is it intended to have an IMEI identifier type?  The introduction
mentions an IMEI type, but there is no specification for it, nor is
there an identifier type number assigned for it.

   ... types for IMSI
   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
GUTI
   [ThreeGPP-IDS].

Initially I suspected it was it was present in an earlier revision
and
then later deleted without this reference being updated.  But all
versions of draft-ietf-dmm-4283mnids and its predecessor
draft-perkins-dmm-4283mnids mention IMEI in this way as one
identifier
type, but none specify it in any way.  The only discussion I can find
on the DMM mailing list of IMEI is:

   
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af">https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af</a>

    From: Marco Liebsch <a class="moz-txt-link-rfc2396E" href="mailto:Marco.Liebsch@neclab.eu">&lt;Marco.Liebsch@neclab.eu&gt;</a>
    To: DMM
    Date: Wed, 10 September 2014 13:29 UTC
    Re: [DMM] regarding the re-chartering..

    It seems the MNID is somehow overloaded to carry both,
node-specific
    IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
    There may be value in adding the IMEI to the list of possible
types of
    node-specific IDs. 

Either the presence of IMEI in this list is a simple mistake that has
persisted in all versions of the draft, or specifying IMEI has always
been intended but has always been overlooked.</pre>
    </blockquote>
    <br>
    I don't know why this happened, but I am happy to include an
    identifier type for IMEI as well as a citation for it.  Thanks for
    catching this and looking through the archives!<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

3. The definition of identifier types for both EUI-48 and EUI-64
suggests that it might be desirable to define an identifier type for
arbitrary hardware (link-level) addresses.  It seems that the natural
differentiator for that purpose is the "hardware type" used in ARP,
so
a EUI-48 address would be represented as

    MN identifier type (one octet) 5 (say)
    hardware type (two octets) 1
    EUI-48 (six octets)

and an EUI-64 similarly, with hardware type 27.

Although with only two subtypes in common use, generalizing this
might
not be worth the effort.</pre>
    </blockquote>
    <br>
    Actually, I am O.K. either way on this matter.  However, at this
    point in time it does not seem that we are likely to see any other
    link hardware address types to be used as MNIDs.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4. Several of the identifier types can be represented as URNs:

- IMEI can be represented as a URN as urn:gsma:imei:...
- all of the RFID types have a URN representation (called the
  "pure-identity URI" in the RFID specifications), which starts
  urn:epc:id:...

Since all URN types are ensured of being unique and persistent, it
seems that we could define a MNID type for URNs generally, and then
any RFID URI or an IMEI (as a URN) could be used as a value of that
type.

If this idea is adopted, it seems that the other 3GPP types (IMSI,
P-TMSI, and GUTI) should be given defined encodings as URNs in new
sub-namespaces of the "gsma" URN namespace, to parallel the encoding
of IMEIs defined in RFC 7254.

This consolidation could be significantly beneficial.  It allows MNID
to use any URN scheme as an identifier.  It reduces the three
different RFID representations to one.  It incorporates any future
expansion of RFID schemes (because all schemes will have a
pure-identity URN representation).  A disadvantage is that the URN
encodings are long, but the security considerations section states
that MNIDs are used only on the first registration at the home agent,
so there isn't much need for brevity.

Similarly, this approach incorporates any future expansion of mobile
identifiers that GSMA decides to define, as long as GSMA provides a
URN representation for it.

The most significant disadvantage is that some URN schemes allow
several character strings to "mean" the same URN.  In most URN
schemes, the allowed variation is limited to the case of letters, and
the common convention is to always use lower-case when there is a
choice, leading to a unique conventional canonical form for the URN.</pre>
    </blockquote>
    <br>
    There is a sort of "hidden" disadvantage to long names, especially
    for tiny devices using constrained link layers.  Namely, a longer
    name makes it more likely to require lower-layer fragmentation.  I'm
    not sure that it should be the job of a layer-3 mobility entity to
    parse URNs and determine if two different flavors are supposed to be
    equivalent.<br>
    <br>
    Other than that, I don't have any real objection to reorganizing the
    namespace, but I'd like some additional confirmation that it's a
    good idea.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

5. Regarding the encoding of a string of digits into octets, it is
stated that "The last digit MUST be zero padded, if needed, for full
octet size."  This seems very unwise unless there is a 3GPP decree
that if a zero is appended to a valid IMSI, the resulting string is
never a valid IMSI.  Instead, I would specify that padding is by
filling the low-order 4 bits of the final octet with 0xF.  That
ensures that the encoding can be uniquely decoded into an IMSI.</pre>
    </blockquote>
    <br>
    I am O.K. with this.  I need to go find out where I got that
    language from, because I don't think I was the person who crafted
    it.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

6. There are four types of DUID specified, each with a distinct MNID
value.  However, DUIDs contain an initial two-octet type field which
distinguishes the various types of DUID, so providing them with
distinct MNID values is redundant.

Distinguishing the types and allowing only four of them to be used as
MNIDs seems to be contrary to the philosophy of DUID construction
(RFC
3315 section 9):

   Clients and servers MUST treat DUIDs as opaque values and MUST
only
   compare DUIDs for equality.  Clients and servers MUST NOT in any
   other way interpret DUIDs.  Clients and servers MUST NOT restrict
   DUIDs to the types defined in this document, as additional DUID
types
   may be defined in the future.

Of course, MNID isn't a DHCP operation, so it isn't subject to those
requirements, but I expect that devices will use the same DUID for
both mobile identification, and we don't want mobile identification
to
restrict future developments of DHCP.

I think this specification must treat DUIDs as opaque and use only
one
MNID type that allows all types of DUIDs as values.</pre>
    </blockquote>
    <br>
    Thanks for this observation.  I will make the corresponding
    revisions to the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

Editorial issues:

Abstract

   Additional Identifier Types are proposed for use with the Mobile
Node
   Identifier Option for IPv6 (RFC 4283).

s/proposed/defined/
This document will define the new types (once it is approved)!</pre>
    </blockquote>
    <br>
    O.K. with your modification.  The document just defines numbers for
    the types, not the types.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

1.  Introduction

   ... types for IMSI
   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
GUTI
   [ThreeGPP-IDS].

There is no description of P-TMSI identifiers, although it is
assigned
identifier type 4.

There is no description of GUTI identifiers, although it is assigned
identifier type 7.</pre>
    </blockquote>
    <br>
    I will insert text from the relevant 3GPP documents to describe
    these identifiers.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

3.  New Mobile Node Identifier Types

   The following types of identifiers are commonly used to identify
   mobile nodes.  For each type, references are provided with full
   details on the format of the type of identifier.

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   including

   o  RFID-GID (Global Identifier),
   o  RFID-SGTIN (Serialized Global Trade Item Number),
   o  RFID-SSCC (Serial Shipping Container),
   o  RFID-SGLN (Global Location Number),
   o  RFID-GRAI (Global Returnable Asset Identifier),
   o  RFID-DOD (Department of Defense ID), and
   o  RFID-GIAI (Global Individual Asset Identifier).

   For each RFID scheme except GID, there are two variations: a
64-bit
   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
has
   only a 96-bit scheme.  Within each scheme, an EPC identifier can
be
   represented in a binary form or other forms such as URI.

   The following list includes the above RFID types as well as
various
   other common identifiers and several different types of DUIDs.

The organization of the text here seems to be poor -- section 3
enumerates the new identifier types, but much of the text at the
beginning of the section is about the RFID-EPC set of types.  It
seems
like a better organization is to use just paragraph 1 followed by
table 1, and move paragraphs 2-5 into section 4.9.</pre>
    </blockquote>
    <br>
    O.K.  Thanks for the suggestion.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   including

The text is using "Tag Data", "EPC", and "RFID" in a way that is
intertwined but not explained.  I can see that it might be useful to
use all of the terms if they commonly used in the field (don't forget
to make them keywords for the RFC!), but you need to explain their
connection and distinction to the reader or make it clear that the
reader does not need to understand the differences among the terms.
E.g., this formulation ties all three terms together

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   which are commonly used in RFID (radio-frequency identification)
   applications, including</pre>
    </blockquote>
    <br>
    Thanks for the text.  I will use it.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">--

   For each RFID scheme except GID, there are two variations: a
64-bit
   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
has
   only a 96-bit scheme.  Within each scheme, an EPC identifier can
be
   represented in a binary form or other forms such as URI.

The text uses "scheme" to mean the distinction between encoding
systems (GID, SGTIN, etc.) and and also to mean the distinction
between the 64-bit and 96-bit variations.  This ambiguity is unwise.
It matters here, because you say "within each scheme ... can be
represented in a binary form or ... URI".  Which meaning of "scheme"
are you using here?  I thought you meant the second meaning when I
first read the paragraph, but after reading external documents about
EPC, I now understand that that last sentence uses "scheme" to in the
first sense.

You need to be clearer here that there are three representations
used,
64-bit binary, 96-bit binary, and URI (URN, actually), and
representation is orthogonal to the seven RFID schemes, with the
exception that RFID-GID does not have a 96-bit binary representation.</pre>
    </blockquote>
    <br>
    This is a good idea.  How about the following:<br>
    <br>
    <blockquote type="cite">   For each RFID scheme except GID, there
      are three representations:<br>
          - a 64-bit binary representation (for example, SGLN-64)<br>
          - a 96-bit binary representation (SGLN-96).<br>
          - a representation as a URI</blockquote>
    <br>
    I didn't originate the use of URI for the non-binary representation.
    The EPC document has the following language:<br>
    <br>
    <blockquote type="cite">
      <div style="left: 520.439px; top: 898.022px; font-size: 18.6471px;
        font-family: serif; transform: scaleX(0.99895);">
        <p>All categories of URIs are represented as Uniform Reference
          Names (<span class="highlight selected">URN</span>s) as
          defined by [RFC2141], where the URN Namespace is   <tt>epc</tt>.
        </p>
      </div>
    </blockquote>
    <br>
    If I were to change it to URN, then I would have to go into some
    detail about why this document somehow disagrees with the
    EPC-Tag-Data document.  Do you think that is necessary? <br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

I'm assuming that the Tag Data standard unambiguously defines the
serialization of the binary representations as a sequence of octets.
If it does not, this document MUST do that, or you will have an
endless nightmare of byte-order problems.</pre>
    </blockquote>
    <br>
    I read through some relevant text in the EPC-Tag-Data document and
    it seems O.K. to me, but nontrivial and it relies on digging through
    other even more arcane documents to be absolutely sure.  I am pretty
    sure that the IETF document should not get into the business of
    augmenting the standards already in place from the external SDOs.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.  Descriptions of MNID types

Identifier ownership is a general concern -- it's worth mentioning
for
each type of identifier where the assigner of the identifier obtains
delegation.  For an EUI, I expect the reader will assume that it's an
EUI assigned to the device under IEEE rules, and similarly for RFID
and 3GPP identifiers.  But for DUID identifiers, it's less clear. 
I'm
guessing that the DUID is one that is, or could be, used by the
device
for DHCP purposes.  For IPv6 addresses, it's even less clear, since
the IPv6 architecture doesn't assume that the association of
addresses
with devices is permanent.</pre>
    </blockquote>
    <br>
    I hope that this document does not have to specify allocation
    procedures for the MNIDs.  It seems to me that if a system designer
    wants to use one of the MNID types, that person will already know
    about how to request the allocation and would not need to rely on
    the MNIDs document for that information.  Plus it's really out of
    scope.  This document was always intended to be a simple tabulation
    of types already in use elsewhere and enabling IETF mobility
    management protocols to use the most natural identifier available
    for a mobile node.  I hope that citing the defining documents for
    the identifier types will be enough to satisfy that.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.1.  Description of the IPv6 address type

It would be good if the document described what the semantics of this
ID are.  Yes, it's a unicast IPv6 address, but what is the connection
between that address and the device?  I suspect the connection is
"the
device has been configured to expect that it will be assigned this
address as a long-term interface address", but there are other
possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
prefix (there are plenty of them!) and then assigning addresses out
of
it simply to create a sequence of unique identifiers for devices, but
not using those addresses on packets.

Then again, perhaps you want to allow flexibility.  But in any case,
I
think you need to specify what the rules are for what address is
associated with what device.</pre>
    </blockquote>
    <br>
    As far as I have understood, the unicast IPv6 address in use as a
    MNID is already assigned to the device.  I have not heard anyone
    asking for this to be an address for future assignment.  I'll try to
    make that clear in the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.2.  Description of the IMSI MNID type

What does "in network order" mean here?  As far as I know, there is
no
defined "network order" for 4-bit quantities, only for dividing
integers into octets and placing sequences of bits into octets.  I
assume you mean that in any octet, the high-order 4 bits are the
first
digit and the low-order 4 bits are the second digit, but I think you
need to state that explicitly.</pre>
    </blockquote>
    <br>
    I probably lifted that language directly from the IMSI spec, but I
    can make further clarification according to your suggestion.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.3.  Description of the EUI-48 address type

   The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
   string containing the IEEE EUI-48 address.

Is "string" the correct word, this not being a sequence of
characters?
I would say "sequence of 6 octets" or simply "encoded as 6 octets".</pre>
    </blockquote>
    <br>
    O.K.  I also lifted that language from elsewhere.<br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.</pre>
    </blockquote>
    <br>
    Here I am at a loss, because I was specifically requested to insert
    some descriptive but not normative text.  I will ask the person who
    made the request to provide their feedback on the mailing list.  For
    myself, I am more than happy to delete the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

5.  Security Considerations

The base MNID specification, RFC 4283, gives these security
considerations (sec 4), which ought to be referenced and probably
summarized in this section:

   Moreover, MNIDs containing sensitive identifiers might only be
used
   for signaling during initial network entry.  Subsequent binding
   update exchanges might then rely on a temporary identifier
allocated
   during the initial network entry, perhaps using mechanisms not
   standardized within the IETF.  Managing the association between
long-
   lived and temporary identifiers is outside the scope of this
   document.

What is the meaning of the word "might" in paragraph 3?  I suspect
that the purpose is to qualify this paragraph with "One way to
address
these vulnerabilities is to only use MNIDs containing ...".  But if
that is the meaning, that expanded wording should be used.  Otherwise
the text reads as if it is hypothetical.</pre>
    </blockquote>
    <br>
    This text was meant to be generally descriptive, so that people
    wanting to include the Mobile Node Identifier Option with the
    relevant MNIDs could understand how the identifiers are actually
    used in various circumstances.  I could replace constructions using
    "might" with "in some specifications" or "in some situations" if
    needed.  Is it also necessary to include citations to the relevant
    documents of the external SDO?<br>
    <br>
    <br>
    Regards,<br>
    Charlie P.<br>
    <br>
  </body>
</html>

--------------34D9108758E61C1C73F50279--


From nobody Fri Feb 10 15:06:11 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 863E412A069; Fri, 10 Feb 2017 15:06:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148676797054.29317.17761463000129345942.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 15:06:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/15yt3UUDs_8FVFNf818B3EM6t1M>
Cc: draft-ietf-mmusic-sctp-sdp.all@ietf.org, mmusic@ietf.org
Subject: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 23:06:10 -0000

Reviewer: Brian Carpenter
Review result: Ready

Gen-ART telechat review of draft-ietf-mmusic-sctp-sdp-23

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-mmusic-sctp-sdp-23.txt
Reviewer: Brian Carpenter
Review Date: 2017-02-11
IETF LC End Date: 2017-02-09
IESG Telechat date: 2017-02-16

Summary: Ready
--------

Comment:
--------

Thanks for handling my Last Call comments.

Nit:
----

Thanks for the IPv6 example. But RFC5952 recommends 
lower case as the canonical form: 2001:db8::a8fd


From nobody Fri Feb 10 15:24:07 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2962712A060; Fri, 10 Feb 2017 15:24:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 15:24:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nVPjLHJ_rT_eEsR86awLRdv02OA>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, ccamp@ietf.org
Subject: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 23:24:06 -0000

Reviewer: Pete Resnick
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ccamp-flexible-grid-ospf-ext-08
Reviewer: Pete Resnick
Review Date: 2017-02-10
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-02-16

Summary: Ready with Nits

A couple of nits that I mentioned in my earlier review that you might
want to address, but none of them are essential. (You may have decided
that I was wrong; that's OK too.) I didn't bother Cc'ing the IETF list
on this, since they're both very minor.

Major issues: None

Minor issues: None

Nits/editorial comments: 

3.1:

   A set of non-overlapping available frequency ranges MUST be 
   disseminated in order to allow efficient resource management of 
   flexi-grid DWDM links and RSA procedures which are described in 
   Section 4.8 of [RFC7698]. 

Those MUSTs look weird to me. I think instead of "MUST be" you mean
"are", since it doesn't look like an implementation really has a
choice here.

3.2:

   Hence, in order to support all possible applications and 
   implementations the following information should be advertised for
   a flexi-grid DWDM link:
   
Is that "should" in there meant to be normative? That is, do bad
things happen if I don't advertise one of those items? Or do you just
mean "the following information is advertised..."? 




From nobody Fri Feb 10 20:29:23 2017
Return-Path: <heard@pobox.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C631296C7; Fri, 10 Feb 2017 20:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5Qaokb2pXGX; Fri, 10 Feb 2017 20:29:17 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A79771296C5; Fri, 10 Feb 2017 20:29:17 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 0EA2568668; Fri, 10 Feb 2017 23:29:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=J7x pklY1odrNjGqVtYjz9B4uWZY=; b=yXaBLrCPnxLafx7D0qum3k4NbB8+xyx7iEz 00imc1/3MTaNr3bcUq02dfnDzEMOdyxbjLuWZiGp4yb3b4fEtmXVNUikXp59fIV0 vUPAYFrx6q8UJYHIUc34hr9PNn6SEZGLbcN1P2Mp14BWtR558buoJY7tKuDDQsfk Ib5UGjoY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= smNhL4F9gBpktzecOhqVX2/Y/pcw8ZnrULbK3OzIXeZHwMIv5jNzwV9JbH7WPbpF gw3wimCUVKgp4KhiA/bAN+PN+TKoI56z7iZnLsCdQEprXP/FaPOe57K398AG4hVF BrjS0x+IeYwf4FwJT/gRD6T8FkIvXGtT/uCnmLcZmeY=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 047F168667; Fri, 10 Feb 2017 23:29:16 -0500 (EST)
Received: from mail-qk0-f169.google.com (unknown [209.85.220.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 6C89868664; Fri, 10 Feb 2017 23:29:15 -0500 (EST)
Received: by mail-qk0-f169.google.com with SMTP id 11so58490805qkl.3; Fri, 10 Feb 2017 20:29:15 -0800 (PST)
X-Gm-Message-State: AMke39lwbW0OzJwPBXJ578D/czmoj6CgBusemGyn2JSypeqMnxPbF/2P4Vy6/W3vgl9MqZsHq+UyKUG6dqBVGg==
X-Received: by 10.55.119.1 with SMTP id s1mr12786187qkc.81.1486787354703; Fri, 10 Feb 2017 20:29:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Fri, 10 Feb 2017 20:28:54 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Fri, 10 Feb 2017 20:28:54 -0800
X-Gmail-Original-Message-ID: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
Message-ID: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: A54B2766-F012-11E6-98C3-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/wtJpdGfQzC9HwrMqS1DB_Sn0Yck>
Cc: Stewart Bryant <stewart@g3ysx.org.uk>, Gen-ART <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 04:29:19 -0000

On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> On 10/02/2017 23:20, Stewart Bryant wrote:
> > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > I wonder if we would best serve both our future and our heritage
> > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > or declared it as historic and wrote a new text from a clean start?
> > >
> > > I don't see that. It's a stable, widely deployed, interoperable
> > > mechanism. That is rather orthogonal to the issue that has been raised,
> > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > across the Internet.
> >
> > I will not debate whether it is faulty or not,
>
> It's faulty by the standard of RFC4890 (which is Informational).
>
> > but it seems that in practice the Internet breaks the mechanism.
> > However it breaks it is a way that seems disruptive to some user
> > traffic. The document is really guidance one how hosts might use
> > ICMP for optimization, and arguabl[y] need not be a standard at all.
>
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes.

Actually, no. You do not have to use PMTUD to avoid black holes.
Other options include:

- Send packets no larger than 1280 bytes (this is always an option)
- Use PLPMTUD (for transports that do their own packetization and
  that can detect packet loss)

> > My remark about heritage is that this vintage draft is very much a
> > product of its time, and really needs modernizing, and after
> > modernizing ought to look quite different, and thus maybe we
> > should employ a procedure other than a simple replacement.

I am afraid that I have to agree with this. Classic PMTUD by itself
is today not enough, but it can be a very useful optimization to
augment other techniques.

> It's proposed for Internet Standard. That means it must replace the
> PS document and must specify the same thing, plus corrections,
> minus unused features.

All true, and my conclusion is that is it should not be promoted to IS.
I would have no problem with republishing at PS to correct the errata
and aid the eventual advance of RFC 4821 (PLPMTUD).

If this document does go forward, the words in Appendix B (Changes
Since RFC 1981) relating to RFC 4821 should be removed, since
there was no mention of RFC 4821 in RFC 1981.

Mike Heard


From nobody Fri Feb 10 21:26:23 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECFBB129420; Fri, 10 Feb 2017 21:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkQOAT399ruC; Fri, 10 Feb 2017 21:26:20 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D17B91293E8; Fri, 10 Feb 2017 21:26:19 -0800 (PST)
X-AuditID: c1b4fb30-b99fe70000007389-56-589ea0781ab2
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 58.75.29577.870AE985; Sat, 11 Feb 2017 06:26:17 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Sat, 11 Feb 2017 06:26:16 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Review of draft-ietf-mmusic-sctp-sdp-23
Thread-Index: AQHSg/JG+PDZpBijwkuorCJaK5ShS6FjRtZ7
Date: Sat, 11 Feb 2017 05:26:15 +0000
Message-ID: <9007DD69-14A7-4B15-9F2C-A8CB0223E817@ericsson.com>
References: <148676797054.29317.17761463000129345942.idtracker@ietfa.amsl.com>
In-Reply-To: <148676797054.29317.17761463000129345942.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2J7oG7lgnkRBvffWlm0XdzHZLGpfxOL xdVXn1kspi5/zOLA4rFz1l12jyVLfjIFMEVx2aSk5mSWpRbp2yVwZXSsvsxeMIWzYmnvTvYG xlXsXYycHBICJhLzFzQwdTFycQgJrGOUOPbuNBuEs5hR4lr7NqAMBwebgIVE9z9tkAYRAUOJ /08/M4LUMAusZJS4eOc2E0hCGGhS55GbzBBFphJb+uexQ9hGEvcmLwerYRFQlWh7dAWshlfA XmJj1wU2EFtIwE9i6YyXYDWcAv4SK1dsZwSxGQXEJL6fWgMWZxYQl7j1ZD4TxNUCEkv2nGeG sEUlXj7+xwpRoyOxYPcnNghbW2LZwtdQuwQlTs58wjKBUWQWklGzkLTMQtIyC0nLAkaWVYyi xanFSbnpRkZ6qUWZycXF+Xl6eaklmxiBUXJwy2+DHYwvnzseYhTgYFTi4S24OjdCiDWxrLgy 9xCjBAezkgjvjunzIoR4UxIrq1KL8uOLSnNSiw8xSnOwKInzmq28Hy4kkJ5YkpqdmlqQWgST ZeLglGpgDOex8DydvNDSgF+r980c7/7bx2PyTJLXhsqyJ0tVOj2ovqxRX8B89ti7HZXr+U/x PjrCeJX/aHvDEtNpqtL7rWKrPydqPpG7zfA7uu/6ufyTc1hte9LtVwZUns1ymdXvcn7exi1f 7d5MYrqTMsdefJ2V/Imd8+Tfft/Fla0bfu9B3O0It5NflFiKMxINtZiLihMBL9nmZo4CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/HxhniZ1ADID435tR4htLSU5a3S8>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 05:26:22 -0000

Hi Brian,

I will fix the case in the next version.

Thanks!=20

Regards,

Christer=20



Sent from my iPhone

> On 11 Feb 2017, at 1.06, Brian Carpenter <brian.e.carpenter@gmail.com> wr=
ote:
>=20
> Reviewer: Brian Carpenter
> Review result: Ready
>=20
> Gen-ART telechat review of draft-ietf-mmusic-sctp-sdp-23
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-mmusic-sctp-sdp-23.txt
> Reviewer: Brian Carpenter
> Review Date: 2017-02-11
> IETF LC End Date: 2017-02-09
> IESG Telechat date: 2017-02-16
>=20
> Summary: Ready
> --------
>=20
> Comment:
> --------
>=20
> Thanks for handling my Last Call comments.
>=20
> Nit:
> ----
>=20
> Thanks for the IPv6 example. But RFC5952 recommends=20
> lower case as the canonical form: 2001:db8::a8fd
>=20


From nobody Fri Feb 10 22:42:49 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B77681294AD; Fri, 10 Feb 2017 22:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7RJZAQS5Ouw; Fri, 10 Feb 2017 22:42:46 -0800 (PST)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E20E127601; Fri, 10 Feb 2017 22:42:45 -0800 (PST)
Received: by mail-vk0-x229.google.com with SMTP id k127so39066542vke.0; Fri, 10 Feb 2017 22:42:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OVjo0u3qVPxNT/T53/VeGKf8JIGySnqBdG62iqs+J74=; b=Eu7grB2SCiiDM0Ed+x2HDbGy7avzpb5sMeFvDgvWkT7dO+CkqWqsDkXUOFYErb1NBN q753ZqU3R86ypQ03vXnGU1NTtmupD4hhQwQ8Zo1ct/KO+2nE4DkxjHoEp3TmdLNPstP+ 6t6FLLvwDT5BaCVrSpRi/QDtYv0J7wEGOLXNUw0IIlJ1ddcT+EHII2SwuzT4M0qAbm5V vxyJ2IrI5bqRlIi41BHmuJufgbXTGGKkCjQylKcMRyT4jj+LM6pqE/OxI3miwLh1Yy4J 79YVnnPi5kFnJaplOqhASVjsS22TVpObeisQGR0W8IYHvoOKTX5bSWuxpMcz1e3hLHxs HqZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OVjo0u3qVPxNT/T53/VeGKf8JIGySnqBdG62iqs+J74=; b=UPJWFI48C/3RdRSF2ZvxlzMaTcsBQ5Z/9FbCpMlOCk25DLK9hNCMgSBXtLWPhkNPhH l7H1kUjPFqPkQjWITlbbHW42Ffn6HuOr8eJGSIJCXvBDV28klKKhSbOUUCSYHo2VrLfv jzYci1hG6uXiMLOoKKzZf8aDcIsOx75ki62GeVFXKxDy1zTr/SyXiO3iHqRXk0/bu2FT XnRMI7AmdLoFDAgREGhe6AYoyefvKYQex73+cu8hYoau/t1go27IsBmJCarodB0Xrosp FzlSCvMSNpT6Dn3COrgAFaAQnJWz7bc9WymyY7dsbmH7Xd6F/KRZBneuOFCbUDPsR5uG uN1w==
X-Gm-Message-State: AMke39kZxCu3ENJxge8ivqEuG8TaNFeOCRR7LtRRYh5v5bCPmf1uPshcxP5UIEu8S+Ey1Wigy36gn3GF8havcQ==
X-Received: by 10.31.128.78 with SMTP id b75mr6185594vkd.174.1486795364824; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
In-Reply-To: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
References: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Sat, 11 Feb 2017 01:42:44 -0500
Message-ID: <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
Content-Type: multipart/alternative; boundary=001a1142a40492fece05483b8561
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/JzvbvYiKowI4dWraSpK-0NOa3Co>
Cc: 6man WG <ipv6@ietf.org>, gen-art@ietf.org, Stewart Bryant <stewart@g3ysx.org.uk>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 06:42:48 -0000

--001a1142a40492fece05483b8561
Content-Type: text/plain; charset=UTF-8

Hi Mike,

On Feb 10, 2017 11:30 PM, "C. M. Heard" <heard@pobox.com> wrote:

On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> On 10/02/2017 23:20, Stewart Bryant wrote:
> > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > I wonder if we would best serve both our future and our heritage
> > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > or declared it as historic and wrote a new text from a clean start?
> > >
> > > I don't see that. It's a stable, widely deployed, interoperable
> > > mechanism. That is rather orthogonal to the issue that has been
raised,
> > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > across the Internet.
> >
> > I will not debate whether it is faulty or not,
>
> It's faulty by the standard of RFC4890 (which is Informational).
>
> > but it seems that in practice the Internet breaks the mechanism.
> > However it breaks it is a way that seems disruptive to some user
> > traffic. The document is really guidance one how hosts might use
> > ICMP for optimization, and arguabl[y] need not be a standard at all.
>
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes.

Actually, no. You do not have to use PMTUD to avoid black holes.
Other options include:

- Send packets no larger than 1280 bytes (this is always an option)
- Use PLPMTUD (for transports that do their own packetization and
  that can detect packet loss)


How does this work for UDP?


> > My remark about heritage is that this vintage draft is very much a
> > product of its time, and really needs modernizing, and after
> > modernizing ought to look quite different, and thus maybe we
> > should employ a procedure other than a simple replacement.

I am afraid that I have to agree with this. Classic PMTUD by itself
is today not enough, but it can be a very useful optimization to
augment other techniques.


OK.


> It's proposed for Internet Standard. That means it must replace the
> PS document and must specify the same thing, plus corrections,
> minus unused features.

All true, and my conclusion is that is it should not be promoted to IS.


What criteria for advancement to IS do you think are not met by this
document?

I would have no problem with republishing at PS to correct the errata
and aid the eventual advance of RFC 4821 (PLPMTUD).

If this document does go forward, the words in Appendix B (Changes
Since RFC 1981) relating to RFC 4821 should be removed, since
there was no mention of RFC 4821 in RFC 1981.


Not sure I understand your concern. This is a change log since RFC1981. And
it is a fact that the reference to RFC4821 was added into this draft. Can
you clarify?

Thanks
Suresh

--001a1142a40492fece05483b8561
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi Mike,=C2=A0<br><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Feb 10, 2017 11:30 PM, &quot;C. M. Heard&quot; &=
lt;<a href=3D"mailto:heard@pobox.com">heard@pobox.com</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">On Fr=
i, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:<br>
&gt; On 10/02/2017 23:20, Stewart Bryant wrote:<br>
&gt; &gt; On 10/02/2017 03:25, Brian E Carpenter wrote:<br>
</div><div class=3D"quoted-text">&gt; &gt; &gt; On 10/02/2017 04:19, Stewar=
t Bryant wrote:<br>
</div><div class=3D"quoted-text">&gt; &gt; &gt; &gt; I wonder if we would b=
est serve both our future and our heritage<br>
&gt; &gt; &gt; &gt; if we declared RFC1981 as historic, and either left the=
 idea there,<br>
&gt; &gt; &gt; &gt; or declared it as historic and wrote a new text from a =
clean start?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don&#39;t see that. It&#39;s a stable, widely deployed, in=
teroperable<br>
&gt; &gt; &gt; mechanism. That is rather orthogonal to the issue that has b=
een raised,<br>
&gt; &gt; &gt; which is that faulty ICMPv6 filtering blocks it on many, man=
y paths<br>
&gt; &gt; &gt; across the Internet.<br>
&gt; &gt;<br>
&gt; &gt; I will not debate whether it is faulty or not,<br>
&gt;<br>
</div><div class=3D"quoted-text">&gt; It&#39;s faulty by the standard of RF=
C4890 (which is Informational).<br>
&gt;<br>
</div>&gt; &gt; but it seems that in practice the Internet breaks the mecha=
nism.<br>
<div class=3D"quoted-text">&gt; &gt; However it breaks it is a way that see=
ms disruptive to some user<br>
&gt; &gt; traffic. The document is really guidance one how hosts might use<=
br>
</div>&gt; &gt; ICMP for optimization, and arguabl[y] need not be a standar=
d at all.<br>
<div class=3D"quoted-text">&gt;<br>
&gt; I think that&#39;s a mischaracterisation of the mechanism (and the dra=
ft).<br>
&gt; PMTUD is not an optimisation. Without it, you get black holes.<br>
<br>
</div>Actually, no. You do not have to use PMTUD to avoid black holes.<br>
Other options include:<br>
<br>
- Send packets no larger than 1280 bytes (this is always an option)<br>
- Use PLPMTUD (for transports that do their own packetization and<br>
=C2=A0 that can detect packet loss)<br></blockquote></div></div></div><div =
dir=3D"auto"><br></div><div dir=3D"auto">How does this work for UDP?=C2=A0<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"quoted-text"><br>
&gt; &gt; My remark about heritage is that this vintage draft is very much =
a<br>
&gt; &gt; product of its time, and really needs modernizing, and after<br>
&gt; &gt; modernizing ought to look quite different, and thus maybe we<br>
&gt; &gt; should employ a procedure other than a simple replacement.<br>
<br>
</div>I am afraid that I have to agree with this. Classic PMTUD by itself<b=
r>
is today not enough, but it can be a very useful optimization to<br>
augment other techniques.<br></blockquote></div></div></div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">OK.=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<div class=3D"quoted-text"><br>
&gt; It&#39;s proposed for Internet Standard. That means it must replace th=
e<br>
&gt; PS document and must specify the same thing, plus corrections,<br>
&gt; minus unused features.<br>
<br>
</div>All true, and my conclusion is that is it should not be promoted to I=
S.<br></blockquote></div></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">What criteria for advancement to IS do you think are not met by t=
his document?=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would have no problem with republishing at PS to correct the errata<br>
and aid the eventual advance of RFC 4821 (PLPMTUD).<br>
<br>
If this document does go forward, the words in Appendix B (Changes<br>
Since RFC 1981) relating to RFC 4821 should be removed, since<br>
there was no mention of RFC 4821 in RFC 1981.<br></blockquote></div></div><=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">Not sure I understand yo=
ur concern. This is a change log since RFC1981. And it is a fact that the r=
eference to RFC4821 was added into this draft. Can you clarify?=C2=A0</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Thanks=C2=A0</div><div dir=3D=
"auto">Suresh</div><div dir=3D"auto"><div class=3D"gmail_extra"><br></div><=
/div></div>

--001a1142a40492fece05483b8561--


From nobody Sat Feb 11 10:05:40 2017
Return-Path: <heard@pobox.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE353129A34; Sat, 11 Feb 2017 10:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEuPaTY-epPa; Sat, 11 Feb 2017 10:05:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 383B4129A33; Sat, 11 Feb 2017 10:05:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id C40E4652D2; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=rZC bRNP8cBp3UQQ+laGRw8A/XzE=; b=svUktSM/bJn9xAk+5ZSosysCHDFJYPwYJgg KTyObZD/ePdjZ+0PxZtJimIDoFSu7nEtHvC0WYnokROm/oMhNLFJhYCQ7+O0zgiC mQSzudNRLb2wFlYRImo8mDuj+b6imhIAea8Y7FOk7nM4b5RGdlIkj37GdTpQcDbp TLGPfuIA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= SOt6WAPXlhqWXSrOBL6C2HoJdQvhStfHFDmZq+LedWVcpClXJpiK+3joIvL5a9wN Lqql7A7hhlU1BMm1kq4FQ03U5ppJhWJ1hALgigcwPvSk8a/Z0wccIJ62fL2nIMeu XZHs6boEPRiCgd0Lu4LDq6z/jsAWTHRhNbQqLrtiBn8=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id AE6A8652D1; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
Received: from mail-qk0-f171.google.com (unknown [209.85.220.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 0E0E4652CC; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
Received: by mail-qk0-f171.google.com with SMTP id s140so66616179qke.0; Sat, 11 Feb 2017 10:05:35 -0800 (PST)
X-Gm-Message-State: AMke39mvdb4S9RGGlNJ9NIW/yryN3p/e5YTatqfesPFjmSqVIvwu5/5MObTB7PrfeUSKVCAS1+l/sJnT8B9EWA==
X-Received: by 10.55.170.17 with SMTP id t17mr13933696qke.15.1486836334971; Sat, 11 Feb 2017 10:05:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sat, 11 Feb 2017 10:05:14 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Sat, 11 Feb 2017 10:05:14 -0800
X-Gmail-Original-Message-ID: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
Message-ID: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: multipart/alternative; boundary=001a114d519895d98b0548450f27
X-Pobox-Relay-ID: B00396D0-F084-11E6-A0BE-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VrDTlA4byMvujNa31XHpGa7EKHs>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, Gen-ART <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:05:39 -0000

--001a114d519895d98b0548450f27
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 10, 2017 at 10:42 PM, Suresh Krishnan <suresh.krishnan@gmail.com
> wrote:

> On Feb 10, 2017 11:30 PM, "C. M. Heard" <heard@pobox.com> wrote:
>
> On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> > On 10/02/2017 23:20, Stewart Bryant wrote:
> > > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > > I wonder if we would best serve both our future and our heritage
> > > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > > or declared it as historic and wrote a new text from a clean start?
> > > >
> > > > I don't see that. It's a stable, widely deployed, interoperable
> > > > mechanism. That is rather orthogonal to the issue that has been
> raised,
> > > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > > across the Internet.
> > >
> > > I will not debate whether it is faulty or not,
> >
> > It's faulty by the standard of RFC4890 (which is Informational).
> >
> > > but it seems that in practice the Internet breaks the mechanism.
> > > However it breaks it is a way that seems disruptive to some user
> > > traffic. The document is really guidance one how hosts might use
> > > ICMP for optimization, and arguabl[y] need not be a standard at all.
> >
> > I think that's a mischaracterisation of the mechanism (and the draft).
> > PMTUD is not an optimisation. Without it, you get black holes.
>
> Actually, no. You do not have to use PMTUD to avoid black holes.
> Other options include:
>
> - Send packets no larger than 1280 bytes (this is always an option)
> - Use PLPMTUD (for transports that do their own packetization and
>   that can detect packet loss)
>
>
> How does this work for UDP?
>

Sending packets no larger than 1280 bytes is always an option, and in
the case of UDP-based request-response protocols such as DNS that do
not have connection state, it may be the only feasible option.

Anyway, the point I was trying to make was not to argue about better
or worse methods but rather to dispute the statement that PMTUD is
essential for avoiding black holes. I don't believe that it is. The
draft itself explicitly says that "IPv6 nodes are not required to
implement Path MTU Discovery."

> > My remark about heritage is that this vintage draft is very much a
> > > product of its time, and really needs modernizing, and after
> > > modernizing ought to look quite different, and thus maybe we
> > > should employ a procedure other than a simple replacement.
>
> I am afraid that I have to agree with this. Classic PMTUD by itself
> is today not enough, but it can be a very useful optimization to
> augment other techniques.
>
>
> OK.
>
>
> > It's proposed for Internet Standard. That means it must replace the
> > PS document and must specify the same thing, plus corrections,
> > minus unused features.
>
> All true, and my conclusion is that is it should not be promoted to IS.
>
>
> What criteria for advancement to IS do you think are not met by this
> document?
>

I do not dispute that the document has met the formal criteria for IS in
Section
2.2 of RFC 6410. I would argue, however, that its failure to provide a
complete
solution for environments where delivery of ICMP messages is not assured
constitutes a significant technical omission for today's Internet, and I
note
that per RFC 2026 Section 4.1.1, even a PS "should have no known technical
omissions." What I am asking the community, and the IESG, is whether it is
wise to advance a document with known technical omissions; it seems to me
that the Gen-ART reviewer has raised much the same question.

I would have no problem with republishing at PS to correct the errata
> and aid the eventual advance of RFC 4821 (PLPMTUD).
>
> If this document does go forward, the words in Appendix B (Changes
> Since RFC 1981) relating to RFC 4821 should be removed, since
> there was no mention of RFC 4821 in RFC 1981.
>
>
> Not sure I understand your concern. This is a change log since RFC1981.
>
And it is a fact that the reference to RFC4821 was added into this draft.
>
Can you clarify?
>

My apologies, I wrote that too hastily, before reading the complete change
log, which contains a description of what changed in each draft as the
document proceeded through the WG process. The comment that I should
have made is that many of those details are not useful to readers of an
archival document. Looking at a diff between RFC 1981 and this draft,
the substantive changes pretty much boil down to these:

      - In Section 1, added a reference to RFC4821 along with a short
        summary of what it does.

      - In Section 4, added text to discard an ICMP Packet Too Big message
        containing an MTU less than the IPv6 minimum link MTU and removed
        the corresponding note specifying actions that were removed from
        [I-D.ietf-6man-rfc2460bis].

      - In Section 5.2, removed text regarding RH0 (since it was deprecated
        by RFC5095) and removed text about obsolete security
classifications.

      - In Section 5.2, clarified that the tentative PMTU must not be made
        smaller that the IPv6 minimum link MTU.

Regarding that last change, I got confused when I was reading the current
text
in the draft:

   The node then uses the value in the MTU field in the Packet Too Big
   message as a tentative PMTU value or the minimum IPv6 next hope MTU
   if that is larger, and compares the tentative PMTU to the existing
   PMTU.  If the tentative PMTU is less than the existing PMTU estimate,
   the tentative PMTU replaces the existing PMTU as the PMTU value for
   the path.

I initially took the words "minimum IPv6 next hope [sic] MTU" to mean the
next
hop MTU of any link on the node, which of course is not what it meant. Maybe
I'm being dense, but it wasn't until I looked at Donald Eastlake's INT-DIR
review (https://www.ietf.org/mail-archive/web/int-dir/current/msg00339.html)
that the correct meaning finally dawned on me. May I suggest saying
 instead:

   The node then uses the value in the MTU field in the Packet Too Big
   message as a tentative PMTU value or the IPv6 minimum link MTU if
   that is larger, and compares the tentative PMTU to the existing
   PMTU.  If the tentative PMTU is less than the existing PMTU estimate,
   the tentative PMTU replaces the existing PMTU as the PMTU value for
   the path.

In other words, s/minimum IPv6 next hope MTU/IPv6 minimum link MTU/.
That makes the terminology consistent with the rest of the document.

Thanks and regards,

Mike Heard

--001a114d519895d98b0548450f27
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 10, 2017 at 10:42 PM, Suresh Krishnan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:suresh.krishnan@gmail.com" target=3D"_blank">suresh.krishnan@gma=
il.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex"><div dir=3D"auto"><div><di=
v><div class=3D"gmail-h5"><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote">On Feb 10, 2017 11:30 PM, &quot;C. M. Heard&quot; &lt;<a href=3D"mailt=
o:heard@pobox.com" target=3D"_blank">heard@pobox.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"gmail-m_-4490337820322616361quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex"><div class=3D"gmail=
-m_-4490337820322616361quoted-text">On Fri, 10 Feb 2017 11:45 -0800 , Brian=
 E Carpenter wrote:<br>
&gt; On 10/02/2017 23:20, Stewart Bryant wrote:<br>
&gt; &gt; On 10/02/2017 03:25, Brian E Carpenter wrote:<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; &gt;=
 On 10/02/2017 04:19, Stewart Bryant wrote:<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; &gt;=
 &gt; I wonder if we would best serve both our future and our heritage<br>
&gt; &gt; &gt; &gt; if we declared RFC1981 as historic, and either left the=
 idea there,<br>
&gt; &gt; &gt; &gt; or declared it as historic and wrote a new text from a =
clean start?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don&#39;t see that. It&#39;s a stable, widely deployed, in=
teroperable<br>
&gt; &gt; &gt; mechanism. That is rather orthogonal to the issue that has b=
een raised,<br>
&gt; &gt; &gt; which is that faulty ICMPv6 filtering blocks it on many, man=
y paths<br>
&gt; &gt; &gt; across the Internet.<br>
&gt; &gt;<br>
&gt; &gt; I will not debate whether it is faulty or not,<br>
&gt;<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; It&#39;s =
faulty by the standard of RFC4890 (which is Informational).<br>
&gt;<br>
</div>&gt; &gt; but it seems that in practice the Internet breaks the mecha=
nism.<br>
<div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; However it=
 breaks it is a way that seems disruptive to some user<br>
&gt; &gt; traffic. The document is really guidance one how hosts might use<=
br>
</div>&gt; &gt; ICMP for optimization, and arguabl[y] need not be a standar=
d at all.<br>
<div class=3D"gmail-m_-4490337820322616361quoted-text">&gt;<br>
&gt; I think that&#39;s a mischaracterisation of the mechanism (and the dra=
ft).<br>
&gt; PMTUD is not an optimisation. Without it, you get black holes.<br>
<br>
</div>Actually, no. You do not have to use PMTUD to avoid black holes.<br>
Other options include:<br>
<br>
- Send packets no larger than 1280 bytes (this is always an option)<br>
- Use PLPMTUD (for transports that do their own packetization and<br>
=C2=A0 that can detect packet loss)<br></blockquote></div></div></div></div=
></div><div dir=3D"auto"><br></div><div dir=3D"auto">How does this work for=
 UDP?</div></div></blockquote><div><br></div><div><div>Sending packets no l=
arger than 1280 bytes is always an option, and in</div><div>the case of UDP=
-based request-response protocols such as DNS that do</div><div>not have co=
nnection state, it may be the only feasible option.</div><div><br></div><di=
v>Anyway, the point I was trying to make was not to argue about better</div=
><div>or worse methods but rather to dispute the statement that PMTUD is</d=
iv><div>essential for avoiding black holes. I don&#39;t believe that it is.=
 The</div><div>draft itself explicitly says that &quot;IPv6 nodes are not r=
equired to</div><div>implement Path MTU Discovery.&quot;</div></div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex"><div dir=3D"auto"><span class=3D"gmail-"><div dir=
=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail-m_-4490337820322616361quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex"><div class=3D"gmail-m_-4490337820322616361quote=
d-text">
&gt; &gt; My remark about heritage is that this vintage draft is very much =
a<br>
&gt; &gt; product of its time, and really needs modernizing, and after<br>
&gt; &gt; modernizing ought to look quite different, and thus maybe we<br>
&gt; &gt; should employ a procedure other than a simple replacement.<br>
<br>
</div>I am afraid that I have to agree with this. Classic PMTUD by itself<b=
r>
is today not enough, but it can be a very useful optimization to<br>
augment other techniques.<br></blockquote></div></div></div><div dir=3D"aut=
o"><br></div></span><div dir=3D"auto">OK.=C2=A0</div><span class=3D"gmail-"=
><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extra"><=
div class=3D"gmail_quote"><blockquote class=3D"gmail-m_-4490337820322616361=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D"gmail-m_-4490337820322616361quoted-text"><br>
&gt; It&#39;s proposed for Internet Standard. That means it must replace th=
e<br>
&gt; PS document and must specify the same thing, plus corrections,<br>
&gt; minus unused features.<br>
<br>
</div>All true, and my conclusion is that is it should not be promoted to I=
S.<br></blockquote></div></div></div><div dir=3D"auto"><br></div></span><di=
v dir=3D"auto">What criteria for advancement to IS do you think are not met=
 by this document?</div></div></blockquote><div><br></div><div><div>I do no=
t dispute that the document has met the formal criteria for IS in Section</=
div><div>2.2 of RFC 6410. I would argue, however, that its failure to provi=
de a complete</div><div>solution for environments where delivery of ICMP me=
ssages is not assured</div><div>constitutes a significant technical omissio=
n for today&#39;s Internet, and I note</div><div>that per RFC 2026 Section =
4.1.1, even a PS &quot;should have no known technical</div><div>omissions.&=
quot; What I am asking the community, and the IESG, is whether it is</div><=
div>wise to advance a document with known technical omissions; it seems to =
me</div><div>that the Gen-ART reviewer has raised much the same question.</=
div></div><div><div><br></div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"auto"><spa=
n class=3D"gmail-"><div dir=3D"auto"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail-m_-4490337820322616361quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex">I would have no pro=
blem with republishing at PS to correct the errata<br>
and aid the eventual advance of RFC 4821 (PLPMTUD).<br>
<br>
If this document does go forward, the words in Appendix B (Changes<br>
Since RFC 1981) relating to RFC 4821 should be removed, since<br>
there was no mention of RFC 4821 in RFC 1981.<br></blockquote></div></div><=
/div><div dir=3D"auto"><br></div></span><div dir=3D"auto">Not sure I unders=
tand your concern. This is a change log since RFC1981.=C2=A0</div></div></b=
lockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-sty=
le:solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto">And it is a =
fact that the reference to RFC4821 was added into this draft.=C2=A0</div></=
div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto">Can y=
ou clarify?=C2=A0</div></div></blockquote><div><br></div><div>My apologies,=
 I wrote that too hastily, before reading the complete change</div><div>log=
, which contains a description of what changed in each draft as the</div><d=
iv>document proceeded through the WG process. The comment that I should</di=
v><div>have made is that many of those details are not useful to readers of=
 an</div><div>archival document. Looking at a diff between RFC 1981 and thi=
s draft,</div><div>the substantive changes pretty much boil down to these:<=
/div><div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 1, added a =
reference to RFC4821 along with a short</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 summary of what it does.</div></div><div><br></div><div><div>=C2=A0 =C2=
=A0 =C2=A0 - In Section 4, added text to discard an ICMP Packet Too Big mes=
sage</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 containing an MTU less than the =
IPv6 minimum link MTU and removed</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 the=
 corresponding note specifying actions that were removed from</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 [I-D.ietf-6man-rfc2460bis].</div></div><div><br></=
div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 5.2, removed text regarding=
 RH0 (since it was deprecated</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 by RFC5=
095) and removed text about obsolete security classifications.</div></div><=
div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 5.2, clarified th=
at the tentative PMTU must not be made</div></div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 smaller that the IPv6 minimum link MTU.</div><div><br></div><div><d=
iv><div>Regarding that last change, I got confused when I was reading the c=
urrent text=C2=A0</div><div>in the draft:</div><div><br></div><div>=C2=A0 =
=C2=A0The node then uses the value in the MTU field in the Packet Too Big</=
div><div>=C2=A0 =C2=A0message as a tentative PMTU value or the minimum IPv6=
 next hope MTU</div><div>=C2=A0 =C2=A0if that is larger, and compares the t=
entative PMTU to the existing</div><div>=C2=A0 =C2=A0PMTU.=C2=A0 If the ten=
tative PMTU is less than the existing PMTU estimate,</div><div>=C2=A0 =C2=
=A0the tentative PMTU replaces the existing PMTU as the PMTU value for</div=
><div>=C2=A0 =C2=A0the path.</div><div><br></div><div>I initially took the =
words &quot;minimum IPv6 next hope [sic] MTU&quot; to mean the next</div><d=
iv>hop MTU of any link on the node, which of course is not what it meant. M=
aybe</div><div>I&#39;m being dense, but it wasn&#39;t until I looked at Don=
ald Eastlake&#39;s INT-DIR</div><div>review (<a href=3D"https://www.ietf.or=
g/mail-archive/web/int-dir/current/msg00339.html">https://www.ietf.org/mail=
-archive/web/int-dir/current/msg00339.html</a>)</div><div>that the correct =
meaning finally dawned on me. May I suggest saying =C2=A0instead:</div><div=
><br></div><div>=C2=A0 =C2=A0The node then uses the value in the MTU field =
in the Packet Too Big</div><div>=C2=A0 =C2=A0message as a tentative PMTU va=
lue or the IPv6 minimum link MTU if</div><div>=C2=A0 =C2=A0that is larger, =
and compares the tentative PMTU to the existing</div><div>=C2=A0 =C2=A0PMTU=
.=C2=A0 If the tentative PMTU is less than the existing PMTU estimate,</div=
><div>=C2=A0 =C2=A0the tentative PMTU replaces the existing PMTU as the PMT=
U value for</div><div>=C2=A0 =C2=A0the path.</div><div><br></div><div>In ot=
her words, s/minimum IPv6 next hope MTU/IPv6 minimum link MTU/.</div></div>=
</div><div>That makes the terminology consistent with the rest of the docum=
ent.</div><div><br></div><div>Thanks and regards,</div><div><br></div><div>=
Mike Heard<br></div></div></div></div>

--001a114d519895d98b0548450f27--


From nobody Sat Feb 11 14:59:31 2017
Return-Path: <otroan@employees.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58722129593; Sat, 11 Feb 2017 14:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVmqmwQla--v; Sat, 11 Feb 2017 14:59:27 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id AE01212958D; Sat, 11 Feb 2017 14:59:27 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 11 Feb 2017 22:59:27 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 7599AD788D; Sat, 11 Feb 2017 14:59:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=ty5fPjcZy3Nqg4Wh6SbLO0l06G4=; b= c6ke+e30wx7UHQTss69syLtR7aoTuYqWAULKxvGY2I6d4le/C4EwfRIf3o3I+JP1 tHGssg2v8UezsgBKcm59nXVPSB1tUAKrnNB7NnUbw2n4I3GZiyCGmKvfWL12F7wP M6eAhNEZlZVa+nm5LpG7zDTFXujQPzR/gJ0I0pivk3Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=HM/MU5WH+IaRS1pyphKk8Bo 0jSy80P2hXL7B/gGR9S/4TmJvBAzgz9GDRuSYeGvuAzReLhulq8E3OmofIK2uDWU mWHp3LdzcFKU9diLHGiqLEh5V+MPRFa3DyT20UTneWFacMmJla0h5Nx88kzZknGb 9etswSQloDgOxZSl1piI=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id F3440D788A; Sat, 11 Feb 2017 14:59:25 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C207089992FC; Sat, 11 Feb 2017 23:59:21 +0100 (CET)
From: otroan@employees.org
Message-Id: <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Sat, 11 Feb 2017 23:59:20 +0100
In-Reply-To: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/RPG69nJyYvON51hL9r2mAQmLak4>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Gen-ART <gen-art@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 22:59:29 -0000

--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> How does this work for UDP?
>=20
> Sending packets no larger than 1280 bytes is always an option, and in
> the case of UDP-based request-response protocols such as DNS that do
> not have connection state, it may be the only feasible option.

Yes, but DNS tend to use IP fragmentation that suffers an order of =
magnitude worse fate than ICMP messages. ;-)

> Anyway, the point I was trying to make was not to argue about better
> or worse methods but rather to dispute the statement that PMTUD is
> essential for avoiding black holes. I don't believe that it is. The
> draft itself explicitly says that "IPv6 nodes are not required to
> implement Path MTU Discovery."

That's correct. But it then must restrict itself to sending packets at =
the minimum MTU size.
You cannot implement RFC2473 (IP in IP) without PMTUD for example.

[...]

> What criteria for advancement to IS do you think are not met by this =
document?
>=20
> I do not dispute that the document has met the formal criteria for IS =
in Section
> 2.2 of RFC 6410. I would argue, however, that its failure to provide a =
complete
> solution for environments where delivery of ICMP messages is not =
assured
> constitutes a significant technical omission for today's Internet, and =
I note
> that per RFC 2026 Section 4.1.1, even a PS "should have no known =
technical
> omissions." What I am asking the community, and the IESG, is whether =
it is
> wise to advance a document with known technical omissions; it seems to =
me
> that the Gen-ART reviewer has raised much the same question.

For IPv6, because of the removal of fragmentation by intermediate nodes, =
failure to provide a path where ICMP message delivery is assured is a =
considered a configuration error.

=46rom =
http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis=
.pdf:

"We observed that for IPV4 between 4% and 6% of the paths between the =
vantage points and our experimental setup filter ICMP PTB packets. For =
IPV6 this was between 0.77% and 1.07%. Furthermore, we found that when =
IPV4 Domain Name System (DNS) servers do not act on the receipt of ICMP =
PTB packets, between 11% and 14% of the answers from these DNS servers =
are lost. For IPV6 DNS servers this was between 40% and 42%. Lastly, we =
found that for IPV4 approximately 6% of the paths between the vantage =
points and our experimental setup filter IP fragments. For IPV6 this was =
approximately 10%."

=46rom that data it looks like we have been quite successful. ICMPv6 =
PMTUD is treated a lot better (about a 1% loss) than its IPv4 =
counterpart.
Unless better data exists I tend to conclude that the claim that the =
Internet breaks PTUMD for IPv6 is a myth.

Fragmentation on the other hand...
And please don't get me wrong, I think we have a big job to do on MTU =
issues. I just don't see data showing that PMTUD isn't doing what it was =
designed to do.

Best regards,
Ole




--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYn5dJAAoJEL7aWKiYQt926xAP/1sMZnrIKXS2y/MeUP1xHuPW
t5fvtAwaYLk1eDlpqkmQNagnn9RZOvoBgBZEN9xEL3pm2b+SD2PeP7cNbrCuY+K6
2LZ29tV12/Tu/mPq1JIyHjvRLN5RhmPOMXdxQyGAHvihJ+hjwJJEcsPqJkYaTzj0
rcZsVPXF38ueWUsM6TtbbXRSSCw2wOh4fhRbKCVaRBrerXkWu9EuRbS5IEwkA9/P
mJNm10RYXLvJcpR1xQMFHK3fsIrO+yEobiNtl6b3Uwh1z0l4OyoG65I8L295j/GW
SXKQIF8zmT59zcAFooajV+ZiCtSDBb+1XnPfzMxGX/Wo3a/uHqEhKrpOCHZmliDW
tJtsk1a+iopJnYP/4pKJ2SH9ccRQOU7K4zajTb7/0nvb4suAc5JrvqGIGZPmiVqf
12Zwz6w3j2g7Mt76uWcofXtcBuEBTmYiyGWYUb24YNUkZlSIwCC0/Qnmy+9JHQTo
x12EAh85S/utghlAyLmqmqRVPTw+j0sosIRxJxUlB/2tmSPuSvPw5BCOoJmtlcVf
pRE1pDEsW9w3/zL50w40t5hlouIh7UoC9cEsOJcPqI1sPXRy5DSmeW+4KEbxqF/H
6Wjr8HMNfpUpbPxsOmHj/8hAd07ibSCiEgk5/+iGCQ4GDU8mTJs8LaKcxz3h7UEs
jfFqsL+lt/obn+RsMm2k
=qWf4
-----END PGP SIGNATURE-----

--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020--


From nobody Sun Feb 12 16:45:43 2017
Return-Path: <yan@cnnic.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8750D1294E9 for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2017 16:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6NxJNTWNy7BP for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2017 16:45:40 -0800 (PST)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 215BD1294B0 for <gen-art@ietf.org>; Sun, 12 Feb 2017 16:45:38 -0800 (PST)
Received: from yanzhiwei (unknown [218.241.111.47]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0AZIpamAaFYdKH3KQ--.63849S2;  Mon, 13 Feb 2017 08:45:26 +0800 (CST)
Date: Mon, 13 Feb 2017 08:45:26 +0800
From: "Z.W. Yan" <yan@cnnic.cn>
To: "Meral Shirazipour" <meral.shirazipour@ericsson.com>, "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DA@eusaamb107.ericsson.se>
Message-ID: <201702130845254583290@cnnic.cn>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon255436567854_====="
X-CM-TRANSID: AQAAf0AZIpamAaFYdKH3KQ--.63849S2
X-Coremail-Antispam: 1UD129KBjvJXoW7AF1UAFy8GrWxJw17uF48WFg_yoW8Wryrpa yxWws5Ja4kJryjkwn293WUZa4fu3s3Cw4UXFyDWw18Xrs8GFykKrWjgr4jy3srJw1xAF4D XF42vF98Xw1ayFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUmlb7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwV C2z280aVCY1x0267AKxVWxJr0_GcWle2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k0 8I80eVW5JVWrJwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4AK048IF2xKxVWUJVW8JwAqx4 xG6xAIxVCFxsxG0wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1l Ox8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F2 4lFcxC0VAYjxAxZF0Ex2IqxwCY02Avz4vE14v_twCF04k20xvY0x0EwIxGrwCFx2IqxVCF s4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r 1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWU JVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6r W3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8 JbIYCTnIWIevJa73UjIFyTuYvjxUx9N3UUUUU
X-CM-SenderInfo: x1dqqupqqluhdfq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8us6_cVfVWEZrbRkAqYJPMBTbCQ>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 00:45:41 -0000

This is a multi-part message in MIME format.

--=====003_Dragon255436567854_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

RGVhciBNZXJhbCwNClRoYW5rIHlvdSBzbyBtdWNoIGZvciB5b3VyIGNvbW1lbnRzIHRvIHBvbGlz
aCB0aGlzIGRyYWZ0Lg0KRG8gd2UgbmVlZCB0byBzdWJtaXQgYSBuZXcgdmVyc2lvbiBiYXNlZCBv
biB5b3VyIGNvbW1lbnRzIG5vdz8NCkJlc3QgUmVnYXJkcywNClpoaXdlaSBZYW4NCg0KMjAxNy0w
Mi0xMyANCg0KDQoNClouVy4gWWFuIA0KDQoNCg0Kt6K8/sjLo7ogTWVyYWwgU2hpcmF6aXBvdXIg
DQq3osvNyrG85KO6IDIwMTctMDItMTEgIDA2OjA0OjQxIA0KytW8/sjLo7ogZHJhZnQtaWV0Zi1k
bW0taG5wcmVudW0uYWxsQHRvb2xzLmlldGYub3JnOyBnZW4tYXJ0QGlldGYub3JnIA0Ks63LzaO6
IA0K1vfM4qO6IEdlbi1BUlQgTGFzdCBDYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWRtbS1obnBy
ZW51bS0wNSANCiANCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMg
ZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxs
IElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYg
Q2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBs
YXN0IGNhbGwgY29tbWVudHMuDQpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUg
RkFRIGF0IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2Vu
QXJ0ZmFxPi4gDQogDQogDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDUNClJl
dmlld2VyOiBNZXJhbCBTaGlyYXppcG91cg0KUmV2aWV3IERhdGU6IDIwMTctMDItMTANCklFVEYg
TEMgRW5kIERhdGU6ICAgMjAxNy0wMi0xMA0KSUVTRyBUZWxlY2hhdCBkYXRlOiAtDQogDQogDQpT
dW1tYXJ5Og0KVGhpcyBkcmFmdCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgU3RhbmRhcmRz
IFRyYWNrIFJGQyBidXQgSSBoYXZlIGNvbW1lbnRzLg0KIA0KTWFqb3IgaXNzdWVzOg0KTWlub3Ig
aXNzdWVzOg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQotQWJzdHJhY3Q6DQpDdXJyZW50OiAN
CiJIb3dldmVyLCB0aGUgY3VycmVudCBQTUlQdjYgc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCBzcGVj
aWZ5IHJlbGF0ZWQgb3BlcmF0aW9ucyB3aGVuIGFuIEhOUCByZW51bWJlcmluZyBpcyBoYXBwZW5l
ZC4iLg0KU3VnZ2VzdGlvbiBmb3IgbW9yZSBjbGFyaXR5Og0KIkhvd2V2ZXIsIHRoZSBjdXJyZW50
IFBNSVB2NiBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgcmVsYXRlZCBvcGVyYXRpb25z
IHdoZW4gYW4gSE5QIHJlbnVtYmVyaW5nIGhhcyBoYXBwZW5lZCAoZS5nLiBkdWUgdG8gY2hhbmdl
IG9mIHNlcnZpY2UgcHJvdmlkZXIsIGNoYW5nZSBvZiBzaXRlIHRvcG9sb2d5LCBldGMuKS4iLg0K
LVtQYWdlIDNdLCAidG8gYW4gTUFHIi0tLS0+InRvIGEgTUFHIg0KIA0KLVtQYWdlIDddLCAidGhl
IHByb2NlZHVlciItLS0+InRoZSBwcm9jZWR1cmUiDQogDQpCZXN0IFJlZ2FyZHMsDQpNZXJhbA0K
LS0tDQpNZXJhbCBTaGlyYXppcG91cg0KRXJpY3Nzb24gUmVzZWFyY2gNCnd3dy5lcmljc3Nvbi5j
b20NCg==

--=====003_Dragon255436567854_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4bWxu
czp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46c2No
ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptID0gDQoiaHR0cDovL3NjaGVt
YXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIj48SEVBRD4NCjxNRVRBIGNvbnRl
bnQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIiIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlPg0K
PE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNIVE1MIDguMDAuNzYwMS4xNzUxNCI+DQo8
U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IENhbWJyaWEgTWF0aDsNCn0NCkBmb250
LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiBDYWxpYnJpOw0KfQ0KQHBhZ2UgV29yZFNlY3Rpb24xIHtz
aXplOiA4LjVpbiAxMS4waW47IG1hcmdpbjogMS4waW4gMS4waW4gMS4waW4gMS4waW47IH0NClAu
TXNvTm9ybWFsIHsNCglNQVJHSU46IDBpbiAwaW4gMHB0OyBGT05ULUZBTUlMWTogIkNhbGlicmki
LHNhbnMtc2VyaWY7IEZPTlQtU0laRTogMTFwdA0KfQ0KTEkuTXNvTm9ybWFsIHsNCglNQVJHSU46
IDBpbiAwaW4gMHB0OyBGT05ULUZBTUlMWTogIkNhbGlicmkiLHNhbnMtc2VyaWY7IEZPTlQtU0la
RTogMTFwdA0KfQ0KRElWLk1zb05vcm1hbCB7DQoJTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1G
QU1JTFk6ICJDYWxpYnJpIixzYW5zLXNlcmlmOyBGT05ULVNJWkU6IDExcHQNCn0NCkE6bGluayB7
DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUtcHJp
b3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVD
T1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUtcHJpb3JpdHk6IDk5DQp9DQpBOnZpc2l0ZWQg
ew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUt
cHJpb3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGlua0ZvbGxvd2VkIHsNCglDT0xPUjogcHVy
cGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZTsgbXNvLXN0eWxlLXByaW9yaXR5OiA5OQ0K
fQ0KU1BBTi5FbWFpbFN0eWxlMTcgew0KCUZPTlQtRkFNSUxZOiAiQ2FsaWJyaSIsc2Fucy1zZXJp
ZjsgQ09MT1I6IHdpbmRvd3RleHQ7IG1zby1zdHlsZS10eXBlOiBwZXJzb25hbC1jb21wb3NlDQp9
DQouTXNvQ2hwRGVmYXVsdCB7DQoJRk9OVC1GQU1JTFk6ICJDYWxpYnJpIixzYW5zLXNlcmlmOyBt
c28tc3R5bGUtdHlwZTogZXhwb3J0LW9ubHkNCn0NCkRJVi5Xb3JkU2VjdGlvbjEgew0KCXBhZ2U6
IFdvcmRTZWN0aW9uMQ0KfQ0KPC9TVFlMRT4NCjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8TUVUQSBuYW1lPUdFTkVSQVRPUiBjb250ZW50PSJNU0hUTUwg
Ni4wMC4yOTAwLjIxODAiPg0KPFNUWUxFPkBmb250LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiDLzszl
Ow0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IFZlcmRhbmE7DQp9DQpAZm9udC1mYWNl
IHsNCglmb250LWZhbWlseTogQMvOzOU7DQp9DQpAcGFnZSBTZWN0aW9uMSB7c2l6ZTogNTk1LjNw
dCA4NDEuOXB0OyBtYXJnaW46IDcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDsgbGF5b3V0LWdy
aWQ6IDE1LjZwdDsgfQ0KUC5Nc29Ob3JtYWwgew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dy
YXBoOyBURVhULUFMSUdOOiBqdXN0aWZ5OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlM
WTogIlRpbWVzIE5ldyBSb21hbiI7IEZPTlQtU0laRTogMTAuNXB0DQp9DQpMSS5Nc29Ob3JtYWwg
ew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dyYXBoOyBURVhULUFMSUdOOiBqdXN0aWZ5OyBN
QVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVzIE5ldyBSb21hbiI7IEZPTlQt
U0laRTogMTAuNXB0DQp9DQpESVYuTXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6IGludGVyLWlk
ZW9ncmFwaDsgVEVYVC1BTElHTjoganVzdGlmeTsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1G
QU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4iOyBGT05ULVNJWkU6IDEwLjVwdA0KfQ0KQTpsaW5rIHsN
CglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NClNQQU4uTXNvSHlw
ZXJsaW5rIHsNCglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NCkE6
dmlzaXRlZCB7DQoJQ09MT1I6IHB1cnBsZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0N
ClNQQU4uTXNvSHlwZXJsaW5rRm9sbG93ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JB
VElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLkVtYWlsU3R5bGUxNyB7DQoJRk9OVC1TVFlMRTogbm9y
bWFsOyBGT05ULUZBTUlMWTogVmVyZGFuYTsgQ09MT1I6IHdpbmRvd3RleHQ7IEZPTlQtV0VJR0hU
OiBub3JtYWw7IFRFWFQtREVDT1JBVElPTjogbm9uZTsgbXNvLXN0eWxlLXR5cGU6IHBlcnNvbmFs
LWNvbXBvc2UNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjENCn0NClVOS05PV04g
ew0KCUZPTlQtU0laRTogMTBwdA0KfQ0KQkxPQ0tRVU9URSB7DQoJTUFSR0lOLVRPUDogMHB4OyBN
QVJHSU4tQk9UVE9NOiAwcHg7IE1BUkdJTi1MRUZUOiAyZW0NCn0NCk9MIHsNCglNQVJHSU4tVE9Q
OiAwcHg7IE1BUkdJTi1CT1RUT006IDBweA0KfQ0KVUwgew0KCU1BUkdJTi1UT1A6IDBweDsgTUFS
R0lOLUJPVFRPTTogMHB4DQp9DQo8L1NUWUxFPg0KPC9IRUFEPg0KPEJPRFkgc3R5bGU9Ik1BUkdJ
TjogMTBweDsgRk9OVC1GQU1JTFk6IHZlcmRhbmE7IEZPTlQtU0laRTogMTBwdCI+DQo8RElWPjxG
T05UIGNvbG9yPSMwMDAwODAgc2l6ZT0yIGZhY2U9VmVyZGFuYT5EZWFyIE1lcmFsLDwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDA4MD5UaGFuayB5b3Ugc28gbXVjaCBmb3IgeW91
ciBjb21tZW50cyB0byBwb2xpc2ggdGhpcyANCmRyYWZ0LjwvRk9OVD48L0RJVj4NCjxESVY+PEZP
TlQgY29sb3I9IzAwMDA4MD5EbyB3ZSBuZWVkIHRvIHN1Ym1pdCBhIG5ldyB2ZXJzaW9uIGJhc2Vk
IG9uIHlvdXIgDQpjb21tZW50cyBub3c/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0j
MDAwMDgwIHNpemU9MiBmYWNlPVZlcmRhbmE+QmVzdCBSZWdhcmRzLDwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgY29sb3I9IzAwMDA4MD5aaGl3ZWkgWWFuPC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBjb2xvcj0jMDAwMDgwIHNpemU9MiBmYWNlPVZlcmRhbmE+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBjb2xvcj0jYzBjMGMwIHNpemU9MiBmYWNlPVZlcmRhbmE+MjAxNy0wMi0xMyA8
L0ZPTlQ+PC9ESVY+PEZPTlQgDQpjb2xvcj0jMDAwMDgwIHNpemU9MiBmYWNlPVZlcmRhbmE+DQo8
SFIgc3R5bGU9IldJRFRIOiAxMDBweCIgYWxpZ249bGVmdCBjb2xvcj0jYjVjNGRmIFNJWkU9MT4N
CjwvRk9OVD4NCjxESVY+PEZPTlQgY29sb3I9I2MwYzBjMCBzaXplPTIgZmFjZT1WZXJkYW5hPjxT
UEFOPlouVy4gWWFuPC9TUEFOPiA8L0ZPTlQ+PC9ESVY+DQo8SFIgY29sb3I9I2I1YzRkZiBTSVpF
PTE+DQoNCjxESVY+PEZPTlQgc2l6ZT0yIGZhY2U9VmVyZGFuYT48U1RST05HPreivP7Iy6O6PC9T
VFJPTkc+IE1lcmFsIFNoaXJhemlwb3VyIA0KPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTIgZmFjZT1WZXJkYW5hPjxTVFJPTkc+t6LLzcqxvOSjujwvU1RST05HPiAyMDE3LTAyLTExJm5i
c3A7IDA2OjA0OjQxIA0KPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTIgZmFjZT1WZXJk
YW5hPjxTVFJPTkc+ytW8/sjLo7o8L1NUUk9ORz4gDQpkcmFmdC1pZXRmLWRtbS1obnByZW51bS5h
bGxAdG9vbHMuaWV0Zi5vcmc7IGdlbi1hcnRAaWV0Zi5vcmcgPC9GT05UPjwvRElWPg0KPERJVj48
Rk9OVCBzaXplPTIgZmFjZT1WZXJkYW5hPjxTVFJPTkc+s63LzaO6PC9TVFJPTkc+IDwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yIGZhY2U9VmVyZGFuYT48U1RST05HPtb3zOKjujwvU1RS
T05HPiBHZW4tQVJUIExhc3QgQ2FsbCByZXZpZXcgb2YgDQpkcmFmdC1pZXRmLWRtbS1obnByZW51
bS0wNSA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MiBmYWNlPVZlcmRhbmE+PC9GT05U
PiA8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yIGZhY2U9VmVyZGFuYT4NCjxESVYgY2xhc3M9V29y
ZFNlY3Rpb24xPg0KPFAgY2xhc3M9TXNvTm9ybWFsPkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSANCkdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IA0K
dGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiZuYnNwOyBQbGVhc2UgdHJlYXQgdGhlc2UgY29t
bWVudHMganVzdCBsaWtlIGFueSANCm90aGVyIGxhc3QgY2FsbCBjb21tZW50cy48bzpwPjwvbzpw
PjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5Gb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNl
ZSB0aGUgRkFRIGF0IA0KJmx0O2h0dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3Ry
YWMvd2lraS9HZW5BcnRmYXEmZ3Q7LiA8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1h
bD48bzpwPiZuYnNwOzwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwv
bzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5Eb2N1bWVudDogZHJhZnQtaWV0Zi1kbW0taG5w
cmVudW0tMDU8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5SZXZpZXdlcjogTWVy
YWwgU2hpcmF6aXBvdXI8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5SZXZpZXcg
RGF0ZTogMjAxNy0wMi0xMDxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPklFVEYg
TEMgRW5kIERhdGU6Jm5ic3A7Jm5ic3A7IDIwMTctMDItMTA8bzpwPjwvbzpwPjwvUD4NCjxQIGNs
YXNzPU1zb05vcm1hbD5JRVNHIFRlbGVjaGF0IGRhdGU6IC08bzpwPjwvbzpwPjwvUD4NCjxQIGNs
YXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD48
bzpwPiZuYnNwOzwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5TdW1tYXJ5OjxvOnA+PC9v
OnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPlRoaXMgZHJhZnQgaXMgcmVhZHkgdG8gYmUgcHVi
bGlzaGVkIGFzIFN0YW5kYXJkcyBUcmFjayBSRkMgDQpidXQgSSBoYXZlIGNvbW1lbnRzLjxvOnA+
PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9QPg0KPFAg
Y2xhc3M9TXNvTm9ybWFsPk1ham9yIGlzc3Vlczo8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1z
b05vcm1hbD5NaW5vciBpc3N1ZXM6PG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+
Tml0cy9lZGl0b3JpYWwgY29tbWVudHM6PG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3Jt
YWw+LUFic3RyYWN0OjxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPkN1cnJlbnQ6
IDxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPiJIb3dldmVyLCB0aGUgY3VycmVu
dCBQTUlQdjYgc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCBzcGVjaWZ5IA0KcmVsYXRlZCBvcGVyYXRp
b25zIHdoZW4gYW4gSE5QIHJlbnVtYmVyaW5nIGlzIGhhcHBlbmVkLiIuPG86cD48L286cD48L1A+
DQo8UCBjbGFzcz1Nc29Ob3JtYWw+U3VnZ2VzdGlvbiBmb3IgbW9yZSBjbGFyaXR5OjxvOnA+PC9v
OnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPiJIb3dldmVyLCB0aGUgY3VycmVudCBQTUlQdjYg
c3BlY2lmaWNhdGlvbiBkb2VzIG5vdCBzcGVjaWZ5IA0KcmVsYXRlZCBvcGVyYXRpb25zIHdoZW4g
YW4gSE5QIHJlbnVtYmVyaW5nIGhhcyBoYXBwZW5lZCAoZS5nLiBkdWUgdG8gY2hhbmdlIG9mIA0K
c2VydmljZSBwcm92aWRlciwgY2hhbmdlIG9mIHNpdGUgdG9wb2xvZ3ksIGV0Yy4pLiIuPG86cD48
L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+PG86cD48L286cD48L1A+DQo8UCBjbGFzcz1N
c29Ob3JtYWw+LVtQYWdlIDNdLCAidG8gYW4gTUFHIi0tLS0mZ3Q7InRvIGEgTUFHIjxvOnA+PC9v
OnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9QPg0KPFAgY2xh
c3M9TXNvTm9ybWFsPi1bUGFnZSA3XSwgInRoZSBwcm9jZWR1ZXIiLS0tJmd0OyJ0aGUgDQpwcm9j
ZWR1cmUiPG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286
cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9QPg0K
PFAgY2xhc3M9TXNvTm9ybWFsPk1lcmFsPG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3Jt
YWw+LS0tPG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+TWVyYWwgU2hpcmF6aXBv
dXI8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5Fcmljc3NvbiBSZXNlYXJjaDxv
OnA+PC9vOnA+PC9QPg0KPFAgDQpjbGFzcz1Nc29Ob3JtYWw+d3d3LmVyaWNzc29uLmNvbTxvOnA+
PC9vOnA+PC9QPjwvRElWPjwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--=====003_Dragon255436567854_=====--



From nobody Sun Feb 12 16:53:04 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48401129521; Sun, 12 Feb 2017 16:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36iWBtMFHc88; Sun, 12 Feb 2017 16:52:45 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46021294E9; Sun, 12 Feb 2017 16:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10991; q=dns/txt; s=iport; t=1486947164; x=1488156764; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=BYQ9fDmK7GmTXhib7cVNaX+eYAAwaYK3/ly0Rpk4VuM=; b=MIqphDEtN6X+wfYrJoBXZYXUcT4kg6+rilfy9Biugc4qDSHksxeOiwXc AyJFS/cznrn5nkd9a9S2X4olZTr9m3gJqWzE9oHoE0eOnc+6hfXcHgrFl r/OAMLIeEOPxdbaB+5ciSzKIRnAduJcdO8ol5GLiGYf+VxurkfvKLxyA8 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AaAQBZAqFY/4gNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm9jgWoHjVqSCpAKhSyCDIYiAoJ7PxgBAgEBAQEBAQFiKIRpAQE?= =?us-ascii?q?BAwFuCwULAgEIDgMDAQIoBzIUCQgCBAENBYlSAw0IsQcrixYBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEdhkyEb4JRgVURATwWhS8FkAOFUYYeAZITgXuFF4lzkxQBHzh?= =?us-ascii?q?4CFEVPYRFHYFhdYgSgSGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,155,1484006400";  d="scan'208,217";a="383183107"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Feb 2017 00:52:43 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1D0qh1E004281 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 13 Feb 2017 00:52:43 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 12 Feb 2017 18:52:42 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Sun, 12 Feb 2017 18:52:42 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Charlie Perkins <charles.perkins@earthlink.net>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHShZN7GUjlGCaTJE+d8OzNd5SzNQ==
Date: Mon, 13 Feb 2017 00:52:42 +0000
Message-ID: <D4C63E24.2598D8%sgundave@cisco.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
In-Reply-To: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: multipart/alternative; boundary="_000_D4C63E242598D8sgundaveciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/WCnkrwx1oKELzzsv02gPbhBuxWg>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 00:52:47 -0000

--_000_D4C63E242598D8sgundaveciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Charlie,

Please see inline.


From: dmm <dmm-bounces@ietf.org<mailto:dmm-bounces@ietf.org>> on behalf of =
Charlie Perkins <charles.perkins@earthlink.net<mailto:charles.perkins@earth=
link.net>>
Date: Friday, February 10, 2017 at 2:28 PM
To: Dale Worley <worley@ariadne.com<mailto:worley@ariadne.com>>, "gen-art@i=
etf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:gen-art@ietf.org=
>>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org<mailto:draft-ietf-dmm-4283mnids.=
all@ietf.org>" <draft-ietf-dmm-4283mnids.all@ietf.org<mailto:draft-ietf-dmm=
-4283mnids.all@ietf.org>>, "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf=
.org<mailto:ietf@ietf.org>>, "dmm@ietf.org<mailto:dmm@ietf.org>" <dmm@ietf.=
org<mailto:dmm@ietf.org>>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04


4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.

> Here I am at a loss, because I was specifically requested to insert some =
descriptive but not normative text.  I will ask the person who made the req=
uest to provide their feedback on the mailing list.  For myself, I am more =
than happy to delete the text.

When we discussed this issue in the past, the general feedback from the WG =
was that the draft should provide some minimal amount of details on the new=
 identifier types, what the identifier is, how the identifier is constructe=
d, what is the access technology and a reference to the specification that =
provides that definition. The idea is NOT TO provide extensive details on t=
he spec, but to enable a reader with some high level details and a pointer =
to the specification. I tend to think the text in the current specification=
 just does that. If the text is seen as redundant text, we can certainly ad=
d a statement saying that the definition for the identifier is provided in =
spec-XYZ and is repeated here for convenience. May be other folks in the WG=
 have some views on this.


Comments from 10/11/2015 email:

"Some text on the motivation for defining new Types may be helpful. Documen=
t is not just standardizing the currently in-use/popular identifier types, =
its also introducing new types are not in use. The reasons/interest for def=
ining identifiers that are tied to the physical elements of the device (RFI=
D, MAC address ..etc) and how it helps in deployment of the technology may =
be useful. Few lines of text will really help."

"I was hoping to see a sub-section for each of the types. We cannot standar=
dize a identifier type without providing any explanation on the identifier =
type or the references to the base definitions. This can be painful, but I'=
d have a small section for each of the types. It can be 3 line text on the =
a.) Definition b.) Format c.) Example format d.) Reference to the base spec=
 that defines those identifiers."



--_000_D4C63E242598D8sgundaveciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <F2960967A78F294BB9C9AEF31440D9F7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Hi Charlie,</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Please see inline.</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>dmm &lt;<a href=3D"mailto:dmm=
-bounces@ietf.org">dmm-bounces@ietf.org</a>&gt; on behalf of Charlie Perkin=
s &lt;<a href=3D"mailto:charles.perkins@earthlink.net">charles.perkins@eart=
hlink.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, February 10, 2017 at =
2:28 PM<br>
<span style=3D"font-weight:bold">To: </span>Dale Worley &lt;<a href=3D"mail=
to:worley@ariadne.com">worley@ariadne.com</a>&gt;, &quot;<a href=3D"mailto:=
gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@=
ietf.org">gen-art@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:draft-i=
etf-dmm-4283mnids.all@ietf.org">draft-ietf-dmm-4283mnids.all@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:draft-ietf-dmm-4283mnids.all@ietf.org">draft-iet=
f-dmm-4283mnids.all@ietf.org</a>&gt;, &quot;<a href=3D"mailto:ietf@ietf.org=
">ietf@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a href=
=3D"mailto:dmm@ietf.org">dmm@ietf.org</a>&quot; &lt;<a href=3D"mailto:dmm@i=
etf.org">dmm@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [DMM] Review of draft-=
ietf-dmm-4283mnids-04<br>
</div>
<div><br>
</div>
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<blockquote cite=3D"mid:148589124578.6067.10086408452323670298.idtracker@ie=
tfa.amsl.com" type=3D"cite">
<pre wrap=3D"">4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.</pre>
</blockquote>
<br>
&gt; Here I am at a loss, because I was specifically requested to insert so=
me descriptive but not normative text.&nbsp; I will ask the person who made=
 the request to provide their feedback on the mailing list.&nbsp; For mysel=
f, I am more than happy to delete the text.<br>
<br>
When we discussed this issue in the past, the general feedback from the WG =
was that the draft should provide some minimal amount of details on the new=
 identifier types, what the identifier is, how the identifier is constructe=
d, what is the access technology
 and a reference to the specification that provides that definition. The id=
ea is NOT TO provide extensive details on the spec, but to enable a reader =
with some high level details and a pointer to the specification. I tend to =
think the text in the current specification
 just does that. If the text is seen as redundant text, we can certainly ad=
d a statement saying that the definition for the identifier is provided in =
spec-XYZ and is repeated here for convenience. May be other folks in the WG=
 have some views on this.</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Comments from 10/11/2015 email:</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<pre style=3D"word-wrap: break-word;"><pre style=3D"word-wrap: break-word;"=
><pre style=3D"word-wrap: break-word;"><pre style=3D"word-wrap: break-word;=
"><font color=3D"#ff0000" style=3D"font-family: Calibri, sans-serif; font-s=
ize: 14px;"><b><font face=3D"Calibri,sans-serif"><span style=3D"white-space=
: pre-wrap;">&quot;Some text on the motivation for defining new Types may b=
e helpful. Document is not just </span></font><span style=3D"white-space: p=
re-wrap;">standardizing the currently in-use/popular identifier types, its =
also introducing new types are not in use. The reasons/interest for definin=
g identifiers that are tied to the physical elements of the device (RFID, M=
AC address ..etc) and how it helps in deployment of the technology may be u=
seful. Few lines of text will really help.</span></b></font><font color=3D"=
#ff0000"><span style=3D"font-size: 14px; white-space: pre-wrap;"><b>&#8221;=
</b></span></font></pre></pre></pre></pre>
</div>
</span>
<div>&quot;<b style=3D"font-family: Calibri, sans-serif; font-size: 14px; c=
olor: rgb(255, 0, 0);"><span style=3D"white-space: pre-wrap;">I</span><span=
 style=3D"white-space: pre-wrap;"> was hoping to see a sub-section for each=
 of the types. We cannot standardize a identifier
 type without providing any explanation on the identifier type or the refer=
ences to the base definitions. This can be painful, but I'd have a small se=
ction for each of the types. It can be 3 line text on the a.) Definition b.=
) Format c.) Example format d.)
 Reference to the base spec that defines those identifiers.</span></b><font=
 color=3D"#ff0000" face=3D"Calibri,sans-serif"><span style=3D"white-space: =
pre-wrap;"><b>&#8221;</b></span></font></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif"><span style=3D"whi=
te-space: pre-wrap;"><b><br>
</b></span></font></div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><b style=
=3D"color: rgb(255, 0, 0);"><span style=3D"white-space: pre-wrap;"><br>
</span></b></div>
</span>
</body>
</html>

--_000_D4C63E242598D8sgundaveciscocom_--


From nobody Sun Feb 12 17:22:50 2017
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178A712954D; Sun, 12 Feb 2017 17:22:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nql-ZQeSjjOU; Sun, 12 Feb 2017 17:22:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36CF912954B; Sun, 12 Feb 2017 17:22:45 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAM02882; Mon, 13 Feb 2017 01:22:39 +0000 (GMT)
Received: from SZXEMA416-HUB.china.huawei.com (10.82.72.35) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 13 Feb 2017 01:22:38 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.215]) by SZXEMA416-HUB.china.huawei.com ([10.82.72.35]) with mapi id 14.03.0235.001; Mon, 13 Feb 2017 09:22:20 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Review of draft-ietf-ccamp-flexible-grid-ospf-ext-08
Thread-Index: AQHSg/TQqxb6Zkls30GMpx9otGdAXqFmJl+w
Date: Mon, 13 Feb 2017 01:22:20 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43988E8F6@SZXEMA504-MBX.china.huawei.com>
References: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com>
In-Reply-To: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.57.78.114]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0202.58A10A63.00CA, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.7.215, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 941cf219dc341b2495025955e7d5b76b
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9MzfCEyyXZKvD0Q8E3aAx9z32LM>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [Gen-art] =?utf-8?b?562U5aSNOiBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft?= =?utf-8?q?p-flexible-grid-ospf-ext-08?=
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 01:22:48 -0000

SGksIFBldGUsIA0KDQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3LiBQbGVhc2UgZmluZCBteSBjb25z
aWRlcmF0aW9ucyBpbmxpbmUuLi4NCg0KQmVzdCB3aXNoZXMsDQpIYW9taWFuDQoNCi0tLS0t6YKu
5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujogUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tA
cXRpLnF1YWxjb21tLmNvbV0gDQrlj5HpgIHml7bpl7Q6IDIwMTflubQy5pyIMTHml6UgNzoyNA0K
5pS25Lu25Lq6OiBnZW4tYXJ0QGlldGYub3JnDQrmioTpgIE6IGRyYWZ0LWlldGYtY2NhbXAtZmxl
eGlibGUtZ3JpZC1vc3BmLWV4dC5hbGxAaWV0Zi5vcmc7IGNjYW1wQGlldGYub3JnDQrkuLvpopg6
IFJldmlldyBvZiBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDgNCg0K
UmV2aWV3ZXI6IFBldGUgUmVzbmljaw0KUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzDQoN
CkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBH
ZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1l
bnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuIFBsZWFz
ZSB3YWl0IGZvciBkaXJlY3Rpb24gZnJvbSB5b3VyIGRvY3VtZW50IHNoZXBoZXJkIG9yIEFEIGJl
Zm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRyYWZ0Lg0KDQpGb3IgbW9yZSBpbmZv
cm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQoNCjxodHRwczovL3RyYWMuaWV0Zi5vcmcv
dHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1jY2FtcC1m
bGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA4DQpSZXZpZXdlcjogUGV0ZSBSZXNuaWNrDQpSZXZpZXcg
RGF0ZTogMjAxNy0wMi0xMA0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wMS0zMQ0KSUVTRyBUZWxl
Y2hhdCBkYXRlOiAyMDE3LTAyLTE2DQoNClN1bW1hcnk6IFJlYWR5IHdpdGggTml0cw0KDQpBIGNv
dXBsZSBvZiBuaXRzIHRoYXQgSSBtZW50aW9uZWQgaW4gbXkgZWFybGllciByZXZpZXcgdGhhdCB5
b3UgbWlnaHQgd2FudCB0byBhZGRyZXNzLCBidXQgbm9uZSBvZiB0aGVtIGFyZSBlc3NlbnRpYWwu
IChZb3UgbWF5IGhhdmUgZGVjaWRlZCB0aGF0IEkgd2FzIHdyb25nOyB0aGF0J3MgT0sgdG9vLikg
SSBkaWRuJ3QgYm90aGVyIENjJ2luZyB0aGUgSUVURiBsaXN0IG9uIHRoaXMsIHNpbmNlIHRoZXkn
cmUgYm90aCB2ZXJ5IG1pbm9yLg0KDQpNYWpvciBpc3N1ZXM6IE5vbmUNCg0KTWlub3IgaXNzdWVz
OiBOb25lDQoNCk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOiANCg0KMy4xOg0KDQogICBBIHNldCBv
ZiBub24tb3ZlcmxhcHBpbmcgYXZhaWxhYmxlIGZyZXF1ZW5jeSByYW5nZXMgTVVTVCBiZSANCiAg
IGRpc3NlbWluYXRlZCBpbiBvcmRlciB0byBhbGxvdyBlZmZpY2llbnQgcmVzb3VyY2UgbWFuYWdl
bWVudCBvZiANCiAgIGZsZXhpLWdyaWQgRFdETSBsaW5rcyBhbmQgUlNBIHByb2NlZHVyZXMgd2hp
Y2ggYXJlIGRlc2NyaWJlZCBpbiANCiAgIFNlY3Rpb24gNC44IG9mIFtSRkM3Njk4XS4gDQoNClRo
b3NlIE1VU1RzIGxvb2sgd2VpcmQgdG8gbWUuIEkgdGhpbmsgaW5zdGVhZCBvZiAiTVVTVCBiZSIg
eW91IG1lYW4gImFyZSIsIHNpbmNlIGl0IGRvZXNuJ3QgbG9vayBsaWtlIGFuIGltcGxlbWVudGF0
aW9uIHJlYWxseSBoYXMgYSBjaG9pY2UgaGVyZS4NCltIYW9taWFuXSBOb3RlZCBhbmQgd2lsbCBj
aGFuZ2UgaW4gbmV4dCB2ZXJzaW9uLg0KDQoNCjMuMjoNCg0KICAgSGVuY2UsIGluIG9yZGVyIHRv
IHN1cHBvcnQgYWxsIHBvc3NpYmxlIGFwcGxpY2F0aW9ucyBhbmQgDQogICBpbXBsZW1lbnRhdGlv
bnMgdGhlIGZvbGxvd2luZyBpbmZvcm1hdGlvbiBzaG91bGQgYmUgYWR2ZXJ0aXNlZCBmb3INCiAg
IGEgZmxleGktZ3JpZCBEV0RNIGxpbms6DQogICANCklzIHRoYXQgInNob3VsZCIgaW4gdGhlcmUg
bWVhbnQgdG8gYmUgbm9ybWF0aXZlPyBUaGF0IGlzLCBkbyBiYWQgdGhpbmdzIGhhcHBlbiBpZiBJ
IGRvbid0IGFkdmVydGlzZSBvbmUgb2YgdGhvc2UgaXRlbXM/IE9yIGRvIHlvdSBqdXN0IG1lYW4g
InRoZSBmb2xsb3dpbmcgaW5mb3JtYXRpb24gaXMgYWR2ZXJ0aXNlZC4uLiI/IA0KDQpbSGFvbWlh
bl0gSSBmZWVsIHdlaXJkIGlmIHJlcGxhY2UgJ3Nob3VsZCBiZScgd2l0aCAnaXMnLCBhcyB5b3Ug
Y2Fubm90IHN1cHBvcnQgc29tZSBhcHBsaWNhdGlvbi9pbXBsZW1lbnRhdGlvbiAocmF0aGVyIHRo
YW4gZG8gYmFkIHRoaW5ncykgaWYgeW91IGRvbid0IGFkdmVydGlzZS4uLiBIb3cgYWJvdXQgZm9s
bG93aW5nIGNoYW5nZT8gDQoNCk9MRA0KICAgSGVuY2UsIGluIG9yZGVyIHRvIHN1cHBvcnQgYWxs
IHBvc3NpYmxlIGFwcGxpY2F0aW9ucyBhbmQgDQogICBpbXBsZW1lbnRhdGlvbnMgdGhlIGZvbGxv
d2luZyBpbmZvcm1hdGlvbiBzaG91bGQgYmUgYWR2ZXJ0aXNlZCBmb3INCiAgIGEgZmxleGktZ3Jp
ZCBEV0RNIGxpbms6DQpORVcNCiAgIEhlbmNlLCBpbiBvcmRlciB0byBzdXBwb3J0IGFsbCBwb3Nz
aWJsZSBhcHBsaWNhdGlvbnMgYW5kIA0KICAgaW1wbGVtZW50YXRpb25zIHRoZSBmb2xsb3dpbmcg
aW5mb3JtYXRpb24gaXMgcmVxdWlyZWQgdG8gYmUgYWR2ZXJ0aXNlZA0KICAgZm9yIGEgZmxleGkt
Z3JpZCBEV0RNIGxpbms6DQoNCg==


From nobody Sun Feb 12 18:00:04 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA73D12943E; Sun, 12 Feb 2017 18:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdDvEBtJDRuK; Sun, 12 Feb 2017 18:00:00 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA343129434; Sun, 12 Feb 2017 18:00:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486951200; x=1518487200; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=oa3JNdOKgoM6LB11ZREIX5DuPkLa3Ox7eTZYBYqBr00=; b=Swycco22s1MElq6jrDsLUWmrZ+Fe5G4GVoZqEWN/jMbUlx2OF5/0I44Q 2Rgg1Ro9usIE49Bl8HZlqAE+whhaZy6Su74jWwJYpGm0RMgXyFK8jC5Qt JfZ22bbeWz/EV2ooiYkWihe5PRdD5brV7wbaBTjynYRllO09yIEw4PW/P w=;
X-IronPort-AV: E=Sophos;i="5.35,155,1484035200"; d="scan'208";a="262268643"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine01.qualcomm.com with ESMTP; 12 Feb 2017 18:00:00 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8437"; a="865501785"
Received: from unknown (HELO [10.64.113.105]) ([10.64.113.105]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Feb 2017 17:59:48 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: Zhenghaomian <zhenghaomian@huawei.com>
Date: Sun, 12 Feb 2017 19:53:48 -0600
Message-ID: <760710CF-FC4F-4CFD-AFB8-82888150A4BD@qti.qualcomm.com>
In-Reply-To: <E0C26CAA2504C84093A49B2CAC3261A43988E8F6@SZXEMA504-MBX.china.huawei.com>
References: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com> <E0C26CAA2504C84093A49B2CAC3261A43988E8F6@SZXEMA504-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/fi6e5YSaRLbyaz-UfCyh6DEgl6o>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 02:00:02 -0000

[Trimming down]

On 12 Feb 2017, at 19:22, Zhenghaomian wrote:

> 3.2:
>
>    Hence, in order to support all possible applications and
>    implementations the following information should be advertised for
>    a flexi-grid DWDM link:
>
> Is that "should" in there meant to be normative? That is, do bad 
> things happen if I don't advertise one of those items? Or do you just 
> mean "the following information is advertised..."?
>
> [Haomian] I feel weird if replace 'should be' with 'is', as you cannot 
> support some application/implementation (rather than do bad things) if 
> you don't advertise... How about following change?
>
> OLD
>    Hence, in order to support all possible applications and
>    implementations the following information should be advertised for
>    a flexi-grid DWDM link:
> NEW
>    Hence, in order to support all possible applications and
>    implementations the following information is required to be 
> advertised
>    for a flexi-grid DWDM link:

Well, that's starting to feel like a SHOULD or a MUST. That is to say, 
some applications/implementations will not work if you don't advertise 
these things, so if you're not going to advertise one or more of them, 
you'd better know what you're doing and understand the consequences. 
That's the 2119 definition of SHOULD. On the other hand, if it's really 
always required because you really have to support all of those 
applications/implementations, and there are no good reasons to fail to 
advertise any of these things, then that's a MUST.

As I said before, I'm someone who doesn't like putting in MUSTs and 
SHOULDs (I've even written protocol documents where they never appear), 
but if you really mean "required" or "required unless you know what 
you're doing", I see no harm in putting them in.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Sun Feb 12 18:39:28 2017
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 573D7129463; Sun, 12 Feb 2017 18:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDFyzsHUMern; Sun, 12 Feb 2017 18:39:21 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50A8D129450; Sun, 12 Feb 2017 18:39:20 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGJ06394; Mon, 13 Feb 2017 02:39:18 +0000 (GMT)
Received: from SZXEMA419-HUB.china.huawei.com (10.82.72.37) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 13 Feb 2017 02:39:17 +0000
Received: from SZXEMA504-MBX.china.huawei.com ([169.254.7.215]) by SZXEMA419-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0235.001; Mon, 13 Feb 2017 10:38:50 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: Review of draft-ietf-ccamp-flexible-grid-ospf-ext-08
Thread-Index: AQHSg/TQqxb6Zkls30GMpx9otGdAXqFmJl+w//+DowCAAJJRAA==
Date: Mon, 13 Feb 2017 02:38:50 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43988E99D@SZXEMA504-MBX.china.huawei.com>
References: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com> <E0C26CAA2504C84093A49B2CAC3261A43988E8F6@SZXEMA504-MBX.china.huawei.com> <760710CF-FC4F-4CFD-AFB8-82888150A4BD@qti.qualcomm.com>
In-Reply-To: <760710CF-FC4F-4CFD-AFB8-82888150A4BD@qti.qualcomm.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.57.78.114]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.58A11C56.016C, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.7.215, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 741699c519cbb5ec06e60b5281417e95
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nlGTeWUaN78RHvlZsob_m323bDo>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [Gen-art] =?gb2312?b?tPC4tDogUmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAt?= =?gb2312?b?ZmxleGlibGUtZ3JpZC1vc3BmLWV4dC0wOA==?=
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 02:39:23 -0000

VGhhbmtzIFBldGUsIHRoZW4gSSBwcmVmZXIgdG8ga2VlcCBpdCBhcyBpdCBpcywgaS5lLiwgdXNl
IHRoZSB0ZXJtICdzaG91bGQnLiANCg0KQmVzdCB3aXNoZXMsDQpIYW9taWFuDQoNCi0tLS0t08q8
/tStvP4tLS0tLQ0Kt6K8/sjLOiBQZXRlIFJlc25pY2sgW21haWx0bzpwcmVzbmlja0BxdGkucXVh
bGNvbW0uY29tXSANCreiy83KsbzkOiAyMDE3xOoy1MIxM8jVIDk6NTQNCsrVvP7IyzogWmhlbmdo
YW9taWFuDQqzrcvNOiBnZW4tYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxl
LWdyaWQtb3NwZi1leHQuYWxsQGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZw0K1vfM4jogUmU6IFJl
dmlldyBvZiBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDgNCg0KW1Ry
aW1taW5nIGRvd25dDQoNCk9uIDEyIEZlYiAyMDE3LCBhdCAxOToyMiwgWmhlbmdoYW9taWFuIHdy
b3RlOg0KDQo+IDMuMjoNCj4NCj4gICAgSGVuY2UsIGluIG9yZGVyIHRvIHN1cHBvcnQgYWxsIHBv
c3NpYmxlIGFwcGxpY2F0aW9ucyBhbmQNCj4gICAgaW1wbGVtZW50YXRpb25zIHRoZSBmb2xsb3dp
bmcgaW5mb3JtYXRpb24gc2hvdWxkIGJlIGFkdmVydGlzZWQgZm9yDQo+ICAgIGEgZmxleGktZ3Jp
ZCBEV0RNIGxpbms6DQo+DQo+IElzIHRoYXQgInNob3VsZCIgaW4gdGhlcmUgbWVhbnQgdG8gYmUg
bm9ybWF0aXZlPyBUaGF0IGlzLCBkbyBiYWQgDQo+IHRoaW5ncyBoYXBwZW4gaWYgSSBkb24ndCBh
ZHZlcnRpc2Ugb25lIG9mIHRob3NlIGl0ZW1zPyBPciBkbyB5b3UganVzdCANCj4gbWVhbiAidGhl
IGZvbGxvd2luZyBpbmZvcm1hdGlvbiBpcyBhZHZlcnRpc2VkLi4uIj8NCj4NCj4gW0hhb21pYW5d
IEkgZmVlbCB3ZWlyZCBpZiByZXBsYWNlICdzaG91bGQgYmUnIHdpdGggJ2lzJywgYXMgeW91IGNh
bm5vdCANCj4gc3VwcG9ydCBzb21lIGFwcGxpY2F0aW9uL2ltcGxlbWVudGF0aW9uIChyYXRoZXIg
dGhhbiBkbyBiYWQgdGhpbmdzKSBpZiANCj4geW91IGRvbid0IGFkdmVydGlzZS4uLiBIb3cgYWJv
dXQgZm9sbG93aW5nIGNoYW5nZT8NCj4NCj4gT0xEDQo+ICAgIEhlbmNlLCBpbiBvcmRlciB0byBz
dXBwb3J0IGFsbCBwb3NzaWJsZSBhcHBsaWNhdGlvbnMgYW5kDQo+ICAgIGltcGxlbWVudGF0aW9u
cyB0aGUgZm9sbG93aW5nIGluZm9ybWF0aW9uIHNob3VsZCBiZSBhZHZlcnRpc2VkIGZvcg0KPiAg
ICBhIGZsZXhpLWdyaWQgRFdETSBsaW5rOg0KPiBORVcNCj4gICAgSGVuY2UsIGluIG9yZGVyIHRv
IHN1cHBvcnQgYWxsIHBvc3NpYmxlIGFwcGxpY2F0aW9ucyBhbmQNCj4gICAgaW1wbGVtZW50YXRp
b25zIHRoZSBmb2xsb3dpbmcgaW5mb3JtYXRpb24gaXMgcmVxdWlyZWQgdG8gYmUgDQo+IGFkdmVy
dGlzZWQNCj4gICAgZm9yIGEgZmxleGktZ3JpZCBEV0RNIGxpbms6DQoNCldlbGwsIHRoYXQncyBz
dGFydGluZyB0byBmZWVsIGxpa2UgYSBTSE9VTEQgb3IgYSBNVVNULiBUaGF0IGlzIHRvIHNheSwg
c29tZSBhcHBsaWNhdGlvbnMvaW1wbGVtZW50YXRpb25zIHdpbGwgbm90IHdvcmsgaWYgeW91IGRv
bid0IGFkdmVydGlzZSB0aGVzZSB0aGluZ3MsIHNvIGlmIHlvdSdyZSBub3QgZ29pbmcgdG8gYWR2
ZXJ0aXNlIG9uZSBvciBtb3JlIG9mIHRoZW0sIHlvdSdkIGJldHRlciBrbm93IHdoYXQgeW91J3Jl
IGRvaW5nIGFuZCB1bmRlcnN0YW5kIHRoZSBjb25zZXF1ZW5jZXMuIA0KVGhhdCdzIHRoZSAyMTE5
IGRlZmluaXRpb24gb2YgU0hPVUxELiBPbiB0aGUgb3RoZXIgaGFuZCwgaWYgaXQncyByZWFsbHkg
YWx3YXlzIHJlcXVpcmVkIGJlY2F1c2UgeW91IHJlYWxseSBoYXZlIHRvIHN1cHBvcnQgYWxsIG9m
IHRob3NlIGFwcGxpY2F0aW9ucy9pbXBsZW1lbnRhdGlvbnMsIGFuZCB0aGVyZSBhcmUgbm8gZ29v
ZCByZWFzb25zIHRvIGZhaWwgdG8gYWR2ZXJ0aXNlIGFueSBvZiB0aGVzZSB0aGluZ3MsIHRoZW4g
dGhhdCdzIGEgTVVTVC4NCg0KQXMgSSBzYWlkIGJlZm9yZSwgSSdtIHNvbWVvbmUgd2hvIGRvZXNu
J3QgbGlrZSBwdXR0aW5nIGluIE1VU1RzIGFuZCBTSE9VTERzIChJJ3ZlIGV2ZW4gd3JpdHRlbiBw
cm90b2NvbCBkb2N1bWVudHMgd2hlcmUgdGhleSBuZXZlciBhcHBlYXIpLCBidXQgaWYgeW91IHJl
YWxseSBtZWFuICJyZXF1aXJlZCIgb3IgInJlcXVpcmVkIHVubGVzcyB5b3Uga25vdyB3aGF0IHlv
dSdyZSBkb2luZyIsIEkgc2VlIG5vIGhhcm0gaW4gcHV0dGluZyB0aGVtIGluLg0KDQpwcg0KLS0g
DQpQZXRlIFJlc25pY2sgPGh0dHA6Ly93d3cucXVhbGNvbW0uY29tL35wcmVzbmljay8+DQpRdWFs
Y29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSArMSAoODU4KTY1MS00NDc4DQo=


From nobody Sun Feb 12 19:13:27 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C521295CA for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2017 19:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6p9Fd9aOQeP for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2017 19:13:21 -0800 (PST)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551AB1295B8 for <gen-art@ietf.org>; Sun, 12 Feb 2017 19:13:21 -0800 (PST)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-09v.sys.comcast.net with SMTP id d742chhTAODBvd74qcPaUD; Mon, 13 Feb 2017 03:13:20 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-03v.sys.comcast.net with SMTP id d74ncX3wGAjV2d74ocTEdC; Mon, 13 Feb 2017 03:13:19 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1D3DHXd028897; Sun, 12 Feb 2017 22:13:17 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1D3DG6o028894; Sun, 12 Feb 2017 22:13:16 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Charlie Perkins <charles.perkins@earthlink.net>
In-Reply-To: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net> (charles.perkins@earthlink.net)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 12 Feb 2017 22:13:16 -0500
Message-ID: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfBTClhHcg8kU70LEEhc9rVMAWPpsRcs1E/x+FAUazwjqoreRWMCkvgfT1wS+L9lve2zQsI6Ba4OQbdCytoLFFiwUPVsxYh/J1gMb28E/aqkTcsac86s0 vqmK/MMN4by2jBEoAejfVmfw/PApFXPVe/ThpB+2Kh0xFNZ+LoaTMSs96oPn/W/hB2UPknUDXn+PU8A/0nmXA+avnTSNoHvc1ABuVt3PDacUQgNPyvVx/SWv 9GM3V3S3gdkGDN5/AHBUFaReexK/KlD9SYFdKrTwC0ftNJ74axLNkNTZ0tdFZMqt
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1cojKS2eYQ5AMzGiTXyR0Rlluag>
Cc: draft-ietf-dmm-4283mnids.all@ietf.org, gen-art@ietf.org, ietf@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 03:13:23 -0000

Charlie Perkins <charles.perkins@earthlink.net> writes:
> > Are there any other types "in common use"?
> 
> I will add some text according to your suggestion.  My criterion for 
> whether the identifier type was included in the document was whether or 
> not anyone had asked for it to be included.

A good criterion -- if it's commonly used, likely someone would have
asked.

> > - NAI (type 1) is defined by 4283.
> > - Fully Qualified Domain Name (FQDN) seems not to be specified
> > - International Mobile Station Identifier (IMSI) (type 3) is defined
> >   in this draft
> > - Mobile Subscriber Number (MSISDN) seems not to be specified
> 
> It is not the jurisdiction of the MNIDs document to specify these 
> identifiers, but citations for the specifications are located elsewhere 
> in the document.  I will also include those citations here.

What I was noting was that 4283 says:

   Mobile IPv6
   nodes need the capability to identify themselves using an identity
   other than the default home IP address.  Some examples of identifiers
   include Network Access Identifier (NAI), Fully Qualified Domain Name
   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
   Subscriber Number (MSISDN).

but that taking 4283 and this document together, there is no way to
specify FQDN or MSISDN as MN identifiers.  If in practice, people don't
use either of those, then the situation is OK, though 4283 is
inaccurate.  But if people do use FQDNs or MSISDNs as MN identifiers,
should those be added to this document?  (I can't find them specified
elsewhere.)

> > 2. Is it intended to have an IMEI identifier type?  The introduction
> > mentions an IMEI type, but there is no specification for it, nor is
> > there an identifier type number assigned for it.

> I don't know why this happened, but I am happy to include an identifier 
> type for IMEI as well as a citation for it.  Thanks for catching this 
> and looking through the archives!

I'm not saying, "Add it because I think it's a good idea to use IMEIs.",
I'm saying, "Your introduction says that you define an MNID type for
IMEIs, but you don't."  Perhaps there is no need for IMEIs, but in that
case, the introduction needs to be edited.

> > 3. The definition of identifier types for both EUI-48 and EUI-64
> > suggests that it might be desirable to define an identifier type for
> > arbitrary hardware (link-level) addresses.  It seems that the natural
> > differentiator for that purpose is the "hardware type" used in ARP,
> > so
> > a EUI-48 address would be represented as

> Actually, I am O.K. either way on this matter.  However, at this point 
> in time it does not seem that we are likely to see any other link 
> hardware address types to be used as MNIDs.

I agree with you there, although I wouldn't be entirely surprised if a
new mobile network introduced a new link-layer address.  But there
doesn't seem to be much value in making the change I suggested, other
than for generality.

> There is a sort of "hidden" disadvantage to long names, especially for 
> tiny devices using constrained link layers.  Namely, a longer name makes 
> it more likely to require lower-layer fragmentation.  I'm not sure that 
> it should be the job of a layer-3 mobility entity to parse URNs and 
> determine if two different flavors are supposed to be equivalent.
> 
> Other than that, I don't have any real objection to reorganizing the 
> namespace, but I'd like some additional confirmation that it's a good idea.

There are a couple of reasons I like this idea.

One is that EPC seems to have a policy of providing a URN form for all
of the identifier classes it defines.  Making a single URN MNID type
means that you've incorporated all future classes of identifier that EPC
defines.

A single URN MNID type would incorporate any of the defined URN
namespaces that turn out to be useful for anybody.  This isn't so
interesting for really large deployments, since they could ask for a new
MNID type, but experimental or small-scale deployments may want to
define their own identifiers, and URNs provide several convenient ways
to do that.

It removes a certain amount of redundancy, in that each RFID class now
has three representations, for a total of 20 MNID types, whereas they
could all be collapsed into one MNID type.

The negatives I see are:

Some URN schemes do not have a unique representation as a character
string.  In practice, this is combated by either (1) Code that handles
URNs of arbitrary namespace copies and compares them as character
strings.  Users of such systems know to write URNs that have multiple
representations in a canonical form.  Or, (2) Code that handles one or a
small fixed set of URN namespaces knows the canonicalization/comparison
rules for those namespaces.  Generally, using these processes doesn't
cause problems in practice.  I expect that whatever receives the MNID
and looks it up in appropriate databases would not be a constrained
device, so it could process URNs carefully.

If the link layer is constrained, longer identifiers may require
fragmentation.  Changing a 96-bit binary representation into a URN seems
to add something like 40 octets, given the examples I've found online.
OTOH, it seems that the MNID is only transmitted when attaching to a
network, and so having that one packet require extra work doesn't seem
to be much of a penalty.

The all-URN ides envisions embedding IMSI and possibly MSISDN into the
gsma URN namespace.  (IMEI is already embedded as urn:gsma:imei:...)
That would take additional specification, although I don't see that
being controversial.  (Andrew Allen <aallen@blackberry.com> would be a
good contact for doing this.)

> > 5. Regarding the encoding of a string of digits into octets, it is
> > stated that "The last digit MUST be zero padded, if needed, for full
> > octet size."  This seems very unwise unless there is a 3GPP decree
> > that if a zero is appended to a valid IMSI, the resulting string is
> > never a valid IMSI.  Instead, I would specify that padding is by
> > filling the low-order 4 bits of the final octet with 0xF.  That
> > ensures that the encoding can be uniquely decoded into an IMSI.
> 
> I am O.K. with this.  I need to go find out where I got that language 
> from, because I don't think I was the person who crafted it.

I suspect this is really an editorial mistake, but I had to treat it as
technical because I couldn't rule out that it was a design question.

> > 6. There are four types of DUID specified, each with a distinct MNID
> > value.  However, DUIDs contain an initial two-octet type field which
> > distinguishes the various types of DUID, so providing them with
> > distinct MNID values is redundant.
> >
> > Distinguishing the types and allowing only four of them to be used as
> > MNIDs seems to be contrary to the philosophy of DUID construction (RFC
> > 3315 section 9):
> >
> >     Clients and servers MUST treat DUIDs as opaque values and MUST only
> >     compare DUIDs for equality.  Clients and servers MUST NOT in any
> >     other way interpret DUIDs.  Clients and servers MUST NOT restrict
> >     DUIDs to the types defined in this document, as additional DUID types
> >     may be defined in the future.
> >
> > Of course, MNID isn't a DHCP operation, so it isn't subject to those
> > requirements, but I expect that devices will use the same DUID for
> > both mobile identification, and we don't want mobile identification to
> > restrict future developments of DHCP.
> >
> > I think this specification must treat DUIDs as opaque and use only
> > one
> > MNID type that allows all types of DUIDs as values.
> 
> Thanks for this observation.  I will make the corresponding revisions to 
> the text.

Give that there has been only 4 types of DUID defined in 13 years, I
don't expect much need for extensibility, but it seems to me that if
devices take their MNID from their platform's DHCP implementation,
there is a risk that the protocol will fail if someone uses a
proprietary/experimental DUID type.

> > Editorial issues:

Trimming everything I have no further comment on:

> > Abstract
> >
> >     Additional Identifier Types are proposed for use with the Mobile
> > Node
> >     Identifier Option for IPv6 (RFC 4283).
> >
> > s/proposed/defined/
> > This document will define the new types (once it is approved)!
> 
> O.K. with your modification.  The document just defines numbers for the 
> types, not the types.

True...  So really "Additional Identifier Type Numbers are defined for
use ..."

> > --
> >
> >     For each RFID scheme except GID, there are two variations: a 64-bit
> >     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID has
> >     only a 96-bit scheme.  Within each scheme, an EPC identifier can be
> >     represented in a binary form or other forms such as URI.
> >
> > The text uses "scheme" to mean the distinction between encoding
> > systems (GID, SGTIN, etc.) and and also to mean the distinction
> > between the 64-bit and 96-bit variations.  This ambiguity is unwise.
> > It matters here, because you say "within each scheme ... can be
> > represented in a binary form or ... URI".  Which meaning of "scheme"
> > are you using here?  I thought you meant the second meaning when I
> > first read the paragraph, but after reading external documents about
> > EPC, I now understand that that last sentence uses "scheme" to in the
> > first sense.
> >
> > You need to be clearer here that there are three representations
> > used,
> > 64-bit binary, 96-bit binary, and URI (URN, actually), and
> > representation is orthogonal to the seven RFID schemes, with the
> > exception that RFID-GID does not have a 96-bit binary representation.
> 
> This is a good idea.  How about the following:
> 
> >    For each RFID scheme except GID, there are three representations:
> >     - a 64-bit binary representation (for example, SGLN-64)
> >     - a 96-bit binary representation (SGLN-96).
> >     - a representation as a URI

That's close, but it doesn't assert the representations for GID.
Better:

    For each RFID there are three representations:
     - a 64-bit binary representation (for example, SGLN-64)
       (except for GID)
     - a 96-bit binary representation (SGLN-96).
     - a representation as a URI (a URN, actually)

(Though all of this discussion can be removed of the binary
representations are removed in favor of the URN representation.)

> I didn't originate the use of URI for the non-binary representation. The 
> EPC document has the following language:
> 
> > All categories of URIs are represented as Uniform Reference Names 
> > (URNs) as defined by [RFC2141], where the URN Namespace is epc.
> 
> If I were to change it to URN, then I would have to go into some detail 
> about why this document somehow disagrees with the EPC-Tag-Data 
> document.  Do you think that is necessary?

We do want to stay aligned with EPC, otherwise there would be chaos.
And technically, all URNs are URIs.  But approaching the subject from
the IETF, it makes a lot more sense that RFID schemes are represented as
URNs rather than general URIs.  It seems to me to be quite sufficient to
notify the reader in some appropriate place that these URIs are URNs.
See the last line of the text I suggested above for one way to do it.

> > I'm assuming that the Tag Data standard unambiguously defines the
> > serialization of the binary representations as a sequence of octets.
> > If it does not, this document MUST do that, or you will have an
> > endless nightmare of byte-order problems.
> 
> I read through some relevant text in the EPC-Tag-Data document and it 
> seems O.K. to me, but nontrivial and it relies on digging through other 
> even more arcane documents to be absolutely sure.  I am pretty sure that 
> the IETF document should not get into the business of augmenting the 
> standards already in place from the external SDOs.

Oh, yes, we don't want to duplicate EPC's work.  I just wanted to know
that you've checked that EPC does define a sequence of octets, rather
than only a sequence of *bits*, which would leave the ordering of the
bits within the octets unspecified.

> > 4.  Descriptions of MNID types
> >
> > Identifier ownership is a general concern -- it's worth mentioning
> > for
> > each type of identifier where the assigner of the identifier obtains
> > delegation.  For an EUI, I expect the reader will assume that it's an
> > EUI assigned to the device under IEEE rules, and similarly for RFID
> > and 3GPP identifiers.  But for DUID identifiers, it's less clear.
> > I'm
> > guessing that the DUID is one that is, or could be, used by the
> > device
> > for DHCP purposes.  For IPv6 addresses, it's even less clear, since
> > the IPv6 architecture doesn't assume that the association of
> > addresses
> > with devices is permanent.
> 
> I hope that this document does not have to specify allocation procedures 
> for the MNIDs.  It seems to me that if a system designer wants to use 
> one of the MNID types, that person will already know about how to 
> request the allocation and would not need to rely on the MNIDs document 
> for that information.  Plus it's really out of scope.  This document was 
> always intended to be a simple tabulation of types already in use 
> elsewhere and enabling IETF mobility management protocols to use the 
> most natural identifier available for a mobile node.  I hope that citing 
> the defining documents for the identifier types will be enough to 
> satisfy that.

OK, I can agree with you there.  The only identifier which doesn't seem
to have a "natural" ownership scheme is IPv6 addresses; I think of IPv6
addressed as being assigned to a device every time it is initialized,
rather than being a way to identify the device.  But you address that in
the item below.

> > 4.1.  Description of the IPv6 address type
> >
> > It would be good if the document described what the semantics of this
> > ID are.  Yes, it's a unicast IPv6 address, but what is the connection
> > between that address and the device?  I suspect the connection is
> > "the
> > device has been configured to expect that it will be assigned this
> > address as a long-term interface address", but there are other
> > possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
> > prefix (there are plenty of them!) and then assigning addresses out
> > of
> > it simply to create a sequence of unique identifiers for devices, but
> > not using those addresses on packets.
> >
> > Then again, perhaps you want to allow flexibility.  But in any case,
> > I
> > think you need to specify what the rules are for what address is
> > associated with what device.
> 
> As far as I have understood, the unicast IPv6 address in use as a MNID 
> is already assigned to the device.  I have not heard anyone asking for 
> this to be an address for future assignment.  I'll try to make that 
> clear in the text.

OK, if that's the case, then the usage is clear, as is how the device
obtains ownership of an address.

> > 4.2.  Description of the IMSI MNID type
> >
> > What does "in network order" mean here?  As far as I know, there is
> > no
> > defined "network order" for 4-bit quantities, only for dividing
> > integers into octets and placing sequences of bits into octets.  I
> > assume you mean that in any octet, the high-order 4 bits are the
> > first
> > digit and the low-order 4 bits are the second digit, but I think you
> > need to state that explicitly.
> 
> I probably lifted that language directly from the IMSI spec, but I can 
> make further clarification according to your suggestion.

It's likely that in the context of the IMSI spec that "network order"
means high-to-low for all sizes quantities, but I've not seen that used
in IETF context, so it's probably worth clarifying just to be thorough.

> > 4.9.  Description of the RFID types
> >
> > This section needs to be revised.  It provides a lot of detail about
> > the RFID types, but it's not enough detail for a reader who doesn't
> > understand RFID to learn how any particular RFID scheme works.  E.g.,
> > the first paragraph says that GID contains three fields in the first
> > sentence, and that it contains four fields in the third sentence.
> > Despite this, the description isn't enough to allow the reader to
> > construct GID identifiers manually.
> >
> > On the other hand, readers who already understand the RFID schemes
> > will find this text redundant.
> >
> > I think that almost all of this text can be replaced by references to
> > the EPC documents, since these identifiers are opaque from the point
> > of view of mobile identification.
> 
> Here I am at a loss, because I was specifically requested to insert some 
> descriptive but not normative text.  I will ask the person who made the 
> request to provide their feedback on the mailing list.  For myself, I am 
> more than happy to delete the text.

OK, if people have asked for descriptions, I can see the value in that.
But you might want to check that your phrasing makes sense to someone
who isn't already familiar with the EPC schemes.

> > 5.  Security Considerations
> >
> > The base MNID specification, RFC 4283, gives these security
> > considerations (sec 4), which ought to be referenced and probably
> > summarized in this section:
> >
> >     Moreover, MNIDs containing sensitive identifiers might only be used
> >     for signaling during initial network entry.  Subsequent binding
> >     update exchanges might then rely on a temporary identifier allocated
> >     during the initial network entry, perhaps using mechanisms not
> >     standardized within the IETF.  Managing the association between long-
> >     lived and temporary identifiers is outside the scope of this
> >     document.
> >
> > What is the meaning of the word "might" in paragraph 3?  I suspect
> > that the purpose is to qualify this paragraph with "One way to
> > address
> > these vulnerabilities is to only use MNIDs containing ...".  But if
> > that is the meaning, that expanded wording should be used.  Otherwise
> > the text reads as if it is hypothetical.
> 
> This text was meant to be generally descriptive, so that people wanting 
> to include the Mobile Node Identifier Option with the relevant MNIDs 
> could understand how the identifiers are actually used in various 
> circumstances.  I could replace constructions using "might" with "in 
> some specifications" or "in some situations" if needed.  Is it also 
> necessary to include citations to the relevant documents of the external 
> SDO?

I'd definitely prefer some other term than "might".  I'm not sure why,
but I think that it's because "might" isn't used much in specifications

If the external documents show how MNIDs will be used, and if that
context shows why the security problems are small, then I'd definitely
reference them.

One point that is not clear to me.  The above quoted paragraph suggests
that MNIDs are only transmitted during initial network entry.  But
reading it again, I'm led to guess that they are currently also used for
"binding update exchanges".  And you are suggesting that their use in
binding update exchanges could be eliminated by using temporary
identifiers?

If the first case is true, you can make the statement more definitive
as simply:

     Currently, MNIDs are only be used for signaling during initial
     network entry. [external reference]

If the second case is true, you want to make it clearer that the current
risks are (slightly) higher:

     Currently, MNIDs are only be used for signaling during initial
     network entry and binding update exchanges. [external reference]
     Future work could ensure that MNIDs are only be used for signaling
     during initial network entry by having subsequent binding update
     exchanges rely on a temporary identifier allocated during the
     initial network entry, perhaps using mechanisms not standardized
     within the IETF.  [perhaps delete that last phrase as not really
     adding anything?]  Managing the association between long-lived and
     temporary identifiers is outside the scope of this document.

Dale


From nobody Sun Feb 12 21:30:38 2017
Return-Path: <marka@isc.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB09129480; Sun, 12 Feb 2017 21:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQK6uAo1HHLB; Sun, 12 Feb 2017 21:30:30 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 196FE12948C; Sun, 12 Feb 2017 21:30:29 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id D8E5324AE0B; Mon, 13 Feb 2017 05:30:25 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 74979160043; Mon, 13 Feb 2017 05:30:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4B473160067; Mon, 13 Feb 2017 05:30:24 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vsXD7j-Owyzc; Mon, 13 Feb 2017 05:30:24 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 640D1160043; Mon, 13 Feb 2017 05:30:23 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BE00D6390011; Mon, 13 Feb 2017 16:30:18 +1100 (EST)
To: otroan@employees.org
From: Mark Andrews <marka@isc.org>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com> <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
In-reply-to: Your message of "Sat, 11 Feb 2017 23:59:20 +0100." <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Date: Mon, 13 Feb 2017 16:30:18 +1100
Message-Id: <20170213053018.BE00D6390011@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/raaYG927B1zOm3QqzNxp3vOBlco>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, Gen-ART <gen-art@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 05:30:32 -0000

In message <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>, otroan@employees.org writes:
> > How does this work for UDP?
> >
> > Sending packets no larger than 1280 bytes is always an option, and in
> > the case of UDP-based request-response protocols such as DNS that do
> > not have connection state, it may be the only feasible option.
>
> Yes, but DNS tend to use IP fragmentation that suffers an order of
> magnitude worse fate than ICMP messages. ;-)

Yep.  Idiots with firewalls break otherwise working protocols.
 
> > Anyway, the point I was trying to make was not to argue about better
> > or worse methods but rather to dispute the statement that PMTUD is
> > essential for avoiding black holes. I don't believe that it is. The
> > draft itself explicitly says that "IPv6 nodes are not required to
> > implement Path MTU Discovery."
>
> That's correct. But it then must restrict itself to sending packets at
> the minimum MTU size.
> You cannot implement RFC2473 (IP in IP) without PMTUD for example.
>
> [...]
>
> > What criteria for advancement to IS do you think are not met by this
> document?
> >
> > I do not dispute that the document has met the formal criteria for IS
> in Section
> > 2.2 of RFC 6410. I would argue, however, that its failure to provide a
> complete
> > solution for environments where delivery of ICMP messages is not assured
> > constitutes a significant technical omission for today's Internet, and
> I note
> > that per RFC 2026 Section 4.1.1, even a PS "should have no known
> technical
> > omissions." What I am asking the community, and the IESG, is whether it
> is
> > wise to advance a document with known technical omissions; it seems to
> me
> > that the Gen-ART reviewer has raised much the same question.
>
> For IPv6, because of the removal of fragmentation by intermediate nodes,
> failure to provide a path where ICMP message delivery is assured is a
> considered a configuration error.
>
> From
> http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis
> .pdf:
>
> "We observed that for IPV4 between 4% and 6% of the paths between the
> vantage points and our experimental setup filter ICMP PTB packets. For
> IPV6 this was between 0.77% and 1.07%. Furthermore, we found that when
> IPV4 Domain Name System (DNS) servers do not act on the receipt of ICMP
> PTB packets, between 11% and 14% of the answers from these DNS servers
> are lost. For IPV6 DNS servers this was between 40% and 42%. Lastly, we
> found that for IPV4 approximately 6% of the paths between the vantage
> points and our experimental setup filter IP fragments. For IPV6 this was
> approximately 10%."

There isn't a lot a DNS server can do unless the host OS records
the path MTU for that destination.  I suppose theoretically it could
listen for PTB then set IPV6_USE_MIN_MTU for destinations that it
has received a PTB for but that is not optimal.  Unfortunately the
OPT/TSIG/SIG records are towards the end of the packet so it generally
isn't possible to resend the response that triggered the PTB.

> From that data it looks like we have been quite successful. ICMPv6 PMTUD
> is treated a lot better (about a 1% loss) than its IPv4 counterpart.
> Unless better data exists I tend to conclude that the claim that the
> Internet breaks PTUMD for IPv6 is a myth.
>
> Fragmentation on the other hand...

Fragmentation failing is basically gun, foot, shoot by blocking all
fragments at the firewall.  Nameservers don't need to support
fragmentation for request traffic which is what at least one of the
fragmentation is broken tested.  Firewall could reassemble or be
more selective about the fragments they drop.

It doesn't help that there is this myth that IPv6 packets will never
be fragmented.

Mark

> And please don't get me wrong, I think we have a big job to do on MTU
> issues. I just don't see data showing that PMTUD isn't doing what it was
> designed to do.
>
> Best regards,
> Ole
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb 13 00:41:39 2017
Return-Path: <lars@netapp.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8406D129558; Mon, 13 Feb 2017 00:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level: 
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3bSbK8zGsBz; Mon, 13 Feb 2017 00:41:36 -0800 (PST)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5ECA129551; Mon, 13 Feb 2017 00:41:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,155,1484035200";  d="asc'?scan'208";a="175583806"
Received: from vmwexchts01-prd.hq.netapp.com ([10.122.105.12]) by mx143-out.netapp.com with ESMTP; 13 Feb 2017 00:28:49 -0800
Received: from VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) by VMWEXCHTS01-PRD.hq.netapp.com (10.122.105.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 00:36:34 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Mon, 13 Feb 2017 00:36:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=g/4R4Dzx3VmQfnmcvEhSkC1KORKM2cWxckqac24/How=; b=OCybobcpKhrgaOXSyNz45cPN8ZUP+utpBy7uHKV/fWq6Xb5VDP+BkUtvpuIO1r71ENm7lyoEDu7sNxIYwBndGScIvsD/rCulR7Be1Aap/vBzXcjQq4vN5SBHZrCVPySsEFKyWx/OUq0Lngn95h0p8+Y+UzaRp+EOjMHHkgPKFuA=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1154.namprd06.prod.outlook.com (10.160.157.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Mon, 13 Feb 2017 08:36:33 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0888.030; Mon, 13 Feb 2017 08:36:33 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHShB9acsjWwaSyJ0WIyoGy+ZdFEqFjW9oAgANEb4A=
Date: Mon, 13 Feb 2017 08:36:33 +0000
Message-ID: <8C4F2A09-AD95-4B0E-9899-AF739E2BE7D8@netapp.com>
References: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com> <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
In-Reply-To: <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: a8cc0b55-e175-4707-d41a-08d453eb6a6f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1154; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1154; 7:ACULdsGakaEo4oMqoKzIrHCJPJO/RTlz+I/RJJ7YtIy1By9u+3aDYgPJZZbtm4MqXImHczLh1t+tp2nZT/pG4Ukm9SkmaR2kLTCp7eGgQNDFctAYdEJ8W0bMVKxmDstscKMZatgqGAMfLSW4me17CUaGEfmMB1YtiVaVj5nBgpxTWcnyWKiTuIEfzb3O4bGcrToOY6WlKpK84Y17JGqU4++MeiTeyLV+7tGHHtVNfafF8P3l099FPylOZtFCYolKNw22RIW1a1KrWXuaozUbyNB9iJDyjRV/5OKiTiS70VvKYb4x49Jt/ZVQ8JLDLjCcqzb9GP5lemgsAMg5/X1e47LBEYpxfjaESqwzv2u5CSkdF4YD04lot0TCazNsfBZDeHANJMkD2BV0awY1p7621ptvdhuSdqERPbBZV0i/tsNwtliDvYUbJ+E8COc5ZtTAZLovI8WYbnrShcPbpUZfNG3PrDX4QBePJ/ADxLGbUVb6EXXbgUVIaJCQGMvCOtGOignvwriGhfpJxmKP587qJA==
x-microsoft-antispam-prvs: <BN3PR0601MB11542BF7CA678AEA8EE23AD1A7590@BN3PR0601MB1154.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123564025)(20161123555025)(20161123558025)(20161123560025)(20161123562025)(6072148); SRVR:BN3PR0601MB1154; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1154; 
x-forefront-prvs: 02176E2458
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(24454002)(377424004)(189002)(36756003)(53936002)(38730400002)(110136004)(101416001)(77096006)(6116002)(82746002)(6436002)(53546003)(6246003)(102836003)(2900100001)(3846002)(122556002)(2950100002)(189998001)(230783001)(97736004)(6916009)(83716003)(66066001)(4001150100001)(50226002)(25786008)(8656002)(5660300001)(6486002)(68736007)(76176999)(8936002)(86362001)(3660700001)(99286003)(50986999)(3280700002)(57306001)(54906002)(81156014)(8676002)(81166006)(99936001)(6506006)(229853002)(2906002)(105586002)(106116001)(33656002)(7736002)(39060400001)(305945005)(4326007)(106356001)(558084003)(6512007)(92566002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1154; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Feb 2017 08:36:33.1874 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1154
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/O_aVWzQov7ahEExMSVaCf10I2oA>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, "gen-art@ietf.org" <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 08:41:37 -0000

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2017-2-11, at 7:42, Suresh Krishnan <suresh.krishnan@gmail.com> =
wrote:
> How does this work for UDP?

See draft-ietf-tsvwg-rfc5405bis (which is in AUTH48), Section 3.2 =
"Message Size Guidelines".

Lars

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYoXALAAoJEFS1wwm/cMFXxNkQALiBKBPolhYj/Q/4++kLc/ed
eAwp9gcI+0CVMzaRxhsbb8jMTkZWsU4+coQ7LXwGA302L8tqAmcYO9o6HPx0T3bO
eLYbMsombhLRmbyBj9nZiVbvsLWydjBTSaHiWNY6UAwqSA3VYhBev0WWqC4+EKYR
Y0eSUmldufGE1XvSOFSgtj32RAFy/iXXmjIRpwKG0ynao0bI/LwpQStlRbkfMBs1
HnCZdyxbt7H1RD3qsi3lJDE8coTC8YZ9pZh7549NrhHRv4/XWsMQuVll37OIYhIV
7cubHZjNOEP9ZUCgSFhlMLBK1FkukR60KibBGlVl4SEwe4cGRM9f1mu6wSsoAsN1
4nqDKfnpGqZJUZJQMza2v9SCUz2JGldbGMHSHMF4STURnn4TQBy0zbiJeGr4MpEY
Y2mE/JkCFkOAP0BSotO2RPL/6zqjqKr2a3IM4Fz4LKnR55Yvdq0zsb6fBB5+wv39
IpPw+Km7d6IFzopljQq+PafIo0n+KaAohYnDxmeelgDMie60wF33MuvPFlgeXjYc
Un4rfMSfP1s4nDEtJxZTELVrJfHLEX0kMlhi3UxsCkU9NLGKJkbN9DYV4cs402o8
Djf7e8HTRGSRfImOi3JLNyAqGd3oQaql8YgFkhK7DbDft9waonrbeyRdFawpR5w0
qgnps6+pH1SftjWGKsYd
=zv15
-----END PGP SIGNATURE-----

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1--


From nobody Mon Feb 13 06:08:39 2017
Return-Path: <vijay.gurbani@alcatel-lucent.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7622B129582; Mon, 13 Feb 2017 06:08:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani <vijay.gurbani@alcatel-lucent.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148699491344.24997.6536739002535110358.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 06:08:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/is78aEVwwLT7kn9grIS18vPbvLA>
Cc: draft-ietf-grow-mrt-add-paths.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-grow-mrt-add-paths-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 14:08:33 -0000

Reviewer: Vijay Gurbani
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-grow-mrt-add-paths-??
Reviewer: Vijay Gurbani
Review Date: 2017-02-13
IETF LC End Date: 2017-02-15
IESG Telechat date: Not scheduled for a telechat

Summary: Document is ready as a PS.

Major issues: None.

Minor issues: None.

Nits/editorial comments:  None.



From nobody Mon Feb 13 07:31:31 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BA512965A; Mon, 13 Feb 2017 07:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-ILDBiEBV84; Mon, 13 Feb 2017 07:31:20 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54B3912961D; Mon, 13 Feb 2017 07:31:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1DFVJTp041098; Mon, 13 Feb 2017 08:31:19 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1DFVDo5041017 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 13 Feb 2017 08:31:14 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 13 Feb 2017 07:31:13 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Mon, 13 Feb 2017 07:31:13 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, "C. M. Heard" <heard@pobox.com>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHShJFkd1t1l5P4r0CAXezaoK6tiaFk8e4AgAIhCtA=
Date: Mon, 13 Feb 2017 15:31:12 +0000
Message-ID: <f8ce237bd57d4262af37cee5889c1830@XCH15-06-08.nw.nos.boeing.com>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com> <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
In-Reply-To: <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/5hHmOrsvkcL-q-WF2I8mjFVOGEk>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Gen-ART <gen-art@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 15:31:22 -0000

Hi Ole,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.o=
rg
> Sent: Saturday, February 11, 2017 2:59 PM
> To: C. M. Heard <heard@pobox.com>
> Cc: 6man WG <ipv6@ietf.org>; IETF <ietf@ietf.org>; Gen-ART <gen-art@ietf.=
org>; Suresh Krishnan <suresh.krishnan@gmail.com>;
> Stewart Bryant <stewart@g3ysx.org.uk>; draft-ietf-6man-rfc1981bis.all@iet=
f.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> > How does this work for UDP?
> >
> > Sending packets no larger than 1280 bytes is always an option, and in
> > the case of UDP-based request-response protocols such as DNS that do
> > not have connection state, it may be the only feasible option.
>=20
> Yes, but DNS tend to use IP fragmentation that suffers an order of magnit=
ude worse fate than ICMP messages. ;-)
>=20
> > Anyway, the point I was trying to make was not to argue about better
> > or worse methods but rather to dispute the statement that PMTUD is
> > essential for avoiding black holes. I don't believe that it is. The
> > draft itself explicitly says that "IPv6 nodes are not required to
> > implement Path MTU Discovery."
>=20
> That's correct. But it then must restrict itself to sending packets at th=
e minimum MTU size.
> You cannot implement RFC2473 (IP in IP) without PMTUD for example.

Right, but RFC2473 also has other problems, e.g., integrity.

Thanks - Fred

> [...]
>=20
> > What criteria for advancement to IS do you think are not met by this do=
cument?
> >
> > I do not dispute that the document has met the formal criteria for IS i=
n Section
> > 2.2 of RFC 6410. I would argue, however, that its failure to provide a =
complete
> > solution for environments where delivery of ICMP messages is not assure=
d
> > constitutes a significant technical omission for today's Internet, and =
I note
> > that per RFC 2026 Section 4.1.1, even a PS "should have no known techni=
cal
> > omissions." What I am asking the community, and the IESG, is whether it=
 is
> > wise to advance a document with known technical omissions; it seems to =
me
> > that the Gen-ART reviewer has raised much the same question.
>=20
> For IPv6, because of the removal of fragmentation by intermediate nodes, =
failure to provide a path where ICMP message delivery is
> assured is a considered a configuration error.
>=20
> From http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-=
thesis.pdf:
>=20
> "We observed that for IPV4 between 4% and 6% of the paths between the van=
tage points and our experimental setup filter ICMP PTB
> packets. For IPV6 this was between 0.77% and 1.07%. Furthermore, we found=
 that when IPV4 Domain Name System (DNS) servers do
> not act on the receipt of ICMP PTB packets, between 11% and 14% of the an=
swers from these DNS servers are lost. For IPV6 DNS
> servers this was between 40% and 42%. Lastly, we found that for IPV4 appr=
oximately 6% of the paths between the vantage points and
> our experimental setup filter IP fragments. For IPV6 this was approximate=
ly 10%."
>=20
> From that data it looks like we have been quite successful. ICMPv6 PMTUD =
is treated a lot better (about a 1% loss) than its IPv4
> counterpart.
> Unless better data exists I tend to conclude that the claim that the Inte=
rnet breaks PTUMD for IPv6 is a myth.
>=20
> Fragmentation on the other hand...
> And please don't get me wrong, I think we have a big job to do on MTU iss=
ues. I just don't see data showing that PMTUD isn't doing
> what it was designed to do.
>=20
> Best regards,
> Ole
>=20
>=20



From nobody Mon Feb 13 08:55:56 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB011296DD for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2017 08:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKoL68sKladT for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2017 08:55:53 -0800 (PST)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9BD0129565 for <gen-art@ietf.org>; Mon, 13 Feb 2017 08:55:53 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-12v.sys.comcast.net with SMTP id dJuNcCsPt6RIndJurcbXTz; Mon, 13 Feb 2017 16:55:53 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-01v.sys.comcast.net with SMTP id dJuocoNOPgcVOdJuqcaYLc; Mon, 13 Feb 2017 16:55:52 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1DGtnOd013897; Mon, 13 Feb 2017 11:55:49 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1DGtmKN013894; Mon, 13 Feb 2017 11:55:48 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Sri Gundavelli \(sgundave\)" <sgundave@cisco.com>
In-Reply-To: <D4C63E24.2598D8%sgundave@cisco.com>
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 13 Feb 2017 11:55:48 -0500
Message-ID: <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfLBYsvvQpSgsytl+ZkBaSpG8sIpIb+R578s7f49lUIVmj/oCsOqEvGTJnwlhOQ7/rbp+jcGowToziBn3MMJfUMpswQKdPcOUus/aKYzpN7zDiMLm9pYR rQAO2NvrotFI8CEdjXoc3EV/ZF/eXZmRM1AXDu7T5nU80+NV+axvqoGNfiXYefgsRRa2rVGUJJgKk7AgkSHZu8skex9p14dwd7YWgCaJWZ29hZvWqrhE941L bEEkARtbsy3aIpkv6oUiIOiW/TYKS3WPAU8WDmKJNQHlH8Y3p+VQB9NyeKaMR4a6VnjB+5hpwvSJIs01Kd/bCj77Gnlw/djxk9KTN8zTXog=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/kA_Ph2krwpOupTJ45H7PbT4-bCQ>
Cc: charles.perkins@earthlink.net, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 16:55:54 -0000

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> writes:
> When we discussed this issue in the past, the general feedback from
> the WG was that the draft should provide some minimal amount of
> details on the new identifier types, what the identifier is, how the
> identifier is constructed, what is the access technology and a
> reference to the specification that provides that definition. The idea
> is NOT TO provide extensive details on the spec, but to enable a
> reader with some high level details and a pointer to the
> specification. I tend to think the text in the current specification
> just does that. If the text is seen as redundant text, we can
> certainly add a statement saying that the definition for the
> identifier is provided in spec-XYZ and is repeated here for
> convenience. May be other folks in the WG have some views on this.

I take it that the following are typical comments from the WG:

> Comments from 10/11/2015 email:
>
> "Some text on the motivation for defining new Types may be
> helpful. Document is not just standardizing the currently
> in-use/popular identifier types, its also introducing new types are
> not in use. The reasons/interest for defining identifiers that are
> tied to the physical elements of the device (RFID, MAC address ..etc)
> and how it helps in deployment of the technology may be useful. Few
> lines of text will really help."
>
> "I was hoping to see a sub-section for each of the types. We cannot
> standardize a identifier type without providing any explanation on the
> identifier type or the references to the base definitions. This can be
> painful, but I'd have a small section for each of the types. It can be
> 3 line text on the a.) Definition b.) Format c.) Example format d.)
> Reference to the base spec that defines those identifiers."

I can understand these desires, and I agree with following them.

In regard to the first message, it seems to request "The
reasons/interest for defining identifiers that are tied to the physical
elements of the device (RFID, MAC address ..etc) and how it helps in
deployment of the technology may be useful."  As far as I can tell, this
isn't handled in section 4.9 (which is the part I was complaining
about).  And I don't recall if the earlier parts of the draft are
specific about "the reasons/interest" for any of the new types.  I
believe from this discussion that the reason an identifier was included
is that somebody told the authors that they wanted to use the identifier
in question -- and that is quite legitimate.  Perhaps saying it
explicitly in the early parts of the draft would help.

In regard to the second message, it seems to request

    a small section for each of the types. It can be
    3 line text on the
	a.) Definition
	b.) Format
	c.) Example format
	d.) Reference to the base spec that defines those identifiers.

Of course, (d) "reference to base spec" is necessary, and the
sub-sections of 4.9 do that for each format, as does Table 1.

For (a) "definition", the texts in 4.9 proper seem to be fairly good.
E.g.,

   The EPC encoding scheme for SGTIN permits the direct embedding of
   EAN.UCC System standard GTIN and Serial Number codes on EPC tags.  In
   all cases, the check digit is not encoded.  Two encoding schemes are
   specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits).

Based on that alone, I couldn't possibly construct a SGTIN-64 myself,
but I have some idea of the information it contains and the technical
terms to look up to find the real definition of the data items.

However (b) "format" seems to be missing (except in the most abstract
sense) and (c) "example format" seem to be missing entirely.  OTOH, I'm
not sure that the space needed to specify those would be worth the
effort.

Summary:  After thinking about it more, I think it's not worth the
effort to revise 4.9 heavily.  Most of that information is for the use
of people who are familiar with the RFID identifiers and their formats,
and if they are happy with it, there's no reason to change it.

Dale


From nobody Mon Feb 13 13:08:14 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 69141129526; Mon, 13 Feb 2017 13:08:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:08:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/w8pN3F6Kkw_4Ewr_9MvKcGPyscg>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis.all@ietf.org
Subject: [Gen-art] Review of draft-ietf-6man-rfc4291bis-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:08:09 -0000

Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc4291bis-07
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-03-02

Summary:

I have three small points for the group to consider:

1) In editing for this bis document, one bit of text was lost. 
RFC4291 said this in its section 2.4.5:
"Global Unicast addresses that start with
 binary 000 have no such constraint on the size or structure of the
 interface ID field."
Without it, the various places remaining the the document that say
things like "except those that start with the binary value 0000"
such as that appearing in section 2.4 of _this_ document leave
the reason behind the exception a mystery.

2) At the point in the text where the modified EUI-64 format
interface
identifier text was moved to the appendix, this document notes that 
these derived interface identifiers are no longer recommended (end of
2.4.1). Consider repeating that at the first line of the new Appendix
A.

3) Appendix B looks like something groups normally ask the RFC Editor
to
delete. If that was your intent, please add instructions to the RFC
Editor
so they don't have to ask. If you planned to leave it, a summary of
the
changes rather than a chronolog of what draft version changes were
made
in would be much more useful to future readers. (Such a summary would
be welcome in any case.)






From nobody Mon Feb 13 13:10:17 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01C41298C6; Mon, 13 Feb 2017 13:10:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y_t-88jS3QY6; Mon, 13 Feb 2017 13:10:10 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61B6D129584; Mon, 13 Feb 2017 13:10:10 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1DLA9PG049421 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 13 Feb 2017 15:10:09 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: gen-art@ietf.org
References: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <f093a040-6b11-2985-9256-877f1675adea@nostrum.com>
Date: Mon, 13 Feb 2017 15:10:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PJHqDIDCLiEFD7nbPpNWP1qc_JI>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc4291bis-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:10:12 -0000

And the tracker caught this, but to be complete in the archives, the 
Summary should have said
"Ready for publication as an Internet Standard but with nits that should 
be considered before proceeding"


On 2/13/17 3:08 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-6man-rfc4291bis-07
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-03-01
> IESG Telechat date: 2017-03-02
>
> Summary:

>
> I have three small points for the group to consider:
>
> 1) In editing for this bis document, one bit of text was lost.
> RFC4291 said this in its section 2.4.5:
> "Global Unicast addresses that start with
>   binary 000 have no such constraint on the size or structure of the
>   interface ID field."
> Without it, the various places remaining the the document that say
> things like "except those that start with the binary value 0000"
> such as that appearing in section 2.4 of _this_ document leave
> the reason behind the exception a mystery.
>
> 2) At the point in the text where the modified EUI-64 format
> interface
> identifier text was moved to the appendix, this document notes that
> these derived interface identifiers are no longer recommended (end of
> 2.4.1). Consider repeating that at the first line of the new Appendix
> A.
>
> 3) Appendix B looks like something groups normally ask the RFC Editor
> to
> delete. If that was your intent, please add instructions to the RFC
> Editor
> so they don't have to ask. If you planned to leave it, a summary of
> the
> changes rather than a chronolog of what draft version changes were
> made
> in would be much more useful to future readers. (Such a summary would
> be welcome in any case.)
>
>
>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Feb 13 13:42:34 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4643A129954; Mon, 13 Feb 2017 13:42:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:42:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/TQu3OqAo6xwPSxUQOvFR2cu_dXQ>
Cc: draft-leiba-rfc2119-update.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-leiba-rfc2119-update-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:42:29 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-leiba-rfc2119-update-01
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-03-09
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as part of BCP 14.

I personally find the first bullet in the NEW section to be chatty,
and think it could be reduced while strengthening the message, but
enough eyes have been on this that I don't object to it going through
as is.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Mon Feb 13 13:51:46 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EC512998E; Mon, 13 Feb 2017 13:51:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:51:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VhgwJMgTxAdal0vAviAccB39gt4>
Cc: mpls@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:51:40 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-residence-time-13
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-01-17
IESG Telechat date: 2017-03-02

Summary: Ready for publication as PS

Thanks for addressing my comments.
(I still think some discussion about taking arrival and departure time
measurements would be helpful, even if it only said "do it
consistently so you don't indicate jitter that's not really there".)


From nobody Mon Feb 13 14:50:09 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 394BA1299D6; Mon, 13 Feb 2017 14:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BEcGJN6NvDs; Mon, 13 Feb 2017 14:49:57 -0800 (PST)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967EA1299DB; Mon, 13 Feb 2017 14:49:52 -0800 (PST)
Received: by mail-it0-x231.google.com with SMTP id 203so7587045ith.0; Mon, 13 Feb 2017 14:49:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=c++aBm9KTTIH/cU1ME57cMGAvgw3MPr0bsj1sziZvlg=; b=O9otzFfRS2/xIB3QG3fNlSddfaimY6v5QDYyM3U0wmvPM62SBPB3oCIXgBhdY0I1SQ W/s4JftCSwUWZ0/GDIe+0A4a8EOP7Xp92Yy3LdnTVICVhmqFcO/Ui4Q1pW5wt+JpLeKx 2WwbpcIukDdjSNIA/OjtLV3kdpS4VwBSUP9H1SxHvwh22a7KjWSZYfYd/PZuwX3Dd3pI lfmsF4Rb8dX0V60yifV7dBQpAV2DZwzsSHaNzqm6MosT2THMJpb4kAU0IXUvzTMOgolp iNHFzOd1ve9M8zPAv/E5/2h7Ez/vmFgIkxwtQASJd6L3WhkX4Etq8MThOULj8IacLl4x CUHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=c++aBm9KTTIH/cU1ME57cMGAvgw3MPr0bsj1sziZvlg=; b=QQSP4oKPBojxMAC492G+OWsVbbWeHEmlVKPtOky7tWikq18JOsQ+/HRdkKHlRJyrJs QxLXE7ifpbuzvGZGLD9IKNQV0JjbyLVwhS6YJoetl5y76EG4DpROJNJQvX81hpJr7z1o +XBp1+DHUP0LtDJKENdCdDnTq+k7s+jwENTEBw3xcdDj+nT7rVEtcHHis3tKVHO1bg8C laq2/DWzWACcAUSAvyShRSFm6P8wCoUiDAPbToyDARooxxi2+hwvP7NIQ0WsTdQTvHgE fSCW3vcCSalBgF+nsg8gjUWGuKuw6qIYqS7rtiyOuajIiOO9Ax3AWu6eb1otRmDSrTuq omJg==
X-Gm-Message-State: AMke39mb2gN8E1jAXguk1jpLA7aGvBXVpxIMrHiQNt9Et4s03nTGbiBhjuxVbkITkSQmotkUKlKxVcgOJDb66g==
X-Received: by 10.36.65.105 with SMTP id x102mr765168ita.32.1487026191936; Mon, 13 Feb 2017 14:49:51 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Mon, 13 Feb 2017 14:49:51 -0800 (PST)
In-Reply-To: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
References: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 13 Feb 2017 17:49:51 -0500
X-Google-Sender-Auth: H_Pk51nIYvXoqwWsiK2r8mBsybw
Message-ID: <CALaySJJ_2sDviT=N6gf_i34gO2S2xXPw3e+YBS=rcgCMa5zC=w@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Hd0JJP8MtyAolSqJE4VVpNniBJY>
Cc: General Area Review Team <gen-art@ietf.org>, draft-leiba-rfc2119-update.all@ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-leiba-rfc2119-update-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:50:00 -0000

Thanks, Robert, for the review.

Barry

On Mon, Feb 13, 2017 at 4:42 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-leiba-rfc2119-update-01
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-03-09
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Ready for publication as part of BCP 14.
>
> I personally find the first bullet in the NEW section to be chatty,
> and think it could be reduced while strengthening the message, but
> enough eyes have been on this that I don't object to it going through
> as is.
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
>


From nobody Mon Feb 13 16:44:28 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3FE712979D; Mon, 13 Feb 2017 16:44:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 16:44:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8e7li18n9nSYTFeVzov7HNomYuI>
Cc: draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: [Gen-art] Review of draft-ietf-pals-mpls-tp-dual-homing-coordination-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 00:44:23 -0000

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-coordination-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-13
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary:

The document is ready. I have few questions, though, that most likely
are obvious to the document authors and to the WG.

Major issues:

None.

Minor issues:

Not really an issue, but more of thinking out loud. There is no text
in Section 3.2. what happens, say, when PE1 sends DHC+Status TLV and
PE2 sends DHC+Switching TLV both reporting a failure of PW1. I am not
sure if this is a relevant case, but I could expect there can be a
sequence of events that cause these DHC messages to cross between PE1
and PE2?

Nits/editorial comments: 

* The document uses few acronyms without expanding them. Those should
be checked.

* In Section 3.2.  s/table 1 ./Table 1.

*  There are multiple occurrences of "table 1" that should be "Table
1".
   There are multiple occurrences of "figure 5" that should be "Figure
5".
   There are multiple occurrences of "figure 1" that should be "Figure
1".

* Section 3.2. says "..using the DHC message above." Since the message
is quite a bit above I would rewrite this as "..using the DHC message
defined in Section 3.1."

* Section 3.2. protection procedures would greatly benefit
clarity/readability having one or two signaling flow figures assisting
the textual description how the PW failures are signaled between the
PEs (using the DHCs and sometimes assisted with OAM messaging).


From nobody Mon Feb 13 16:46:51 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A9B12944B; Mon, 13 Feb 2017 16:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bvTNlRgVh-cD; Mon, 13 Feb 2017 16:46:44 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0125.outbound.protection.outlook.com [104.47.42.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0FF4129404; Mon, 13 Feb 2017 16:46:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qcsvxrSQxA1TT4f4nKow61qxkar+GLNltUMle5rE1cA=; b=JDL4bh0aLULq/wVSe5phgXuxz0QuzKdCXUGrqdfkhs8MlRJjzRTDJ2fntPI9GBHYwOHXidudISNsZt2hmQmVU2MVMGFBlvOAG7Y8DP6VqUFYt5V9u6/cxTJ8zuuZuQwV6ay2vBvWG0A0k+T+DPVWKERoHzpd3apTzvTwwQb1t1s=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Tue, 14 Feb 2017 00:46:42 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.0888.030; Tue, 14 Feb 2017 00:46:42 +0000
From: Orit Levin <oritl@microsoft.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
Thread-Index: AdKGUyRrA62VAoYfSbKLtLScPr2Ehw==
Date: Tue, 14 Feb 2017 00:46:42 +0000
Message-ID: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=oritl@microsoft.com; 
x-originating-ip: [73.157.101.212]
x-ms-office365-filtering-correlation-id: 69f771db-ccee-42a5-2c66-08d45472f1be
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:CY1PR0301MB2122; 
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2122; 7:2+yEOnJYaNXXaceTcwyxMOzMSTsm+Hky7X7uYt7Y7IRt27yxadfLblBLWtonNzaOpB4W0mXV0KeeQaQr7l25YFIRkJLbewHnPJha96Ry/b6+7fWxmTNA8lEqwCnusH5JTSQ2zi4+R8C7m2McC8p4c+XU6oaflNQgsEUzmOWtTYj+pwsk2C9yB2iGT6Oj8CgtUr/O6zEiJwd4aTYDk64bQq9uAwZE1iaD3lKJADLUqro/VrJDqr/WY9w40TZOu6Rg7kWKbpF3SIYus+LaOgvkftGRORwui27JuqySuvyGHJiBp0vcVIiuA/gLBtNlWAFkLBn0YrR/eZS2yZsSzS7XQVooTAjAoLlLgO8jGGTLxWAkmoXtpU/+hGCReG6n4WiLwk77BP5IMskYZybQUQ3HPBuAY12bI2p+h+qa389Sj3Gv4aPtVfGz3dNOGlw4PFvLdnQyX10TNrtJzjif8S04go6WNc1SMn07gZG/v1wZrokbwAHqScKGzIRB8YpAx5EbR7ysYbX+mkSBtf7lG5jWn+udbu05Vvedin5pDAL7QFU=
x-microsoft-antispam-prvs: <CY1PR0301MB2122680CF37FD6F06B5DF237AD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123558025)(20161123560025)(6072148); SRVR:CY1PR0301MB2122; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2122; 
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(39850400002)(39860400002)(39450400003)(39840400002)(39410400002)(189002)(377424004)(199003)(5005710100001)(6916009)(86612001)(10090500001)(8676002)(33656002)(5630700001)(68736007)(2351001)(106356001)(5660300001)(101416001)(81156014)(81166006)(81003)(10290500002)(2501003)(50986999)(105586002)(54356999)(6436002)(606005)(92566002)(236005)(9686003)(5640700003)(8936002)(25786008)(74316002)(230783001)(8990500004)(7906003)(6506006)(2900100001)(54906002)(55016002)(6306002)(54896002)(66066001)(99286003)(7696004)(7736002)(97736004)(4326007)(122556002)(6116002)(790700001)(102836003)(3846002)(189998001)(86362001)(3280700002)(2906002)(53936002)(110136004)(53946003)(38730400002)(3660700001)(77096006)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2122; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2017 00:46:42.2788 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2122
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/x2Nzui7ZYEjeFmS-ibZdiL8Xu7U>
Cc: "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 00:46:47 -0000

--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.



For more information, please see the FAQ at



<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.



Document: draft-ietf-sidr-delta-protocol-06

Reviewer: Orit Levin

Review Date: 2017-02-13

IETF LC End Date: 2017-01-31

IESG Telechat date: (if known)



Summary:

This draft is basically ready for publication. I only suggest adding the ac=
ronym "RRDP" (in brackets) to the title of the document and replacing the e=
xpression "this delta protocol" with "RRDP" in 3.1 and 3.2.

Thanks,

Orit.



--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"ProgId" content=3D"Word.Document">
<meta name=3D"Generator" content=3D"Microsoft Word 15">
<meta name=3D"Originator" content=3D"Microsoft Word 15">
<link rel=3D"File-List" href=3D"cid:filelist.xml@01D28618.986C09C0"><!--[if=
 gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>120</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false" DefSem=
iHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99" LatentStyleCount=
=3D"374">
<w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"No=
rmal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"he=
ading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"header"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footer"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index heading"/>
<w:LsdException Locked=3D"false" Priority=3D"35" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"caption"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of figures"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope return"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"line number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"page number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of authorities"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"macro"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"toa heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 5"/>
<w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true" Name=3D"T=
itle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Closing"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Signature"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" Name=3D"Default Paragraph Font"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Message Header"/>
<w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"true" Name=3D"S=
ubtitle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Salutation"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Date"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Note Heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Block Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"FollowedHyperlink"/>
<w:LsdException Locked=3D"false" Priority=3D"22" QFormat=3D"true" Name=3D"S=
trong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" QFormat=3D"true" Name=3D"E=
mphasis"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Document Map"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Plain Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"E-mail Signature"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Top of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Bottom of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal (Web)"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Acronym"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Cite"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Code"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Definition"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Keyboard"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Preformatted"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Sample"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Typewriter"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Variable"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal Table"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation subject"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"No List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Contemporary"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Elegant"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Professional"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Balloon Text"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Theme"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Placeholder Te=
xt"/>
<w:LsdException Locked=3D"false" Priority=3D"1" QFormat=3D"true" Name=3D"No=
 Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1"/=
>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2"/=
>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading"/=
>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" QFormat=3D"true" Name=3D"L=
ist Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" Name=3D"Q=
uote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" QFormat=3D"true" Name=3D"I=
ntense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 1=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 2=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 3=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 4=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 5=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 6=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true" Name=3D"S=
ubtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"true" Name=3D"I=
ntense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"true" Name=3D"S=
ubtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" QFormat=3D"true" Name=3D"I=
ntense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" Name=3D"B=
ook Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"TOC Heading"/>
<w:LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table 1"/>
<w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"Plain Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"44" Name=3D"Plain Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table 5"/>
<w:LsdException Locked=3D"false" Priority=3D"40" Name=3D"Grid Table Light"/=
>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Mention"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Smart Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hashtag"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073732485 9 0 511 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-bidi-font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1956404582;
	mso-list-type:hybrid;
	mso-list-template-ids:1772529444 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"tab-interval:.=
5in">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. The General Area Review Team (Gen-ART) reviews all IETF documents being p=
rocessed by the IESG for the IETF Chair.<span style=3D"mso-spacerun:yes">&n=
bsp;
</span>Please treat these comments just like any other last call comments.<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For more information, please see the FAQ at<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArt=
faq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-sidr-delta-protocol-06<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">Reviewer: Orit Levin<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2017-02-13<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2017-01-31<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG <span class=3D"SpellE">Telechat</span> date:=
 (if known)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:<o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is basically ready for publication. I =
only suggest adding the acronym &#8220;RRDP&#8221; (in brackets) to the tit=
le of the document and replacing the expression &#8220;this delta protocol&=
#8221; with &#8220;RRDP&#8221; in 3.1 and 3.2.<o:p></o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Orit.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"mso-ascii-font-family:Calibri;mso-far=
east-font-family:Calibri;mso-hansi-font-family:Calibri;mso-bidi-font-family=
:&quot;Times New Roman&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_--


From nobody Mon Feb 13 17:02:52 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 444EE129497; Mon, 13 Feb 2017 17:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PODCHytKHhxx; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D109129401; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 65so81843752otq.2; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QEBURqKCSBHqeVDeaTyUw/AU/WUunC+sXE3guKdOb60=; b=tdSrl1szKdkNeiL95U3lsHOIa15eoF8P/RiwNVIJ+Krv865bP+8gEqGeNzd7Hgll0L 2RrqaMT8jRH2JiFv20N4F67aOsEvEkNm0Vih8PpUM10vAaeLXLP15E3j6z6kX5h5gLDZ I9HgScV39wk2xnOpagVtELevqCQ/2bb+QhpmwaUkaxLreituqC+HvP/27KVPZEypsK+s uuEqHaZ4Jlb9tYz50yzWb8KV50tc2vfEUklkthyVWCZ2XGHeDqvoB4LBplDn9Hkmu7bW 4BtEljY/3XRzCR9o5kYrCP4BKy7o7ncgms/Se4S/b7xQgekQ/gdJZirEYdMiDXDYuhqt eYug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QEBURqKCSBHqeVDeaTyUw/AU/WUunC+sXE3guKdOb60=; b=um52FlSLtcz33Q+TxuOqPh2qSz2oys2nyh1JCOU+E4oXEHSRqzbnGHGkmeyxgtzck7 pAQamvMMCRvw25AxGHhyAbZufAmibUpMWNB4+NzPsHNfJqNs0CuA1QwOQUWGoIvc2mG4 q6DQ+iAeDcqIRa4QwyY0NDI4ozWqDRV5l7e4NmrMR511rnswKIax+2M2OYKHPWJ4xzWy sZV+cxKjbiK8eDE65/B7sDFPXWakmWDqM4jgXzDQU/PRN/h2hO5oq9EmRNwGkqCqz28g Bx8D6eqAeQ5lGdKcP93dyWGZgSh1Qy354/jgKtxQukTgygrv9bJTYQFiEslfzkyPFsT+ ziIA==
X-Gm-Message-State: AMke39k+86MnzichCRqGvPZ7dL9uj+MZQvMkZyzT3FzX3UipumnqaDA8VE2eqY1eOWIhtOA19EixteSFYEuDyQ==
X-Received: by 10.157.17.5 with SMTP id g5mr16747282ote.118.1487034164910; Mon, 13 Feb 2017 17:02:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Mon, 13 Feb 2017 17:02:44 -0800 (PST)
In-Reply-To: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 13 Feb 2017 17:02:44 -0800
Message-ID: <CA+RyBmUW5GvYefTL2X+b1x7W8xhEpuVQHt0AphOyck51Aig1sg@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a1145009e2b34b20548731f7d
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/K46daHGOqn8acT94EBXJm_Y1Btk>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 01:02:47 -0000

--001a1145009e2b34b20548731f7d
Content-Type: text/plain; charset=UTF-8

Hi Robert,
thank you for your review and patience as we've been working on the
document. The text you've proposed is indeed useful to implementer and I'll
add it with the next update.

Regards,
Greg

On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-mpls-residence-time-13
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-01-17
> IESG Telechat date: 2017-03-02
>
> Summary: Ready for publication as PS
>
> Thanks for addressing my comments.
> (I still think some discussion about taking arrival and departure time
> measurements would be helpful, even if it only said "do it
> consistently so you don't indicate jitter that's not really there".)
>
>

--001a1145009e2b34b20548731f7d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>thank you for your review and patience as w=
e&#39;ve been working on the document. The text you&#39;ve proposed is inde=
ed useful to implementer and I&#39;ll add it with the next update.=C2=A0</d=
iv><div><br></div><div>Regards,</div><div>Greg</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, R=
obert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" =
target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Reviewer: Robert Sparks<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-mpls-residence-<wbr>time-13<br>
Reviewer: Robert Sparks<br>
Review Date: 2017-02-13<br>
IETF LC End Date: 2017-01-17<br>
IESG Telechat date: 2017-03-02<br>
<br>
Summary: Ready for publication as PS<br>
<br>
Thanks for addressing my comments.<br>
(I still think some discussion about taking arrival and departure time<br>
measurements would be helpful, even if it only said &quot;do it<br>
consistently so you don&#39;t indicate jitter that&#39;s not really there&q=
uot;.)<br>
<br>
</blockquote></div><br></div>

--001a1145009e2b34b20548731f7d--


From nobody Mon Feb 13 19:09:47 2017
Return-Path: <chengweiqiang@chinamobile.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 004C6129409; Mon, 13 Feb 2017 19:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHblW8a4_PqV; Mon, 13 Feb 2017 19:09:41 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 282EC129991; Mon, 13 Feb 2017 19:03:51 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec58a27390d0a-8416f; Tue, 14 Feb 2017 11:03:45 +0800 (CST)
X-RM-TRANSID: 2eec58a27390d0a-8416f
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[10.2.51.86]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee458a2738fe69-56c71; Tue, 14 Feb 2017 11:03:44 +0800 (CST)
X-RM-TRANSID: 2ee458a2738fe69-56c71
From: "Weiqiang Cheng" <chengweiqiang@chinamobile.com>
To: "'Jouni Korhonen'" <jounikor@gmail.com>, <gen-art@ietf.org>
References: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
In-Reply-To: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
Date: Tue, 14 Feb 2017 11:03:52 +0800
Message-ID: <011201d2866e$f8f2ec40$ead8c4c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdKGW5D/ERp+i/EBTWC4nomVg8XnNgAExSNA
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8jVDGpoC8kxSW8co16C8bdT5xyY>
Cc: pals@ietf.org, ietf@ietf.org, draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org
Subject: Re: [Gen-art] [Pals] Review of draft-ietf-pals-mpls-tp-dual-homing-coordination-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 03:09:42 -0000

Hi Jouni,
Thank you very much for your careful review and valuable comments.
We authors will fix those issues late.

B.R.
Weiqiang Cheng

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: Pals [mailto:pals-bounces@ietf.org] =B4=FA=B1=ED =
Jouni Korhonen
=B7=A2=CB=CD=CA=B1=BC=E4: 2017=C4=EA2=D4=C214=C8=D5 8:44
=CA=D5=BC=FE=C8=CB: gen-art@ietf.org
=B3=AD=CB=CD: =
draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org;
ietf@ietf.org; pals@ietf.org
=D6=F7=CC=E2: [Pals] Review of =
draft-ietf-pals-mpls-tp-dual-homing-coordination-05

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area =
Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG =
for
the IETF Chair.  Please treat these comments just like any other last =
call
comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-coordination-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-13
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary:

The document is ready. I have few questions, though, that most likely =
are
obvious to the document authors and to the WG.

Major issues:

None.

Minor issues:

Not really an issue, but more of thinking out loud. There is no text in
Section 3.2. what happens, say, when PE1 sends DHC+Status TLV and
PE2 sends DHC+Switching TLV both reporting a failure of PW1. I am not =
sure
if this is a relevant case, but I could expect there can be a sequence =
of
events that cause these DHC messages to cross between PE1 and PE2?

Nits/editorial comments:=20

* The document uses few acronyms without expanding them. Those should be
checked.

* In Section 3.2.  s/table 1 ./Table 1.

*  There are multiple occurrences of "table 1" that should be "Table 1".
   There are multiple occurrences of "figure 5" that should be "Figure =
5".
   There are multiple occurrences of "figure 1" that should be "Figure =
1".

* Section 3.2. says "..using the DHC message above." Since the message =
is
quite a bit above I would rewrite this as "..using the DHC message =
defined
in Section 3.1."

* Section 3.2. protection procedures would greatly benefit
clarity/readability having one or two signaling flow figures assisting =
the
textual description how the PW failures are signaled between the PEs =
(using
the DHCs and sometimes assisted with OAM messaging).

_______________________________________________
Pals mailing list
Pals@ietf.org
https://www.ietf.org/mailman/listinfo/pals




From nobody Mon Feb 13 21:19:57 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9613E1293F2; Mon, 13 Feb 2017 21:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUh48_2MheQo; Mon, 13 Feb 2017 21:19:53 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6EDC12947B; Mon, 13 Feb 2017 21:19:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1487049591; bh=oQL8LJ6JXMs2JvYPClb8bnZ1wKrcwZo0B48V KdgI39Q=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=Go617Mm hd1IapmbNf1rZnFYJ+NFgTLvJvJGZSDcoHvEy7FsM1N5YXHLmAM2txhzKj+ct7vGrcq wxrihlgq/Vq9VKfmJePpsctYVGQ4sT7Qp6PTmJY5mL8gALlqNIwzHRwyOcSxBo2nUXf 6THOOVzSTp4EXwndtsVKCzNTKM8ntZX+iCGfQmPX4aj4qHthAQt0aZjUZPcVbAE/Rbt mY691TloIA9Hm4gW7lA3tO3nPx7zyb0t1hXgbgGnyfyN8Yl+//js/BxfqiVBLXr+2j8 sb9UP1t6X/znzX8cjNTkmE3ZNvqg5itiBvrsYAw+ZnKrlxzmH74L5B0aBJUCRBUIi2w ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=DhvR0B69kFGg/8vEOlRmbCkPxhpttcNF9gEzxBAJRqrecxA14mhLcjDE2PoSUH8ljWjrnRcjEvL1zrh/fkYTgDIrc+F3wRVgLfF5DezlgtaS/uf15ScECCBD/xhIVBDr8dCY1bun12qWZMawMNBSJSjlvtePXzThnXLcKT0kadmRAB6Okn87Qs8x00xXkePANsBHOs/iu9g7oVFgk1AWKZ+93b6ImGd1cIui7JpGX5NFFw4i6xXhhhj7vixAfeb3Up5Jl+y85Wr5idXahLTPUF7Xox9MF8ytdvODpOn/o7lD3cOxafZR8xlN95AkfFQqqMqH/jbEJ5+Mz/uaVqEhgw==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1cdVWX-0005Kc-CJ; Tue, 14 Feb 2017 00:19:33 -0500
To: "Dale R. Worley" <worley@ariadne.com>
References: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <d59427a0-a105-9c10-9de1-86755386d43e@earthlink.net>
Date: Mon, 13 Feb 2017 21:19:27 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7598ed599bdacb1532843c9b011678fe5350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ekimKZy4iCmNllZtmlnrWJg3OD0>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 05:19:55 -0000

Hello Dale,

Follow-up below...

On 2/12/2017 7:13 PM, Dale R. Worley wrote:
>
>> There is a sort of "hidden" disadvantage to long names, especially for
>> tiny devices using constrained link layers.  Namely, a longer name makes
>> it more likely to require lower-layer fragmentation.  I'm not sure that
>> it should be the job of a layer-3 mobility entity to parse URNs and
>> determine if two different flavors are supposed to be equivalent.
>>
>> Other than that, I don't have any real objection to reorganizing the
>> namespace, but I'd like some additional confirmation that it's a good idea.
> There are a couple of reasons I like this idea.
>
> One is that EPC seems to have a policy of providing a URN form for all
> of the identifier classes it defines.  Making a single URN MNID type
> means that you've incorporated all future classes of identifier that EPC
> defines.
>
> A single URN MNID type would incorporate any of the defined URN
> namespaces that turn out to be useful for anybody.  This isn't so
> interesting for really large deployments, since they could ask for a new
> MNID type, but experimental or small-scale deployments may want to
> define their own identifiers, and URNs provide several convenient ways
> to do that.
>
> It removes a certain amount of redundancy, in that each RFID class now
> has three representations, for a total of 20 MNID types, whereas they
> could all be collapsed into one MNID type.
>
> The negatives I see are:
>
> Some URN schemes do not have a unique representation as a character
> string.  In practice, this is combated by either (1) Code that handles
> URNs of arbitrary namespace copies and compares them as character
> strings.  Users of such systems know to write URNs that have multiple
> representations in a canonical form.  Or, (2) Code that handles one or a
> small fixed set of URN namespaces knows the canonicalization/comparison
> rules for those namespaces.  Generally, using these processes doesn't
> cause problems in practice.  I expect that whatever receives the MNID
> and looks it up in appropriate databases would not be a constrained
> device, so it could process URNs carefully.
>
> If the link layer is constrained, longer identifiers may require
> fragmentation.  Changing a 96-bit binary representation into a URN seems
> to add something like 40 octets, given the examples I've found online.
> OTOH, it seems that the MNID is only transmitted when attaching to a
> network, and so having that one packet require extra work doesn't seem
> to be much of a penalty.
>
> The all-URN ides envisions embedding IMSI and possibly MSISDN into the
> gsma URN namespace.  (IMEI is already embedded as urn:gsma:imei:...)
> That would take additional specification, although I don't see that
> being controversial.  (Andrew Allen <aallen@blackberry.com> would be a
> good contact for doing this.)

I am hesitant to replace so many MNID types by a single URN type with 
substructure.  What would you think about replacing the existing 
RFID-*-URI types with a single URN type, but leaving the existing binary 
types?  This gets the benefit you suggest for future extensibility, but 
retains the shorter forms that may often be advantageous.



>>> 5.  Security Considerations
>>>
>>> The base MNID specification, RFC 4283, gives these security
>>> considerations (sec 4), which ought to be referenced and probably
>>> summarized in this section:
>>>
>>>      Moreover, MNIDs containing sensitive identifiers might only be used
>>>      for signaling during initial network entry.  Subsequent binding
>>>      update exchanges might then rely on a temporary identifier allocated
>>>      during the initial network entry, perhaps using mechanisms not
>>>      standardized within the IETF.  Managing the association between long-
>>>      lived and temporary identifiers is outside the scope of this
>>>      document.
>>>
>>> What is the meaning of the word "might" in paragraph 3?  I suspect
>>> that the purpose is to qualify this paragraph with "One way to
>>> address
>>> these vulnerabilities is to only use MNIDs containing ...".  But if
>>> that is the meaning, that expanded wording should be used.  Otherwise
>>> the text reads as if it is hypothetical.
>> This text was meant to be generally descriptive, so that people wanting
>> to include the Mobile Node Identifier Option with the relevant MNIDs
>> could understand how the identifiers are actually used in various
>> circumstances.  I could replace constructions using "might" with "in
>> some specifications" or "in some situations" if needed.  Is it also
>> necessary to include citations to the relevant documents of the external
>> SDO?
> I'd definitely prefer some other term than "might".  I'm not sure why,
> but I think that it's because "might" isn't used much in specifications
>
> ....

I changed the text as follows:

>     Some MNIDs contain sensitive identifiers which, as used in protocols
>     specified by other SDOs, are only used for signaling during initial
>     network entry.  In such protocols, subsequent exchanges then rely on
>     a temporary identifier allocated during the initial network entry.
>     Managing the association between long-lived and temporary identifiers
>     is outside the scope of this document.


I can't remember exactly why this text was added - it was a long time 
ago.  But anyway the main point is to simply mention that there may be 
associations between some of the MNID types that might be important from 
a security standpoint, without meaning to go into examples.

Regards,
Charlie P.


From nobody Tue Feb 14 01:59:49 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783261294C4; Tue, 14 Feb 2017 01:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFxRgFf09we0; Tue, 14 Feb 2017 01:59:44 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1273A129416; Tue, 14 Feb 2017 01:50:41 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id r18so2634974wmd.3; Tue, 14 Feb 2017 01:50:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=mmZ3mA+s6xe9pbQ7REALZWgqnwuowm0B9vu9jbK6CaE=; b=WrTXm9+lv9xun1UBXmS62jZZuC2zlEPyMiSUlklbovWr7Pk0MX1Ml+5PmXkv+0YrnA np2kthZg1wgvYTCf85MR0l2D9JDXro7K3jT1uo2oqoVQpnFmczvmajg9GdcBaMgmSsY9 jj8ZP2sdd7gS9QWL0COQdrGz9/xbQiLchtM194a3I+qsbm4AqbeVZBmzaAhXW7h4zNcB KeJYVb9hokQsoHiMBqWVPsMmTeQAPaL7QcMZKDhR6q2fpgy+N2KW1/7kxCq4JEjfMHrz peKPBT1vRSLitF7qvVcq/89vU85CZi67QYp401+HlOjpvp+VAPZcDYi5BYDiU1r3N9h8 OJ4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=mmZ3mA+s6xe9pbQ7REALZWgqnwuowm0B9vu9jbK6CaE=; b=NZ2erBaFpihXTQCm4HMuTQwvQ8q9bRSxftZK+S/58qvzNAp8k5WrZtp1Zq0qcZd5S5 GuTu2EVKv3v5GykpShetvFpoW1M3CbSLwB8xP9InDB6Rdh/ih321xp0i0VAjQ+SXee1q ggihsDUfK/kBFeDerjtvO2asqdlPW1e31HpiTx03ha60pszgIR3eaWP6l8/fEMPekE+D pveFafEORVJVcvCpDQEJY5Rxyse+6v2ygbilEs2Gdd/kCgOYMIqRnxlf7PEVi6c3S1HB DCaCOlJxqnM8h8ygO94NBTRs1SXHVi71EsGVHCPvnkX1oMdeHBqMANcrIN4U9dTNkw9Q j46w==
X-Gm-Message-State: AMke39kNBC1xLNWohuiueheEtznB6El8hw/r5zG9duNmTZMJczwBxIgODoTY/OjAhjHNPQ==
X-Received: by 10.28.140.140 with SMTP id o134mr2418826wmd.87.1487065839261; Tue, 14 Feb 2017 01:50:39 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 136sm514751wms.32.2017.02.14.01.50.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 01:50:38 -0800 (PST)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
Date: Tue, 14 Feb 2017 09:50:37 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/B7rfsv9tPqqW2UBL6zp0MxhrU6E>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 09:59:46 -0000

Hi Fred

Looks like a good point on RFC4821.

As to you first point remember that the convergence process disrupts the 
traffic flow as it does so, and that this will repeat every 10 mins as 
it tries to re-optimise.

- Stewart


On 10/02/2017 15:38, Templin, Fred L wrote:
> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
> converge to the minimum MTU of all paths in the multipath, and so it is
> still OK to store the MTU in the network layer where it would be shared
> by all flows.
>
> ECMP does present challenges for RFC4821, however. If a first transport
> session discovers a large MTU and shares it with a second transport
> session, the second session may take a very different path where there
> is a smaller MTU and encounter a black hole. IMHO, it might be a good
> idea to file an erratum to RFC4821 explaining how ECMP might cause
> problems if discovered MTUs are shared between sessions.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>> Sent: Friday, February 10, 2017 2:21 AM
>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>
>>
>>
>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>> Stewart,
>>>
>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>> ...
>>>> I wonder if we would best serve both our future and our heritage
>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>> or declared it as historic and wrote a new text from a clean start?
>>> I don't see that. It's a stable, widely deployed, interoperable
>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>> across the Internet.
>> I will not debate whether it is faulty or not, but it seems that in
>> practice the
>> Internet breaks the mechanism. However it breaks it is a way that seems
>> disruptive to some user traffic. The document is really guidance
>> one how hosts might use  ICMP for optimization, and arguable need
>> not be a standard at all.
>>
>> My remark about heritage is that this vintage draft is very much a
>> product of
>> its time, and really needs modernizing, and after modernizing ought to
>> look quite different, and thus maybe we should employ a procedure
>> other than a simple replacement.
>>
>>
>>> ...
>>>> It is concerning that the draft does not talk in any detail about
>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>> the PMTU may be different depending on the transport layer port
>>>> numbers.
>>> Has this problem been analysed for, say, IPv4? And does the real world
>>> contain ECMP setups with different MTUs on different paths?
>> I don't know if anyone has looked. Since the mechanism is
>> self-correcting albeit
>> with some disruption to user traffic it looks to the application and the
>> application
>> user, just like the Internet not working for a few moments.
>>
>> In a well managed SP network there should not be, but neither should there
>> be asymmetric path costs, but there are. The less well manage private
>> networks are less well managed.
>>
>>
>>>> Given that a very large fraction of packets will traverse an MPLS
>>>> network at some point, I am surprised that there is no text talking
>>>> about the importance of providing support for this feature in the
>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>> I don't understand. How does the fact that there might be some MPLS
>>> segments along the path affect end-to-end PMTUD?
>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>> and the
>> PE has to fragment or has to reply with an ICMP error message to support
>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>> result
>> in the right response at the end node.
>>
>> My point is that the draft is silent on the subject, and perhaps it
>> should not be.
>>
>> However your question make me ask a further question. The draft is also
>> silent
>> on NATs. Is there any advice needed for people designing and configuring
>> NATs?
>>
>>>> ======
>>>>
>>>>      If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>      could use the flow id as the local representation of a path. Packets
>>>>      sent to a particular destination but belonging to different flows may
>>>>      use different paths, with the choice of path depending on the flow
>>>>      id.  This approach will result in the use of optimally sized packets
>>>>      on a per-flow basis, providing finer granularity than PMTU values
>>>>      maintained on a per-destination basis.
>>>>
>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>> SB> and thus routers tended to glean information from the packet themselves.
>>> This is future-proofing. Agreed, usage today is limited.
>>>
>>> (But it would be better to call it the Flow Label for consistency with other
>>> recent RFCs.)
>> Well the question is whether it is simply limited today, or broken today
>> in a manner that
>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>> approach
>> is the five-tuple. There is something akin to the flow label being
>> deployed in MPLS. However
>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>> removed) by the
>> service provider and is therefore trusted by the service provider.
>>
>>> I think your other comments are all valuable.
>> Thank you.
>>
>> Stewart
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 07:50:57 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA7E129453; Tue, 14 Feb 2017 07:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkHenFffo_XV; Tue, 14 Feb 2017 07:50:35 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C44B71293DC; Tue, 14 Feb 2017 07:50:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1EFoUI9054338; Tue, 14 Feb 2017 08:50:30 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EFoScr054328 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 08:50:28 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 07:50:28 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 07:50:27 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSw
Date: Tue, 14 Feb 2017 15:50:27 +0000
Message-ID: <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
In-Reply-To: <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/F9lGGt00XL3ZsI2sG4S2qXxIzFM>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:50:39 -0000

HI Stewart,

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 1:51 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; Stewart Bryant
> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Hi Fred
>=20
> Looks like a good point on RFC4821.

OK.

> As to you first point remember that the convergence process disrupts the
> traffic flow as it does so, and that this will repeat every 10 mins as
> it tries to re-optimise.

Yes, you are right. So, even in the case of RFC1981bis it might not be a
good idea to store discovered MTUs in the network layer when there
is ECMP in the path. (Which could be any time at all.)

You briefly mentioned the authorship in your earlier post. As you well
know, the corporate affiliation of two of the authors no longer exists.

Thanks - Fred
fred.l.templin@boeing.com

> - Stewart
>=20
>=20
> On 10/02/2017 15:38, Templin, Fred L wrote:
> > Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in =
the
> > network as long as ICMP PTBs are not blocked. RFC1981bis will eventuall=
y
> > converge to the minimum MTU of all paths in the multipath, and so it is
> > still OK to store the MTU in the network layer where it would be shared
> > by all flows.
> >
> > ECMP does present challenges for RFC4821, however. If a first transport
> > session discovers a large MTU and shares it with a second transport
> > session, the second session may take a very different path where there
> > is a smaller MTU and encounter a black hole. IMHO, it might be a good
> > idea to file an erratum to RFC4821 explaining how ECMP might cause
> > problems if discovered MTUs are shared between sessions.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
> >> Sent: Friday, February 10, 2017 2:21 AM
> >> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <s=
tewart@g3ysx.org.uk>; gen-art@ietf.org
> >> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.=
org
> >> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>
> >>
> >>
> >> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>> Stewart,
> >>>
> >>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>> ...
> >>>> I wonder if we would best serve both our future and our heritage
> >>>> if we declared RFC1981 as historic, and either left the idea there,
> >>>> or declared it as historic and wrote a new text from a clean start?
> >>> I don't see that. It's a stable, widely deployed, interoperable
> >>> mechanism. That is rather orthogonal to the issue that has been raise=
d,
> >>> which is that faulty ICMPv6 filtering blocks it on many, many paths
> >>> across the Internet.
> >> I will not debate whether it is faulty or not, but it seems that in
> >> practice the
> >> Internet breaks the mechanism. However it breaks it is a way that seem=
s
> >> disruptive to some user traffic. The document is really guidance
> >> one how hosts might use  ICMP for optimization, and arguable need
> >> not be a standard at all.
> >>
> >> My remark about heritage is that this vintage draft is very much a
> >> product of
> >> its time, and really needs modernizing, and after modernizing ought to
> >> look quite different, and thus maybe we should employ a procedure
> >> other than a simple replacement.
> >>
> >>
> >>> ...
> >>>> It is concerning that the draft does not talk in any detail about
> >>>> how modern ECMP works, i.e. using the five tuple, and noting that
> >>>> the PMTU may be different depending on the transport layer port
> >>>> numbers.
> >>> Has this problem been analysed for, say, IPv4? And does the real worl=
d
> >>> contain ECMP setups with different MTUs on different paths?
> >> I don't know if anyone has looked. Since the mechanism is
> >> self-correcting albeit
> >> with some disruption to user traffic it looks to the application and t=
he
> >> application
> >> user, just like the Internet not working for a few moments.
> >>
> >> In a well managed SP network there should not be, but neither should t=
here
> >> be asymmetric path costs, but there are. The less well manage private
> >> networks are less well managed.
> >>
> >>
> >>>> Given that a very large fraction of packets will traverse an MPLS
> >>>> network at some point, I am surprised that there is no text talking
> >>>> about the importance of providing support for this feature in the
> >>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
> >>> I don't understand. How does the fact that there might be some MPLS
> >>> segments along the path affect end-to-end PMTUD?
> >> The point that RFC3988 makes is that MPLS looks like a single hop to I=
P
> >> and the
> >> PE has to fragment or has to reply with an ICMP error message to suppo=
rt
> >> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
> >> result
> >> in the right response at the end node.
> >>
> >> My point is that the draft is silent on the subject, and perhaps it
> >> should not be.
> >>
> >> However your question make me ask a further question. The draft is als=
o
> >> silent
> >> on NATs. Is there any advice needed for people designing and configuri=
ng
> >> NATs?
> >>
> >>>> =3D=3D=3D=3D=3D=3D
> >>>>
> >>>>      If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementati=
on
> >>>>      could use the flow id as the local representation of a path. Pa=
ckets
> >>>>      sent to a particular destination but belonging to different flo=
ws may
> >>>>      use different paths, with the choice of path depending on the f=
low
> >>>>      id.  This approach will result in the use of optimally sized pa=
ckets
> >>>>      on a per-flow basis, providing finer granularity than PMTU valu=
es
> >>>>      maintained on a per-destination basis.
> >>>>
> >>>> SB> How widely is flow-id supported in networks? I thought that the
> >>>> SB> current position was that it was unreliable as an ECMP indicator
> >>>> SB> and thus routers tended to glean information from the packet the=
mselves.
> >>> This is future-proofing. Agreed, usage today is limited.
> >>>
> >>> (But it would be better to call it the Flow Label for consistency wit=
h other
> >>> recent RFCs.)
> >> Well the question is whether it is simply limited today, or broken tod=
ay
> >> in a manner that
> >> is irrecoverable? I don't know, but I do know that the mainstream ECMP
> >> approach
> >> is the five-tuple. There is something akin to the flow label being
> >> deployed in MPLS. However
> >> what distinguishes the MPLS Entropy Label is that it is inserted (and
> >> removed) by the
> >> service provider and is therefore trusted by the service provider.
> >>
> >>> I think your other comments are all valuable.
> >> Thank you.
> >>
> >> Stewart
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >
>=20



From nobody Tue Feb 14 08:13:17 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41F11294BF; Tue, 14 Feb 2017 08:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFU-s9xb1fqP; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E14212967F; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
Received: by mail-wm0-x243.google.com with SMTP id r18so4282887wmd.3; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=aFYRlUp+zT3cRyTuc5QfAuwZevJdSQ7XkY44NGrREJA=; b=o57p4trTCV2S669d9jhozhYNhwjISSEcqt9PDfPy4SZEQhnEDRzaG3BQCTbT3ldCVy UOFvNt57Hf3MDqsOygpLzAXEMQJWuZpQwT/udHPIbtB/Wt9myTg4XPNg5QW1MbzBKdBO 99C4LK3c8WEV1sno5IMp8d7hF21n/1w25Qq/jQEju4y3BTBPRVk4JeQw+zxrtcyMfDwr 3NHKB4MkiraOcwihRyhZg95sV1AvryL4hNgRLKvE5zV2HwGp3qH11NEYu7iiqRPLfI8A BSThZ2Y3FMsQ3KGU1EOwl5Hx5mDnNs9O3q5/+5Xdf9oNbbkPipw9qxyGzHbkq06dnB6M fNCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=aFYRlUp+zT3cRyTuc5QfAuwZevJdSQ7XkY44NGrREJA=; b=gEMc2K3hAhtZh0szOU/we4ZTh+wNEiOhTf+l34g6atafSz8cUrRLFqJVezQ2vboVRN Cdfi+Vx6oS+2OIqZL+ezlz94aWYOy9eJ77dkT22IJaKTIHRgTYzgissPSThvCme2OLgl udsNDV+0SXFMBEaxH/lgGGb2m3kgztRduunFCxdLIO1fECkQh1k19NewSCnC1F3S6IKj 12B9jF9GTHmpAcKiHO3Ib3oB4wa9BmVH2Ae/SyoZuxTuy0UUtIXyhdyhbzrWwfzzG9EH 7XxcsrFtEJ4zxqhd56lYXjhOq1NIA+ZO09Ca5Ws9OhLfGkOs1FhnFLFsVctZ7j0IM+C8 jEiA==
X-Gm-Message-State: AMke39m4LeP0DrOo8ubEUKy7K7IgS/wuUoWggBXoSDVngweSMbPLBonoAzS6wIBmz+uZZg==
X-Received: by 10.28.185.77 with SMTP id j74mr4122365wmf.76.1487088784984; Tue, 14 Feb 2017 08:13:04 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 8sm4414020wmg.1.2017.02.14.08.13.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 08:13:04 -0800 (PST)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
Date: Tue, 14 Feb 2017 16:13:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Se-gZmGCjziMpysTrpLf51pOogI>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:13:09 -0000

On 14/02/2017 15:50, Templin, Fred L wrote:
>
>> As to you first point remember that the convergence process disrupts the
>> traffic flow as it does so, and that this will repeat every 10 mins as
>> it tries to re-optimise.
> Yes, you are right. So, even in the case of RFC1981bis it might not be a
> good idea to store discovered MTUs in the network layer when there
> is ECMP in the path. (Which could be any time at all.)

Yes, I think if you really care about disruption due to packet loss your 
best bet is
to go with the minimum supported MTU.

Forwarding performance is not a issue these days, and core link are over 
provisioned
so you have to wonder how important the efficiency gain is in practice.  
The efficiency
gain produced by this protocol in most networks (1276 vs 1496) is only 
about 15% anyway.

>
> You briefly mentioned the authorship in your earlier post. As you well
> know, the corporate affiliation of two of the authors no longer exists.
My concern was that some authors cannot take part in Auth48 due to not 
providing
active email addresses.

- Stewart

>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> - Stewart
>>
>>
>> On 10/02/2017 15:38, Templin, Fred L wrote:
>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
>>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
>>> converge to the minimum MTU of all paths in the multipath, and so it is
>>> still OK to store the MTU in the network layer where it would be shared
>>> by all flows.
>>>
>>> ECMP does present challenges for RFC4821, however. If a first transport
>>> session discovers a large MTU and shares it with a second transport
>>> session, the second session may take a very different path where there
>>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
>>> problems if discovered MTUs are shared between sessions.
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>> -----Original Message-----
>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>>>> Sent: Friday, February 10, 2017 2:21 AM
>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>>>
>>>>
>>>>
>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>>>> Stewart,
>>>>>
>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>>>> ...
>>>>>> I wonder if we would best serve both our future and our heritage
>>>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>>>> or declared it as historic and wrote a new text from a clean start?
>>>>> I don't see that. It's a stable, widely deployed, interoperable
>>>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>>>> across the Internet.
>>>> I will not debate whether it is faulty or not, but it seems that in
>>>> practice the
>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>> disruptive to some user traffic. The document is really guidance
>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>> not be a standard at all.
>>>>
>>>> My remark about heritage is that this vintage draft is very much a
>>>> product of
>>>> its time, and really needs modernizing, and after modernizing ought to
>>>> look quite different, and thus maybe we should employ a procedure
>>>> other than a simple replacement.
>>>>
>>>>
>>>>> ...
>>>>>> It is concerning that the draft does not talk in any detail about
>>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>>>> the PMTU may be different depending on the transport layer port
>>>>>> numbers.
>>>>> Has this problem been analysed for, say, IPv4? And does the real world
>>>>> contain ECMP setups with different MTUs on different paths?
>>>> I don't know if anyone has looked. Since the mechanism is
>>>> self-correcting albeit
>>>> with some disruption to user traffic it looks to the application and the
>>>> application
>>>> user, just like the Internet not working for a few moments.
>>>>
>>>> In a well managed SP network there should not be, but neither should there
>>>> be asymmetric path costs, but there are. The less well manage private
>>>> networks are less well managed.
>>>>
>>>>
>>>>>> Given that a very large fraction of packets will traverse an MPLS
>>>>>> network at some point, I am surprised that there is no text talking
>>>>>> about the importance of providing support for this feature in the
>>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>>>> I don't understand. How does the fact that there might be some MPLS
>>>>> segments along the path affect end-to-end PMTUD?
>>>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>>>> and the
>>>> PE has to fragment or has to reply with an ICMP error message to support
>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>>>> result
>>>> in the right response at the end node.
>>>>
>>>> My point is that the draft is silent on the subject, and perhaps it
>>>> should not be.
>>>>
>>>> However your question make me ask a further question. The draft is also
>>>> silent
>>>> on NATs. Is there any advice needed for people designing and configuring
>>>> NATs?
>>>>
>>>>>> ======
>>>>>>
>>>>>>       If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>>>       could use the flow id as the local representation of a path. Packets
>>>>>>       sent to a particular destination but belonging to different flows may
>>>>>>       use different paths, with the choice of path depending on the flow
>>>>>>       id.  This approach will result in the use of optimally sized packets
>>>>>>       on a per-flow basis, providing finer granularity than PMTU values
>>>>>>       maintained on a per-destination basis.
>>>>>>
>>>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>>>> SB> and thus routers tended to glean information from the packet themselves.
>>>>> This is future-proofing. Agreed, usage today is limited.
>>>>>
>>>>> (But it would be better to call it the Flow Label for consistency with other
>>>>> recent RFCs.)
>>>> Well the question is whether it is simply limited today, or broken today
>>>> in a manner that
>>>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>>>> approach
>>>> is the five-tuple. There is something akin to the flow label being
>>>> deployed in MPLS. However
>>>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>>>> removed) by the
>>>> service provider and is therefore trusted by the service provider.
>>>>
>>>>> I think your other comments are all valuable.
>>>> Thank you.
>>>>
>>>> Stewart
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 08:25:33 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2940129641; Tue, 14 Feb 2017 08:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwtTfMG-yEXl; Tue, 14 Feb 2017 08:25:28 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B976129696; Tue, 14 Feb 2017 08:25:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1EGPRJ3051436; Tue, 14 Feb 2017 09:25:27 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EGPGg0051233 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 09:25:16 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 08:25:15 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 08:25:15 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEA==
Date: Tue, 14 Feb 2017 16:25:15 +0000
Message-ID: <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
In-Reply-To: <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/iVz3buVrrx42A9lzF_XD7P4soL8>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:25:29 -0000

Hi Stewart,

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 8:13 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; Stewart Bryant
> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
>=20
>=20
> On 14/02/2017 15:50, Templin, Fred L wrote:
> >
> >> As to you first point remember that the convergence process disrupts t=
he
> >> traffic flow as it does so, and that this will repeat every 10 mins as
> >> it tries to re-optimise.
> > Yes, you are right. So, even in the case of RFC1981bis it might not be =
a
> > good idea to store discovered MTUs in the network layer when there
> > is ECMP in the path. (Which could be any time at all.)
>=20
> Yes, I think if you really care about disruption due to packet loss your
> best bet is
> to go with the minimum supported MTU.
>=20
> Forwarding performance is not a issue these days, and core link are over
> provisioned
> so you have to wonder how important the efficiency gain is in practice.
> The efficiency
> gain produced by this protocol in most networks (1276 vs 1496) is only
> about 15% anyway.

So, that would leave us with RFC4821 plus per {session,destination}
probing instead of just per-destination probing. Or, just stick with the
IPv6 minMTU (1280)?

Thanks - Fred
fred.l.templin@boeing.com

> > You briefly mentioned the authorship in your earlier post. As you well
> > know, the corporate affiliation of two of the authors no longer exists.
> My concern was that some authors cannot take part in Auth48 due to not
> providing
> active email addresses.
>=20
> - Stewart
>=20
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> - Stewart
> >>
> >>
> >> On 10/02/2017 15:38, Templin, Fred L wrote:
> >>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used i=
n the
> >>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventua=
lly
> >>> converge to the minimum MTU of all paths in the multipath, and so it =
is
> >>> still OK to store the MTU in the network layer where it would be shar=
ed
> >>> by all flows.
> >>>
> >>> ECMP does present challenges for RFC4821, however. If a first transpo=
rt
> >>> session discovers a large MTU and shares it with a second transport
> >>> session, the second session may take a very different path where ther=
e
> >>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
> >>> idea to file an erratum to RFC4821 explaining how ECMP might cause
> >>> problems if discovered MTUs are shared between sessions.
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>> -----Original Message-----
> >>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryan=
t
> >>>> Sent: Friday, February 10, 2017 2:21 AM
> >>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant =
<stewart@g3ysx.org.uk>; gen-art@ietf.org
> >>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@iet=
f.org
> >>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>>>
> >>>>
> >>>>
> >>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>>>> Stewart,
> >>>>>
> >>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>>>> ...
> >>>>>> I wonder if we would best serve both our future and our heritage
> >>>>>> if we declared RFC1981 as historic, and either left the idea there=
,
> >>>>>> or declared it as historic and wrote a new text from a clean start=
?
> >>>>> I don't see that. It's a stable, widely deployed, interoperable
> >>>>> mechanism. That is rather orthogonal to the issue that has been rai=
sed,
> >>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
> >>>>> across the Internet.
> >>>> I will not debate whether it is faulty or not, but it seems that in
> >>>> practice the
> >>>> Internet breaks the mechanism. However it breaks it is a way that se=
ems
> >>>> disruptive to some user traffic. The document is really guidance
> >>>> one how hosts might use  ICMP for optimization, and arguable need
> >>>> not be a standard at all.
> >>>>
> >>>> My remark about heritage is that this vintage draft is very much a
> >>>> product of
> >>>> its time, and really needs modernizing, and after modernizing ought =
to
> >>>> look quite different, and thus maybe we should employ a procedure
> >>>> other than a simple replacement.
> >>>>
> >>>>
> >>>>> ...
> >>>>>> It is concerning that the draft does not talk in any detail about
> >>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
> >>>>>> the PMTU may be different depending on the transport layer port
> >>>>>> numbers.
> >>>>> Has this problem been analysed for, say, IPv4? And does the real wo=
rld
> >>>>> contain ECMP setups with different MTUs on different paths?
> >>>> I don't know if anyone has looked. Since the mechanism is
> >>>> self-correcting albeit
> >>>> with some disruption to user traffic it looks to the application and=
 the
> >>>> application
> >>>> user, just like the Internet not working for a few moments.
> >>>>
> >>>> In a well managed SP network there should not be, but neither should=
 there
> >>>> be asymmetric path costs, but there are. The less well manage privat=
e
> >>>> networks are less well managed.
> >>>>
> >>>>
> >>>>>> Given that a very large fraction of packets will traverse an MPLS
> >>>>>> network at some point, I am surprised that there is no text talkin=
g
> >>>>>> about the importance of providing support for this feature in the
> >>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental=
.
> >>>>> I don't understand. How does the fact that there might be some MPLS
> >>>>> segments along the path affect end-to-end PMTUD?
> >>>> The point that RFC3988 makes is that MPLS looks like a single hop to=
 IP
> >>>> and the
> >>>> PE has to fragment or has to reply with an ICMP error message to sup=
port
> >>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate =
to
> >>>> result
> >>>> in the right response at the end node.
> >>>>
> >>>> My point is that the draft is silent on the subject, and perhaps it
> >>>> should not be.
> >>>>
> >>>> However your question make me ask a further question. The draft is a=
lso
> >>>> silent
> >>>> on NATs. Is there any advice needed for people designing and configu=
ring
> >>>> NATs?
> >>>>
> >>>>>> =3D=3D=3D=3D=3D=3D
> >>>>>>
> >>>>>>       If flows [I-D.ietf-6man-rfc2460bis] are in use, an implement=
ation
> >>>>>>       could use the flow id as the local representation of a path.=
 Packets
> >>>>>>       sent to a particular destination but belonging to different =
flows may
> >>>>>>       use different paths, with the choice of path depending on th=
e flow
> >>>>>>       id.  This approach will result in the use of optimally sized=
 packets
> >>>>>>       on a per-flow basis, providing finer granularity than PMTU v=
alues
> >>>>>>       maintained on a per-destination basis.
> >>>>>>
> >>>>>> SB> How widely is flow-id supported in networks? I thought that th=
e
> >>>>>> SB> current position was that it was unreliable as an ECMP indicat=
or
> >>>>>> SB> and thus routers tended to glean information from the packet t=
hemselves.
> >>>>> This is future-proofing. Agreed, usage today is limited.
> >>>>>
> >>>>> (But it would be better to call it the Flow Label for consistency w=
ith other
> >>>>> recent RFCs.)
> >>>> Well the question is whether it is simply limited today, or broken t=
oday
> >>>> in a manner that
> >>>> is irrecoverable? I don't know, but I do know that the mainstream EC=
MP
> >>>> approach
> >>>> is the five-tuple. There is something akin to the flow label being
> >>>> deployed in MPLS. However
> >>>> what distinguishes the MPLS Entropy Label is that it is inserted (an=
d
> >>>> removed) by the
> >>>> service provider and is therefore trusted by the service provider.
> >>>>
> >>>>> I think your other comments are all valuable.
> >>>> Thank you.
> >>>>
> >>>> Stewart
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> IETF IPv6 working group mailing list
> >>>> ipv6@ietf.org
> >>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>>> --------------------------------------------------------------------
> >
>=20



From nobody Tue Feb 14 08:45:16 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7E112968E; Tue, 14 Feb 2017 08:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIrkd1xf6cEs; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A4B9129674; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
Received: by mail-wm0-x244.google.com with SMTP id v77so4417102wmv.0; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Le87WbpJqsUA9ApP9SxYAyK+ngTySjoywXo7oQ51DaU=; b=QMA/oYlmC8RHT9uRzxD4lkyW7ExrHeLj4BIVcpxyT55PVeV/+pYvnMvBHqIQARkx/R FBfB3uCSI9CdM9aZ6DTpxjz+FmrI4xQez0WaGtRpzWguRyXNjJE5iUAbmNCwn0IqcEWO m1yuxtWqPCiyz7F2IsZjvue1dsOik1mw5/69BgSjc2AK4OMohF/9nfxzKDkGECvMDGEM aMpPGraU/ZYSQw+Osxo+PtAnQ2FmbIpDfHx4ievrvGaLDdyUAserJVmzSX74qchy7l+Y FprjoAXPRns+GfTEIESzeKDrN5lHq3zm3lcfN24to9xBy1Rgyb1oFNHybrPOKS4BUqOX SXZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Le87WbpJqsUA9ApP9SxYAyK+ngTySjoywXo7oQ51DaU=; b=eF8DT7ZqTQkZw2c8KhVsAE4Hnp/oIRMu4shK99X46Wl4swBwGQ0WLi8sYFigoOK7JZ I5TNvOwgLQv5ug7bBRHs73jneWyJXTAqR/x4lAERFWY+cFGvT/ehjFeH3R/fJiADXQFT eWGJL+JdTpbePlbdQcRpLziaaw4lS2RZgWheVF3iFkyyMm3F5zxc7nxkbA+RHQ8PU5S1 fg49j9amCx/0yk2rv5ufWmV/x5Hbgi5FPuPBMpm5IvNOromW0YNU5lX6A0HEAydEEBSd eqj1WqWY0pTBOZaj4KfJ5Aa7gMDE/ZD0FO7kJDvSB+f4yyT+EkDWDlhNHHXwxbZ/OdPs rI9w==
X-Gm-Message-State: AMke39m+2aCcaJuxqHVN8MBCnPi+pAAjX4PMQW4LiKUHZVoPUIsKCJlBRSsRxqSIJaciaA==
X-Received: by 10.28.109.218 with SMTP id b87mr4112682wmi.52.1487090706509; Tue, 14 Feb 2017 08:45:06 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 45sm1414641wrx.60.2017.02.14.08.45.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 08:45:05 -0800 (PST)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
Date: Tue, 14 Feb 2017 16:45:04 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ANblg8ZJAnk3Og-7MxrAKclojw0>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:45:10 -0000

Fred
*If*  you care about packet loss, then your only option is to probe the 
path with with
synthetic data that exactly mimics the live data, or not to probe at all 
and live
with the 1280. As I said 1280 is pretty close to 1496 which is all most 
networks
will give you in practice.

When I think about the people asking for fast re-route to minimise 
packet loss, it seems
very strange to deliberately induce loss to try to stretch the MTU by 15%.

- Stewart


On 14/02/2017 16:25, Templin, Fred L wrote:
> Hi Stewart,
>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
>> Sent: Tuesday, February 14, 2017 8:13 AM
>> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant
>> <stewart@g3ysx.org.uk>; gen-art@ietf.org
>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>
>>
>>
>> On 14/02/2017 15:50, Templin, Fred L wrote:
>>>> As to you first point remember that the convergence process disrupts the
>>>> traffic flow as it does so, and that this will repeat every 10 mins as
>>>> it tries to re-optimise.
>>> Yes, you are right. So, even in the case of RFC1981bis it might not be a
>>> good idea to store discovered MTUs in the network layer when there
>>> is ECMP in the path. (Which could be any time at all.)
>> Yes, I think if you really care about disruption due to packet loss your
>> best bet is
>> to go with the minimum supported MTU.
>>
>> Forwarding performance is not a issue these days, and core link are over
>> provisioned
>> so you have to wonder how important the efficiency gain is in practice.
>> The efficiency
>> gain produced by this protocol in most networks (1276 vs 1496) is only
>> about 15% anyway.
> So, that would leave us with RFC4821 plus per {session,destination}
> probing instead of just per-destination probing. Or, just stick with the
> IPv6 minMTU (1280)?
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>>> You briefly mentioned the authorship in your earlier post. As you well
>>> know, the corporate affiliation of two of the authors no longer exists.
>> My concern was that some authors cannot take part in Auth48 due to not
>> providing
>> active email addresses.
>>
>> - Stewart
>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>> - Stewart
>>>>
>>>>
>>>> On 10/02/2017 15:38, Templin, Fred L wrote:
>>>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
>>>>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
>>>>> converge to the minimum MTU of all paths in the multipath, and so it is
>>>>> still OK to store the MTU in the network layer where it would be shared
>>>>> by all flows.
>>>>>
>>>>> ECMP does present challenges for RFC4821, however. If a first transport
>>>>> session discovers a large MTU and shares it with a second transport
>>>>> session, the second session may take a very different path where there
>>>>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
>>>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
>>>>> problems if discovered MTUs are shared between sessions.
>>>>>
>>>>> Thanks - Fred
>>>>> fred.l.templin@boeing.com
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>>>>>> Sent: Friday, February 10, 2017 2:21 AM
>>>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>>>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>>>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>>>>>> Stewart,
>>>>>>>
>>>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>>>>>> ...
>>>>>>>> I wonder if we would best serve both our future and our heritage
>>>>>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>>>>>> or declared it as historic and wrote a new text from a clean start?
>>>>>>> I don't see that. It's a stable, widely deployed, interoperable
>>>>>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>>>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>>>>>> across the Internet.
>>>>>> I will not debate whether it is faulty or not, but it seems that in
>>>>>> practice the
>>>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>>>> disruptive to some user traffic. The document is really guidance
>>>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>>>> not be a standard at all.
>>>>>>
>>>>>> My remark about heritage is that this vintage draft is very much a
>>>>>> product of
>>>>>> its time, and really needs modernizing, and after modernizing ought to
>>>>>> look quite different, and thus maybe we should employ a procedure
>>>>>> other than a simple replacement.
>>>>>>
>>>>>>
>>>>>>> ...
>>>>>>>> It is concerning that the draft does not talk in any detail about
>>>>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>>>>>> the PMTU may be different depending on the transport layer port
>>>>>>>> numbers.
>>>>>>> Has this problem been analysed for, say, IPv4? And does the real world
>>>>>>> contain ECMP setups with different MTUs on different paths?
>>>>>> I don't know if anyone has looked. Since the mechanism is
>>>>>> self-correcting albeit
>>>>>> with some disruption to user traffic it looks to the application and the
>>>>>> application
>>>>>> user, just like the Internet not working for a few moments.
>>>>>>
>>>>>> In a well managed SP network there should not be, but neither should there
>>>>>> be asymmetric path costs, but there are. The less well manage private
>>>>>> networks are less well managed.
>>>>>>
>>>>>>
>>>>>>>> Given that a very large fraction of packets will traverse an MPLS
>>>>>>>> network at some point, I am surprised that there is no text talking
>>>>>>>> about the importance of providing support for this feature in the
>>>>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>>>>>> I don't understand. How does the fact that there might be some MPLS
>>>>>>> segments along the path affect end-to-end PMTUD?
>>>>>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>>>>>> and the
>>>>>> PE has to fragment or has to reply with an ICMP error message to support
>>>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>>>>>> result
>>>>>> in the right response at the end node.
>>>>>>
>>>>>> My point is that the draft is silent on the subject, and perhaps it
>>>>>> should not be.
>>>>>>
>>>>>> However your question make me ask a further question. The draft is also
>>>>>> silent
>>>>>> on NATs. Is there any advice needed for people designing and configuring
>>>>>> NATs?
>>>>>>
>>>>>>>> ======
>>>>>>>>
>>>>>>>>        If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>>>>>        could use the flow id as the local representation of a path. Packets
>>>>>>>>        sent to a particular destination but belonging to different flows may
>>>>>>>>        use different paths, with the choice of path depending on the flow
>>>>>>>>        id.  This approach will result in the use of optimally sized packets
>>>>>>>>        on a per-flow basis, providing finer granularity than PMTU values
>>>>>>>>        maintained on a per-destination basis.
>>>>>>>>
>>>>>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>>>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>>>>>> SB> and thus routers tended to glean information from the packet themselves.
>>>>>>> This is future-proofing. Agreed, usage today is limited.
>>>>>>>
>>>>>>> (But it would be better to call it the Flow Label for consistency with other
>>>>>>> recent RFCs.)
>>>>>> Well the question is whether it is simply limited today, or broken today
>>>>>> in a manner that
>>>>>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>>>>>> approach
>>>>>> is the five-tuple. There is something akin to the flow label being
>>>>>> deployed in MPLS. However
>>>>>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>>>>>> removed) by the
>>>>>> service provider and is therefore trusted by the service provider.
>>>>>>
>>>>>>> I think your other comments are all valuable.
>>>>>> Thank you.
>>>>>>
>>>>>> Stewart
>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list
>>>>>> ipv6@ietf.org
>>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 10:33:17 2017
Return-Path: <otroan@employees.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2A1296CA; Tue, 14 Feb 2017 10:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2N-O6NDYEI8; Tue, 14 Feb 2017 10:33:06 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8741296F5; Tue, 14 Feb 2017 10:33:06 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 18:33:05 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 64618D788B; Tue, 14 Feb 2017 10:33:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=2Udc1oFlG6DgKxvFdQ/STFKHWJg=; b= hJuTcP4qepEsGMzxZoNIrWWSI9UjA1Op8WZJLnmRejHpy1vnspHWCCVNE9sIvFWY 8KM7+QLacSwlZQiYCxt2CLVepE/9X7z/lxB4b2tvfbf60F44JnsWrosLW81CEECY VtFwlVQdFHztlk5Irlqiyp7EWzl+HtgD6bevinlJvTk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=i8i3vG4MX8m7qmdsKqQrULc 4NlgC0t6JjQdAhJVxB7hkH1KvQ3zoL84YDnLH3HsLF5WPJ0oSLd6qAw4pTCE2jYE drKDtft6v2uFMwOatf2SfktuonMn/vgamF/HSKGDF5FeZmoG80XfuPg7e+rulv0Z zIZBlBneffvHFrzhJ4aw=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id EAD4AD788D; Tue, 14 Feb 2017 10:33:04 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 0A7208AD77E0; Tue, 14 Feb 2017 19:33:10 +0100 (CET)
From: otroan@employees.org
Message-Id: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Tue, 14 Feb 2017 19:33:09 +0100
In-Reply-To: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/UF0vyysT2Uk3U2u3UEIr021ejj0>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:33:07 -0000

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Stewart,

> *If*  you care about packet loss, then your only option is to probe =
the path with with
> synthetic data that exactly mimics the live data, or not to probe at =
all and live
> with the 1280. As I said 1280 is pretty close to 1496 which is all =
most networks
> will give you in practice.

Yes, but sending at 1280 does not work for IP tunnels. The whole purpose =
of the minimum MTU was to give space for tunnel headers (1500-1280).

> When I think about the people asking for fast re-route to minimise =
packet loss, it seems
> very strange to deliberately induce loss to try to stretch the MTU by =
15%.

Please show the data that there is significant loss. The measurements I =
have found has not shown that.
If not, then let's please leave that argument on the shelf.

(And please don't read me wrong, I think we should get DNS fixed, that =
we should fix the IP tunnelling protocols, and that we should get IP =
fragmentation deprecated).

But right here, right now. PMTUD is for many problems the only solution =
on the table.
We as a community can choose not to elevate the standard of course, and =
that will of course not have any big consequence.
Are you afraid that elevating 1981, will hinder people from working on =
new and better solutions?

Best regards,
Ole

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYo01lAAoJEL7aWKiYQt92u0IP/2lXtgePm1tB/H1AzQng3S7t
olEJPQSkETUOIDopR48/04S3XxRfBGf+5Uh8suPHnZnTiVNZ3goRFZldY02/GRoR
Rfzc45vZBuWOfBwlqsHmgXz8T+rFeJzlzJ+v7feBQ645KPPKHjBMrGs36ojJTdI7
M07bKNFR4uLEXFTlxvC8UCy731Itla0jCwQg4NBB7d45EODIgUl1TocsOsArP05m
XQNW5Ex8E1inNHDIRamHpwd//PTfXnAG4ME+Xrgz6L5RtUX/YiXgIIY2Nadd1/Cv
X+B6BbhM8cjmB/SbEqGu9aPCPlw8UNkpo/s2HFbht0G3U5QnnRDCJSIG9w3tfQhc
YJ3nHpojHg7EHu4g77sMFJzmI9jz9p1TF232DzFzbiNPsbHMIaNF3w104b3Xb1dq
744ED8ZzGNxMTQzHhie/n6tm0Ft4a0RIvwXEjXY8VasUiwMF7HqLW4z8vBsGL0tI
wOzaA0X1R95v2WpJ6zuZz2AfVuwCXTXU2oj/mRD5WAg1bCVdc7Kp02+uFsMBqcp7
awrp7Va3cYAR0Hx6ziqSe7lIbDQlAIk/DTRJyxnsCUZcJaR1bxfUos8bePlKlxks
vuFgkB8+6Ajlz2tUb4+FeeqHqhFILkCJdAPPwQQJJrFnc8gB3P3I8eJDCEAtSkml
2Eif1J254Ib81r6zh4YE
=iCl+
-----END PGP SIGNATURE-----

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE--


From nobody Tue Feb 14 10:53:54 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFA261296DF for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 10:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zu6XmOl2zU2 for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 10:53:51 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E436C129531 for <gen-art@ietf.org>; Tue, 14 Feb 2017 10:53:50 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id u63so4945602wmu.2 for <gen-art@ietf.org>; Tue, 14 Feb 2017 10:53:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ZUdXZ/YRKADWNSGMCPd1LKqxvAuhXlF4fJnE5UU9N2c=; b=B7QLII2YXKUEOX2Vi7/FWpWcjRyi953ejSt0OFnGnIU6gxkBX4hh7bPz5BRH/GaMtE /rmjEcDNyC7hKJMiPNgQ09fOtqzsgKCjqOkEw0EIOsJbsZ45NIiffukv6p0on3AejfiR Q5p793Kjqb2tWsROzaQ7yiLMY9OPZxTZA8AReF35yuo84YEchWz9Ya/hvoac42zhnifA 0aRWOXZbcpvEzLcvG+WG/VQUFdcAQHWQKkizlQJjIKb2LlQVAJoDTMaCg0mYI27shwam 1RUui0Y5YFo+5439h8WHJUdJm1H7p4cgsuWdpH/MlUp137ShbGAEsg+ZjVZrgwoNd/wz bCag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZUdXZ/YRKADWNSGMCPd1LKqxvAuhXlF4fJnE5UU9N2c=; b=WzVvYB3wuPhfEB7CPF2QAFSIqgSJ1r4Me1zUWmPUUUOJ/StvCXGE54RO0nT2VB7ejJ u+3MYepfsDS37AOA3WjFmmTNZgNMIam2m7kpBX0abtQItWHTEKb0EhVa4aK5kGxLwhka xXxSuQnTOmJ9S0qw36fONjkP8eNbTQkY/8hTAZhvo0ErE7AlJ65QmMZI7mHU1Iz9MRwq XIYEJHpyOUWWSvw+UElD5/Pd2ngvcg3lc2KFp1seBjO/PSFSGlLuOTG8j/Txne9w5Ux1 KsWzz06ZSDSptIhCeXEuEdRpZ6adYOPJPszVA43ax9aA9HyhZp6lKARlnMM1cTSf1Pnc hrLQ==
X-Gm-Message-State: AMke39mButKaQFf45ttAFbp8xoMlMDn7bLP7m6Qlf7tJVjrLf+p3TFb8kMDWKEpAhr8bcw==
X-Received: by 10.28.232.90 with SMTP id f87mr4498610wmh.35.1487098429229; Tue, 14 Feb 2017 10:53:49 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id l37sm1846390wrc.41.2017.02.14.10.53.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 10:53:48 -0800 (PST)
To: otroan@employees.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <79dc448c-ac7e-faa2-7fe1-b189262f1d34@gmail.com>
Date: Tue, 14 Feb 2017 18:53:47 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0JyYwby3Thf_un0JKlCSNIRNi7A>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:53:53 -0000

Ole

Maybe we could sort this out faster with a short phone call.

As I read the spec it says hunt for a new upper  limit every 10 mins, 
won't there be packet as it sends out oversized packets looking for a 
higher MTU?

Stewart


On 14/02/2017 18:33, otroan@employees.org wrote:
> Stewart,
>
>> *If*  you care about packet loss, then your only option is to probe the path with with
>> synthetic data that exactly mimics the live data, or not to probe at all and live
>> with the 1280. As I said 1280 is pretty close to 1496 which is all most networks
>> will give you in practice.
> Yes, but sending at 1280 does not work for IP tunnels. The whole purpose of the minimum MTU was to give space for tunnel headers (1500-1280).
>
>> When I think about the people asking for fast re-route to minimise packet loss, it seems
>> very strange to deliberately induce loss to try to stretch the MTU by 15%.
> Please show the data that there is significant loss. The measurements I have found has not shown that.
> If not, then let's please leave that argument on the shelf.
>
> (And please don't read me wrong, I think we should get DNS fixed, that we should fix the IP tunnelling protocols, and that we should get IP fragmentation deprecated).
>
> But right here, right now. PMTUD is for many problems the only solution on the table.
> We as a community can choose not to elevate the standard of course, and that will of course not have any big consequence.
> Are you afraid that elevating 1981, will hinder people from working on new and better solutions?
>
> Best regards,
> Ole


From nobody Tue Feb 14 10:54:40 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D0B1297AA; Tue, 14 Feb 2017 10:54:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_en8OkY62uV; Tue, 14 Feb 2017 10:54:29 -0800 (PST)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7FCB1297A5; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
Received: by mail-it0-x242.google.com with SMTP id e137so6522345itc.0; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zoljRW9e/UePysa9t3UpARD6TJXQUjGQNMwSDSa/q3M=; b=fXQYCVFPG+GY38kyzGQMn8DYSvLqS9kuXBaeaPoXTPlzMqQK6hiM+N1wUt9VBJvSX/ p7EmOEnJ/VHEt8mPSJGaTg+brVntzh0jSgp26OobbcvTwot+kPsy6kJJg4U4JMvWmp1A n7/uNVjBfGkQWWvupsLvC0suAVOpdypy+8lKlCEKOjZj8q7IO19rtx1BDM5ZHJgcome5 +3Yv00mcboBLSBfxuvIF8WVpd8RsFvrSO1/q74yRpRGluhJ9BxgiHBQyGvp2icXBmhsb GwcuaIcEB08wbYQJd3xsXOw5YryRgcnJZvX3pdwGRjF2g8Ex9IF761TSo7FnPjmvMYcr VUcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zoljRW9e/UePysa9t3UpARD6TJXQUjGQNMwSDSa/q3M=; b=tEnSTg+wqgugwIYg2SmhIajf4pmQ2Plxsq3eIIYKtfIeWGb42Ny0UiBclaxf58f9oB QXk/XKCLtzw5bpITXoIB1OGEmki/xpR3WaQn1Bap086fk2hQmr33SzaYl3I2ve5ReMh2 I50Drt7BmV99hmn59bm8sPdXB7usleO2rd12EWcQghuhAtvqcWrK0a5a2BFDyOclBMzv muQixDHG9aOuGNBG9GqRX1Qa4+Li4WZPqIUejDJKziUz0uR/d7raK6pGwnXsaZTdpd9P DiCc9nJWo51mob0qrsuZMGAkbcq/oMZpqJAGzP7oKQUvHPcbS+gulRDahvrMBimp5nxV M86Q==
X-Gm-Message-State: AMke39mhFO+wXWjkL5QkNpypfcbUWTQlRI0F95NLcAHOcJle0J1FHe+DFmjvA7Htju2/WA==
X-Received: by 10.84.131.130 with SMTP id d2mr5396174pld.41.1487098468212; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id r78sm2698005pfl.63.2017.02.14.10.54.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 10:54:27 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Date: Tue, 14 Feb 2017 10:54:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC4EEF4D-45E6-4E1B-8FCA-226E5E55BEEF@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/AqN3P053rBZ2IyFxvTumCF5uUig>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:54:30 -0000

> On Feb 14, 2017, at 10:33 AM, otroan@employees.org wrote:
>=20
>> *If*  you care about packet loss, then your only option is to probe =
the path with with
>> synthetic data that exactly mimics the live data, or not to probe at =
all and live
>> with the 1280. As I said 1280 is pretty close to 1496 which is all =
most networks
>> will give you in practice.
>=20
> Yes, but sending at 1280 does not work for IP tunnels. The whole =
purpose of the minimum MTU was to give space for tunnel headers =
(1500-1280).

I'm confused by that statement. =
https://tools.ietf.org/html/rfc7676#section-3.2 indicates that a GRE =
tunnel on IPv6 and carrying an IPv6 payload works with a PMTU of 1280, =
and AFAIK it is among the larger tunnel headers. What tunnels does a =
PMTU of 1280 not work for?=


From nobody Tue Feb 14 10:55:26 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233FD129A9F; Tue, 14 Feb 2017 10:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Vjswx_p9F03; Tue, 14 Feb 2017 10:55:11 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A280129AA8; Tue, 14 Feb 2017 10:54:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1EIshnx015092; Tue, 14 Feb 2017 11:54:43 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EIsYLf014962 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 11:54:34 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 10:54:33 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 10:54:33 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, Stewart Bryant <stewart.bryant@gmail.com>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAAEjdGhAACokzA=
Date: Tue, 14 Feb 2017 18:54:33 +0000
Message-ID: <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VRsZvk-zFGvzOPvlGI4mL2SyK2w>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:55:13 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Tuesday, February 14, 2017 10:33 AM
> To: Stewart Bryant <stewart.bryant@gmail.com>
> Cc: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; gen-art@ietf.org; 6man WG
> <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Stewart,
>=20
> > *If*  you care about packet loss, then your only option is to probe the=
 path with with
> > synthetic data that exactly mimics the live data, or not to probe at al=
l and live
> > with the 1280. As I said 1280 is pretty close to 1496 which is all most=
 networks
> > will give you in practice.
>=20
> Yes, but sending at 1280 does not work for IP tunnels. The whole purpose =
of the minimum MTU was to give space for tunnel headers
> (1500-1280).

But, if non-tunnel links set a 1280 MTU which is perfectly OK with the stan=
dard then
there is no space for headers. Given the issues with classical PMTUD then (=
plus the
non-applicability of RFC4821 for tunnels) the only solution for tunnels is =
fragmentation.
I'll let Joe step in if he wants to.

Thanks - Fred

> > When I think about the people asking for fast re-route to minimise pack=
et loss, it seems
> > very strange to deliberately induce loss to try to stretch the MTU by 1=
5%.
>=20
> Please show the data that there is significant loss. The measurements I h=
ave found has not shown that.
> If not, then let's please leave that argument on the shelf.
>=20
> (And please don't read me wrong, I think we should get DNS fixed, that we=
 should fix the IP tunnelling protocols, and that we should
> get IP fragmentation deprecated).
>=20
> But right here, right now. PMTUD is for many problems the only solution o=
n the table.
> We as a community can choose not to elevate the standard of course, and t=
hat will of course not have any big consequence.
> Are you afraid that elevating 1981, will hinder people from working on ne=
w and better solutions?
>=20
> Best regards,
> Ole


From nobody Tue Feb 14 11:14:54 2017
Return-Path: <otroan@employees.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33319129699 for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 11:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NEIWxuD0tWtk for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 11:14:51 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id D7CC2120724 for <gen-art@ietf.org>; Tue, 14 Feb 2017 11:14:51 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 19:14:51 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 9C82ED788A; Tue, 14 Feb 2017 11:14:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=apVArGmi0QTbAG9n9CO7lQ47yf0=; b= V6/s0GN+k5BfY/IgHZpJpejPgRQHkOgzWu9c/uCk5WPywILhNKkC+pEp/YU6EE/f ZI1dKp/RYmiLzL0k07mEtN15f0IYuaB/q4mpCjtQKRy0+PxToT9GUvZ8ytjBcWr9 Thu6mbl5sTdCs2D8DXmF13yqCau2hO81QR9ynCb2w4g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=jLTcU4l77MYpNKeqm/U/V5/ btcDlodZvo2qLiA+SqIdR0QOi2ucClQCtIxm3MaNlvb1VZhNweuH0DynUoPdVKMy WxY898TANOVxFiSXZnYbExh0zkHVm+tCM3HR8O2hW0EPAjmTkziOURZHZt9jEkIC Oapil16Ov5uugG+It2iA=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 27082D788E; Tue, 14 Feb 2017 11:14:51 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 1D4D08AE3919; Tue, 14 Feb 2017 20:14:57 +0100 (CET)
From: otroan@employees.org
Message-Id: <68CF4CA5-76E9-4610-8D58-A18A1DA00175@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_B2EEB6AE-88BF-47C4-B9EE-7AB2AD827A95"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Tue, 14 Feb 2017 20:14:56 +0100
In-Reply-To: <79dc448c-ac7e-faa2-7fe1-b189262f1d34@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <79dc448c-ac7e-faa2-7fe1-b189262f1d34@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/TbWRJ7Jy2T5fO4ZlL1Qmu71QErU>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:14:53 -0000

--Apple-Mail=_B2EEB6AE-88BF-47C4-B9EE-7AB2AD827A95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Stewart,


> Maybe we could sort this out faster with a short phone call.

Yes, we can certainly do that!

> As I read the spec it says hunt for a new upper  limit every 10 mins, =
won't there be packet as it sends out oversized packets looking for a =
higher MTU?

Yes.

Best regards,
Ole

> On 14/02/2017 18:33, otroan@employees.org wrote:
>> Stewart,
>>=20
>>> *If*  you care about packet loss, then your only option is to probe =
the path with with
>>> synthetic data that exactly mimics the live data, or not to probe at =
all and live
>>> with the 1280. As I said 1280 is pretty close to 1496 which is all =
most networks
>>> will give you in practice.
>> Yes, but sending at 1280 does not work for IP tunnels. The whole =
purpose of the minimum MTU was to give space for tunnel headers =
(1500-1280).
>>=20
>>> When I think about the people asking for fast re-route to minimise =
packet loss, it seems
>>> very strange to deliberately induce loss to try to stretch the MTU =
by 15%.
>> Please show the data that there is significant loss. The measurements =
I have found has not shown that.
>> If not, then let's please leave that argument on the shelf.
>>=20
>> (And please don't read me wrong, I think we should get DNS fixed, =
that we should fix the IP tunnelling protocols, and that we should get =
IP fragmentation deprecated).
>>=20
>> But right here, right now. PMTUD is for many problems the only =
solution on the table.
>> We as a community can choose not to elevate the standard of course, =
and that will of course not have any big consequence.
>> Are you afraid that elevating 1981, will hinder people from working =
on new and better solutions?
>>=20
>> Best regards,
>> Ole


--Apple-Mail=_B2EEB6AE-88BF-47C4-B9EE-7AB2AD827A95
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYo1cwAAoJEL7aWKiYQt92HyQP/1SKmB3KWu42DUEJ9kWWNnnr
L420pr6jVejGmTkHH7w5VSrIC6VwB4iXsLMTbRjf79T/GWVqHnaG+cpQzDRNyheW
g4Aei+zDoMfCqrwZ/8rOaYhzY3IqpJQFlxFgVQOBTLY90R+I+Q7dDMK28OvwYfJp
CcYzgGlJcoOz5dG9ah81oinOirOoZiS7kRAUPQsr3kuwewCQdTy2OFYpQAYkZ3iU
+uBQ/KSbVDpMkEz+RCazHkSdRHJlXApX5TqLT6+iw0CGmyvH+bQp8USLJMe2vlwr
AjkRtKwkxmo1CSI/S1cP1u7oyEicvyZrTqFDoT+f2avyqQxAM0et5GgiAlH3Y0WX
ubuaSGH/TJskd5mDRuW0+waUmRG13PaPApuhXHYK17T8LxcrkgL+J6klp+uRtxCM
pzmni+vh9MuaYQPtvp58fGXLYObgENuVWfwPgDxECzCiPVXADwFktjNpOMq6+5iD
ALV5NZlvCNysmb6Dbn/AU5G4iKpfXa7F1iUH3OuIf2jOldx86iYnw57KjT9JYcoM
ljKfr1TmohiG45Wghqw3eu39D4HVtkhNDvoUrdGpMsxg0J0qJvtu8mCRx++xatrN
EWwPvQTa+ZaUG7eMQZ83M1DV1ScEdOUW7v+JnDr69Wd2A8df7W8tFNPGRWtLqimg
VLNQ/hcQ3plh5jjgvRgU
=pVJJ
-----END PGP SIGNATURE-----

--Apple-Mail=_B2EEB6AE-88BF-47C4-B9EE-7AB2AD827A95--


From nobody Tue Feb 14 11:16:58 2017
Return-Path: <otroan@employees.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71E11296B2; Tue, 14 Feb 2017 11:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVjaTKiFuvW3; Tue, 14 Feb 2017 11:16:51 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 301B9129603; Tue, 14 Feb 2017 11:16:51 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 19:16:51 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E5B67D788A; Tue, 14 Feb 2017 11:16:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=wPMheHye/k6TPP7yBAQ3/E5Lf+8=; b= Prnp1qMQ3lJVha8eIgu9mPhoGeU4UJN6pqwiPZPYXV4qacjQGZRh5OS/qRzh//+a eU+xpDOrc/TGrzdIBhl9qRYutWQ6s8TjiVt7q/CJhFtaDy8FwA77gX1JzDXCzdZz LqNFrngL1SvzDsJ/qeg1c0arG/6Qw065Eq+5qREmnTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=I8EVsHdJz8SFNAno7z5w7aA aWZlCpTpYXbEkwNF9EMEjTm9q2saGpNp8Ywk60U37HXr82i41YLS9O9RFaaWr+jG AGi2Sr3Svgx8eO3doaU0K3cSAfwNcTVz5QV12/xmIxkyA5BNdyS2JNUKboM+9E6D Ia4+KH2iVJUEZYE1SgVc=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B18BED788E; Tue, 14 Feb 2017 11:16:50 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id AB8CD8AE4338; Tue, 14 Feb 2017 20:16:56 +0100 (CET)
From: otroan@employees.org
Message-Id: <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Tue, 14 Feb 2017 20:16:56 +0100
In-Reply-To: <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/c8-wr9HcFqTvgytI_CSBDw-6qr0>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:16:53 -0000

--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

>> Yes, but sending at 1280 does not work for IP tunnels. The whole =
purpose of the minimum MTU was to give space for tunnel headers
>> (1500-1280).
>=20
> But, if non-tunnel links set a 1280 MTU which is perfectly OK with the =
standard then
> there is no space for headers. Given the issues with classical PMTUD =
then (plus the
> non-applicability of RFC4821 for tunnels) the only solution for =
tunnels is fragmentation.
> I'll let Joe step in if he wants to.

You are correct. "Does not work for IP tunnels without fragmenting the =
outer header" is what I should have written.
Of course it appears IPv6 fragments have a order of magnitude higher =
drop probability than ICMP PMTUD messages.

Pick your poison.

Best regards,
Ole


--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYo1eoAAoJEL7aWKiYQt92YoYP/R3MJD4Hc99194o2w19VE3Vj
rxE6NM5DQ+oIH/qvh4Wwc4HwkM0vc/Mv28YzDIfwiOeJk1QvBGi8M4vuOJkpQ7/6
IEtG2oJ9ZPs8pI9HmiQw2EKKDoWVbXBd35zhStLOoyJrMOMDPZ/Z23+0oxJUZO3P
dcW//+cdSlGV6z81feohMMgrMsxBLBeEx8YBIxJg2OyDe0DeL3YRSxiShBDY/46h
/qdyprHOWDp3g9Wo1xEU9oaF1pPMmeQGZiiIqATWWxdVCbtWNj/5OJWlUCZLUfyd
Sa06NN3xLFDfdrwtqbBcRoAetSPBHt8VtJE2w5vrM7KQaQQthWWMhXpikVCaGY65
kKctNgHDiaCBgwZDL1OdipEHKBl0HLMAI1mSMAijr6yk2wvl4iBR2niAq/PhLBPd
+pTatokpJMh6H0qO8HEelrJWjSugu694uuR8Fwpy52FJttAsrCQ2pC7lk1Z9iP3F
Em2tYVqwsASlCIZEVKvjh1Er4BY1Ye74O/kJOXw5dnrqOF3YBvcsIADHDmGzRUUo
/ltoqasex4YwMxKePWH7BsU9cjO+cr1LDHWy+mLrTiL0X0kVfXeRq7+Jg97MjeED
wUqnsbgkNKsAz4u+IGwG5o8Fuu8pLMQoGEoIAHTz656xqCt7d8aSjXFn7qEuIuxR
YA43s9akUE8SmcwjFJTl
=xIgR
-----END PGP SIGNATURE-----

--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B--


From nobody Tue Feb 14 11:46:29 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFB912943B; Tue, 14 Feb 2017 11:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5oYeT-FnMMj; Tue, 14 Feb 2017 11:46:16 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 951521297C6; Tue, 14 Feb 2017 11:46:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1EJkFEi011586; Tue, 14 Feb 2017 12:46:16 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EJk7Ts011118 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 12:46:07 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 11:46:06 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 11:46:06 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAAEjdGhAACokzAAEaEMAAAQAsUw
Date: Tue, 14 Feb 2017 19:46:06 +0000
Message-ID: <9ef36e63256448b0b17c91e145ad6fde@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com> <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
In-Reply-To: <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XaaDV-Qr2tBqhHoDwILNV-RvAm8>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:46:18 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Tuesday, February 14, 2017 11:17 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: Stewart Bryant <stewart.bryant@gmail.com>; Brian E Carpenter <brian.e=
.carpenter@gmail.com>; gen-art@ietf.org; 6man WG
> <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Fred,
>=20
> >> Yes, but sending at 1280 does not work for IP tunnels. The whole purpo=
se of the minimum MTU was to give space for tunnel
> headers
> >> (1500-1280).
> >
> > But, if non-tunnel links set a 1280 MTU which is perfectly OK with the =
standard then
> > there is no space for headers. Given the issues with classical PMTUD th=
en (plus the
> > non-applicability of RFC4821 for tunnels) the only solution for tunnels=
 is fragmentation.
> > I'll let Joe step in if he wants to.
>=20
> You are correct. "Does not work for IP tunnels without fragmenting the ou=
ter header" is what I should have written.
> Of course it appears IPv6 fragments have a order of magnitude higher drop=
 probability than ICMP PMTUD messages.

Right. Depending on the encapsulation, however, fragmentation might occur a=
s
some mid-layer between the outer and inner IP headers. For example, a UDP
encapsulation that includes its own fragmentation control fields. In that w=
ay,
the network would only see UDP/IP packets - it would not see IPv6 fragments=
.

GUE is an example UDP encapsulation that include its own fragmentation
control fields:

https://datatracker.ietf.org/doc/draft-herbert-gue-extensions/

> Pick your poison.

As far as RFC 2473 is concerned, you are right. Other encapsulations that
can do the fragmentation at a mid-layer between the inner and outer
IP headers should be OK.

Thanks - Fred

> Best regards,
> Ole



From nobody Tue Feb 14 12:08:25 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105E61297CB for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 12:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o542J-yMyxO3 for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 12:08:22 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71D73129559 for <gen-art@ietf.org>; Tue, 14 Feb 2017 12:08:22 -0800 (PST)
X-AuditID: c6180641-0291898000000a06-b7-58a31d62de45
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by  (Symantec Mail Security) with SMTP id 88.1C.02566.26D13A85; Tue, 14 Feb 2017 16:08:18 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0319.002; Tue, 14 Feb 2017 15:08:20 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSguf8tzHiOyHIvkGLSSyCa1ILvaFh6LsAgABz6ICAAFj0gIAF6ACAgABkiYCAAAZRgIAAA2mAgAAFiQCAAB4zgIAABcOAgAAF6QCAAA7uAA==
Date: Tue, 14 Feb 2017 20:08:20 +0000
Message-ID: <F05298FF-AC49-463B-9539-8C0E0BAE6215@ericsson.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <79dc448c-ac7e-faa2-7fe1-b189262f1d34@gmail.com> <68CF4CA5-76E9-4610-8D58-A18A1DA00175@employees.org>
In-Reply-To: <68CF4CA5-76E9-4610-8D58-A18A1DA00175@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: multipart/signed; boundary="Apple-Mail=_9DAF1ED3-C807-4873-B8EF-D583761C148F"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJIsWRmVeSWpSXmKPExsUyuXSPt26S7OIIg73/VCyuvvrMYjG5bQWb xakHiQ7MHgePfWT02DnrLrvHkiU/mQKYo7hsUlJzMstSi/TtErgy7s08w15wTb/i/7kOlgbG h7pdjJwcEgImEq0TDzN1MXJxCAmsZ5TovXmYBSQhJLCcUeLdX1sQmw2oaMPOz0wgtoiAisT5 ae8Yuxg5OJgFPCWmXE4ACQsL2Ek8WPkdqsReYsHmN2wQdp3Evn9/wOIsAqoSa7YcYwexeYFq bry6zwKxdxurxIr+x6wgCU4BR4m5a96DNTAKiEl8P7UGzGYWEJe49WQ+E8TRIhIPL55mg7BF JV4+/scKYStJTFp6jhVkKLPAFEaJ+zd7WSG2CUqcnPmEZQKjyCwks2Yhq5uFpA6iSF5i+9s5 zLPAHtWRmLyQESJsKvH66Eco21pixq+DbBC2osSU7ofsCxg5VjFylBYX5OSmGxluYgRG2jEJ NscdjHt7PQ8xCnAwKvHwGjxeFCHEmlhWXJl7iFEFqPXRhtUXGKVY8vLzUpVEeDUcFkcI8aYk VlalFuXHF5XmpBYfYpTmYFES570ecj9cSCA9sSQ1OzW1ILUIJsvEwSnVwChtsiA0WUFj2UEz roJbt22F+2ulDzTaPpC8ez1k91UO/SPq91vmButYBreLrNc9crZM+NdZu/QdDzRnvUgomKd4 9rjZkrmv3968s9FzjmYly8nMQxm/fk6891ct6tm1aMElh3Q+Vp/7f9gp8V6CwYuzMWYHJ0z6 V8K7rDJvZmPJZL9p0z9Z5rUpsRRnJBpqMRcVJwIADGw5uLwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6u1uMT8kK75vFUYD9k7NCr1oxLc>
Cc: Gen art <gen-art@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 20:08:24 -0000

--Apple-Mail=_9DAF1ED3-C807-4873-B8EF-D583761C148F
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On Feb 14, 2017, at 2:14 PM, otroan@employees.org wrote:
> 
> Stewart,
> 
> 
>> Maybe we could sort this out faster with a short phone call.
> 
> Yes, we can certainly do that!

Let me know if you would like me to call in as well. 

Thanks
Suresh
--Apple-Mail=_9DAF1ED3-C807-4873-B8EF-D583761C148F
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjE0MjAwODIzWjAjBgkqhkiG9w0B
CQQxFgQU9yDouVKSGxcnvOMW0FSHqVea1kcwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQB9keWFE9EeM5jzkx5Holu4nqppdyeWEgamEMU4GNlDOqKG67GAJv+yBiwlR2dW
+gwwHX1KjcaaJa64gbqMrdHDjKOJMmeaYFs4Vma8S4dVodOI12e/jgtthOBDzO75cUn3EjPfu4K3
kEDs0HUqGM8Q9fE6FUaFBZls3pL+K4BLJFmJ1uZ/lvQdkVlrwqk5SuDLZe507VjlK+Tye5YtoGFL
kQu04SP9OVh8OnyaCqEa4LybS8gYTaTQHdmm20JGGWb/VPSq6E9uaK/9HzHkWg2Ia+kvysyPUJm6
aqtgqH/65lz6hGWe4vksCNkKa0ezMaes7a916k7TLb4+fxf0K/jbAAAAAAAA

--Apple-Mail=_9DAF1ED3-C807-4873-B8EF-D583761C148F--


From nobody Tue Feb 14 15:01:04 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA7712943C; Tue, 14 Feb 2017 15:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xI5hLsRBuYW; Tue, 14 Feb 2017 15:00:56 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19231129407; Tue, 14 Feb 2017 15:00:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v1EN0t9e037093; Tue, 14 Feb 2017 16:00:55 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EN0mhG037037 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 16:00:48 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 15:00:47 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 15:00:47 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAARiaQAAAQYGSA=
Date: Tue, 14 Feb 2017 23:00:47 +0000
Message-ID: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
In-Reply-To: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/EBlRRqcAW0WBcIJTPBPdkf9Lqe0>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:00:58 -0000

Hi Stewart,

> *If*  you care about packet loss

I can say that, for air traffic communications at least, we do care very
much about packet loss.

> then your only option is to probe the path with with
> synthetic data that exactly mimics the live data

Yes, that is exactly correct - so, the probing must be on a per
(session,destination) basis and not just per-destination.

> or not to probe at all and live with the 1280

That is the case for tunnels for sure, but many tunneling specs have
been published with an "optimistic" outlook assuming that the
network can support as much as 1500 minus the length of the=20
encapsulation headers. Unless there is operational assurance of
some size X>1280, however, tunnels have to use fragmentation to
guarantee that - at a minimum - packets up to 1280 will get through.

> As I said 1280 is pretty close to 1496 which is all most networks
> will give you in practice.

Still, I wish for the day that we may eventually see larger path MTUs.
It seems that the only way for sources to safely discover them
however is to employ per-session RFC4821.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 8:45 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Stewart Bryant <stewart.=
bryant@gmail.com>; Brian E Carpenter
> <brian.e.carpenter@gmail.com>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Fred
> *If*  you care about packet loss, then your only option is to probe the
> path with with
> synthetic data that exactly mimics the live data, or not to probe at all
> and live
> with the 1280. As I said 1280 is pretty close to 1496 which is all most
> networks
> will give you in practice.
>=20
> When I think about the people asking for fast re-route to minimise
> packet loss, it seems
> very strange to deliberately induce loss to try to stretch the MTU by 15%=
.
>=20
> - Stewart
>=20
>=20
> On 14/02/2017 16:25, Templin, Fred L wrote:
> > Hi Stewart,
> >
> >> -----Original Message-----
> >> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> >> Sent: Tuesday, February 14, 2017 8:13 AM
> >> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <br=
ian.e.carpenter@gmail.com>; Stewart Bryant
> >> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> >> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.=
org
> >> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>
> >>
> >>
> >> On 14/02/2017 15:50, Templin, Fred L wrote:
> >>>> As to you first point remember that the convergence process disrupts=
 the
> >>>> traffic flow as it does so, and that this will repeat every 10 mins =
as
> >>>> it tries to re-optimise.
> >>> Yes, you are right. So, even in the case of RFC1981bis it might not b=
e a
> >>> good idea to store discovered MTUs in the network layer when there
> >>> is ECMP in the path. (Which could be any time at all.)
> >> Yes, I think if you really care about disruption due to packet loss yo=
ur
> >> best bet is
> >> to go with the minimum supported MTU.
> >>
> >> Forwarding performance is not a issue these days, and core link are ov=
er
> >> provisioned
> >> so you have to wonder how important the efficiency gain is in practice=
.
> >> The efficiency
> >> gain produced by this protocol in most networks (1276 vs 1496) is only
> >> about 15% anyway.
> > So, that would leave us with RFC4821 plus per {session,destination}
> > probing instead of just per-destination probing. Or, just stick with th=
e
> > IPv6 minMTU (1280)?
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >>> You briefly mentioned the authorship in your earlier post. As you wel=
l
> >>> know, the corporate affiliation of two of the authors no longer exist=
s.
> >> My concern was that some authors cannot take part in Auth48 due to not
> >> providing
> >> active email addresses.
> >>
> >> - Stewart
> >>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>> - Stewart
> >>>>
> >>>>
> >>>> On 10/02/2017 15:38, Templin, Fred L wrote:
> >>>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used=
 in the
> >>>>> network as long as ICMP PTBs are not blocked. RFC1981bis will event=
ually
> >>>>> converge to the minimum MTU of all paths in the multipath, and so i=
t is
> >>>>> still OK to store the MTU in the network layer where it would be sh=
ared
> >>>>> by all flows.
> >>>>>
> >>>>> ECMP does present challenges for RFC4821, however. If a first trans=
port
> >>>>> session discovers a large MTU and shares it with a second transport
> >>>>> session, the second session may take a very different path where th=
ere
> >>>>> is a smaller MTU and encounter a black hole. IMHO, it might be a go=
od
> >>>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
> >>>>> problems if discovered MTUs are shared between sessions.
> >>>>>
> >>>>> Thanks - Fred
> >>>>> fred.l.templin@boeing.com
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bry=
ant
> >>>>>> Sent: Friday, February 10, 2017 2:21 AM
> >>>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryan=
t <stewart@g3ysx.org.uk>; gen-art@ietf.org
> >>>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@i=
etf.org
> >>>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>>>>>> Stewart,
> >>>>>>>
> >>>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>>>>>> ...
> >>>>>>>> I wonder if we would best serve both our future and our heritage
> >>>>>>>> if we declared RFC1981 as historic, and either left the idea the=
re,
> >>>>>>>> or declared it as historic and wrote a new text from a clean sta=
rt?
> >>>>>>> I don't see that. It's a stable, widely deployed, interoperable
> >>>>>>> mechanism. That is rather orthogonal to the issue that has been r=
aised,
> >>>>>>> which is that faulty ICMPv6 filtering blocks it on many, many pat=
hs
> >>>>>>> across the Internet.
> >>>>>> I will not debate whether it is faulty or not, but it seems that i=
n
> >>>>>> practice the
> >>>>>> Internet breaks the mechanism. However it breaks it is a way that =
seems
> >>>>>> disruptive to some user traffic. The document is really guidance
> >>>>>> one how hosts might use  ICMP for optimization, and arguable need
> >>>>>> not be a standard at all.
> >>>>>>
> >>>>>> My remark about heritage is that this vintage draft is very much a
> >>>>>> product of
> >>>>>> its time, and really needs modernizing, and after modernizing ough=
t to
> >>>>>> look quite different, and thus maybe we should employ a procedure
> >>>>>> other than a simple replacement.
> >>>>>>
> >>>>>>
> >>>>>>> ...
> >>>>>>>> It is concerning that the draft does not talk in any detail abou=
t
> >>>>>>>> how modern ECMP works, i.e. using the five tuple, and noting tha=
t
> >>>>>>>> the PMTU may be different depending on the transport layer port
> >>>>>>>> numbers.
> >>>>>>> Has this problem been analysed for, say, IPv4? And does the real =
world
> >>>>>>> contain ECMP setups with different MTUs on different paths?
> >>>>>> I don't know if anyone has looked. Since the mechanism is
> >>>>>> self-correcting albeit
> >>>>>> with some disruption to user traffic it looks to the application a=
nd the
> >>>>>> application
> >>>>>> user, just like the Internet not working for a few moments.
> >>>>>>
> >>>>>> In a well managed SP network there should not be, but neither shou=
ld there
> >>>>>> be asymmetric path costs, but there are. The less well manage priv=
ate
> >>>>>> networks are less well managed.
> >>>>>>
> >>>>>>
> >>>>>>>> Given that a very large fraction of packets will traverse an MPL=
S
> >>>>>>>> network at some point, I am surprised that there is no text talk=
ing
> >>>>>>>> about the importance of providing support for this feature in th=
e
> >>>>>>>> MPLS domain. RFC3988 talks to this point, but is only experiment=
al.
> >>>>>>> I don't understand. How does the fact that there might be some MP=
LS
> >>>>>>> segments along the path affect end-to-end PMTUD?
> >>>>>> The point that RFC3988 makes is that MPLS looks like a single hop =
to IP
> >>>>>> and the
> >>>>>> PE has to fragment or has to reply with an ICMP error message to s=
upport
> >>>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrat=
e to
> >>>>>> result
> >>>>>> in the right response at the end node.
> >>>>>>
> >>>>>> My point is that the draft is silent on the subject, and perhaps i=
t
> >>>>>> should not be.
> >>>>>>
> >>>>>> However your question make me ask a further question. The draft is=
 also
> >>>>>> silent
> >>>>>> on NATs. Is there any advice needed for people designing and confi=
guring
> >>>>>> NATs?
> >>>>>>
> >>>>>>>> =3D=3D=3D=3D=3D=3D
> >>>>>>>>
> >>>>>>>>        If flows [I-D.ietf-6man-rfc2460bis] are in use, an implem=
entation
> >>>>>>>>        could use the flow id as the local representation of a pa=
th. Packets
> >>>>>>>>        sent to a particular destination but belonging to differe=
nt flows may
> >>>>>>>>        use different paths, with the choice of path depending on=
 the flow
> >>>>>>>>        id.  This approach will result in the use of optimally si=
zed packets
> >>>>>>>>        on a per-flow basis, providing finer granularity than PMT=
U values
> >>>>>>>>        maintained on a per-destination basis.
> >>>>>>>>
> >>>>>>>> SB> How widely is flow-id supported in networks? I thought that =
the
> >>>>>>>> SB> current position was that it was unreliable as an ECMP indic=
ator
> >>>>>>>> SB> and thus routers tended to glean information from the packet=
 themselves.
> >>>>>>> This is future-proofing. Agreed, usage today is limited.
> >>>>>>>
> >>>>>>> (But it would be better to call it the Flow Label for consistency=
 with other
> >>>>>>> recent RFCs.)
> >>>>>> Well the question is whether it is simply limited today, or broken=
 today
> >>>>>> in a manner that
> >>>>>> is irrecoverable? I don't know, but I do know that the mainstream =
ECMP
> >>>>>> approach
> >>>>>> is the five-tuple. There is something akin to the flow label being
> >>>>>> deployed in MPLS. However
> >>>>>> what distinguishes the MPLS Entropy Label is that it is inserted (=
and
> >>>>>> removed) by the
> >>>>>> service provider and is therefore trusted by the service provider.
> >>>>>>
> >>>>>>> I think your other comments are all valuable.
> >>>>>> Thank you.
> >>>>>>
> >>>>>> Stewart
> >>>>>>
> >>>>>> ------------------------------------------------------------------=
--
> >>>>>> IETF IPv6 working group mailing list
> >>>>>> ipv6@ietf.org
> >>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv=
6
> >>>>>> ------------------------------------------------------------------=
--
> >
>=20



From nobody Tue Feb 14 17:04:39 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8312012953B for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 17:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjH8Q54D0doT for <gen-art@ietfa.amsl.com>; Tue, 14 Feb 2017 17:04:24 -0800 (PST)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253DC12994F for <gen-art@ietf.org>; Tue, 14 Feb 2017 17:04:23 -0800 (PST)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-12v.sys.comcast.net with SMTP id do0DcFwyQ6RIndo18ci5zq; Wed, 15 Feb 2017 01:04:22 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-02v.sys.comcast.net with SMTP id do16cIP3uanCido17cdSBQ; Wed, 15 Feb 2017 01:04:22 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1F14K3c028393; Tue, 14 Feb 2017 20:04:20 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1F14JIs028390; Tue, 14 Feb 2017 20:04:19 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Charlie Perkins <charles.perkins@earthlink.net>
In-Reply-To: <d59427a0-a105-9c10-9de1-86755386d43e@earthlink.net> (charles.perkins@earthlink.net)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 14 Feb 2017 20:04:19 -0500
Message-ID: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfKS5k4ydAZv1A456HK1fKqO6j5y19L1ZpbVVuQFDzw5RJynsm4EAMW/wcjOfIV/X2s1VMEvayTR3vLd+fyExBbJ4s+untlG2qrb6SFcan1fbUFhjyWJi BuWJ2XhXWcrJM9lz9/6nA+ONc7YRHvEIZzAN6p6B9Mj+SD33E4czqMy3Q/LYHEvDJI+QY3qSNkzvw2XpIoLuwqBEyYtWSo35V6QdQZOBWEt02DkGEokD6VkX qaVRCcr4CJFrMjY+moCAJVvIRT2bi5AXh8g2OMgkykVP8wp5PlSLFJlZv7DcnV7T
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6KMaxgqo2Gr5W82ASkAZtsQiFVE>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:04:25 -0000

Charlie Perkins <charles.perkins@earthlink.net> writes:
> I am hesitant to replace so many MNID types by a single URN type with 
> substructure.  What would you think about replacing the existing 
> RFID-*-URI types with a single URN type, but leaving the existing binary 
> types?  This gets the benefit you suggest for future extensibility, but 
> retains the shorter forms that may often be advantageous.

Suddenly today I realized something I should have realized in the
review, which would have saved us much time in discussion.  Viz.,
consider this proposal:

- one MNID type for *all* the EPC binary schemes

- one MNID type for *all* URNs, *including* the EPC URI forms

This would work, since (1) (not surprisingly) the EPC binary schemes are
all differentiated by their first 8 bits.  (see table on page 19 of the
tag-data standard,
http://www.gs1.org/gsmp/kc/epcglobal/tds/tds_1_1_rev_1_27-standard-20050510.pdf)
and (2) all URNs are differentiated by their namespace part.

(This parallels using one MNID number for all DUID types, since DUIDs
have an internal indicator for the four types.)

This approach has all the desirable properties anyone has mentioned so
far:

- includes all EPC binary and URI forms
- automatically includes all existing and future EPC binary forms
- automatically includes all existing and future URN forms *including*
  all existing and future EPC URI forms
- doesn't have a proliferation of MNID type numbers which duplicate
  information that can be fairly easily extracted from the
  identifier itself
- includes all the short EPC forms, allowing brevity when that is
  desirable

This seems to be practical, simple, and almost as elegant as possible.
What do you think?

> I changed the text as follows:
>
>>     Some MNIDs contain sensitive identifiers which, as used in protocols
>>     specified by other SDOs, are only used for signaling during initial
>>     network entry.  In such protocols, subsequent exchanges then rely on
>>     a temporary identifier allocated during the initial network entry.
>>     Managing the association between long-lived and temporary identifiers
>>     is outside the scope of this document.
>
> I can't remember exactly why this text was added - it was a long time 
> ago.  But anyway the main point is to simply mention that there may be 
> associations between some of the MNID types that might be important from 
> a security standpoint, without meaning to go into examples.

Certainly the new text is clear enough.

Dale


From nobody Tue Feb 14 20:06:45 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FCA7129984; Tue, 14 Feb 2017 20:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpFpSLNjuPdM; Tue, 14 Feb 2017 20:06:38 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F41D0129586; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 65so108868934otq.2; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WIY/rdVxy09tB7PrJoES46Zjm2UJ5syfwN9D8wrDtXM=; b=N/BJgCrWjZV/WTDeAdfBmDpkky/wyepCQ/abnpWLNa9Z4goxO8+W+dnqEBETdKrw49 a+QWsEZ5F7AfDZNkarhwTpIrzKLG/7L4SEoJ99r30pHsRFx6CaESa/15H8tLSHmyfTpn /T/0b5LmZwDIKetkHZEiTAAXzgQMinodyW8Bjkfqo6SW2WWjK4NCNgbDKlO7pRZoQDdr qX1HC391LUWMetcJpWKNJp+Eu0+zfiw+EjJXvTTWgfYVee4v+kAM2ztSBJgsHESv+sYC 1tC7XK0g7qApzoTZ7EaNQnjvxac2/DmENUF8P/ueiaAJzW3szv5NIL8ppiN9+LXvL+4b xvFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WIY/rdVxy09tB7PrJoES46Zjm2UJ5syfwN9D8wrDtXM=; b=kGqJuK+AaITqa7Mx9AB+6wFwRI4CTWfZyKD+gFKqrFHKhsss1Pc4WCvcdlOkh3sWs5 uhdKbUOrYhvoIzjyu68N64rvgaol1I8k15ofkYb66wFMhapSMqeCJyoTUrCYoU57jqVP n1r814YeiISysrfmNfLD4Yqf5/8sYhj8u3NZ6sYpzQHP3KbioC9MRoK8HXkkfQvB7gJX HS6Bn3r8i2jYVdr4Ky3huNiVLabWvWYC4lWIuwBJ3Y0ZLaJua6+Pe/WhX3p8508DFMw5 ud1OuGf3MDLbQSV/LiVPFCoPVLhKiOBpdrE0B0slpt2rUBR9BsBvwYtMyxLNOuacWssl x+KQ==
X-Gm-Message-State: AMke39nYJzmEk6BPd3FxLwa+yMDbORoKkNztSb/RsJRissnMBTrhiQMdVyvAcF31AL83c7UCQn3gKnL/NoFTxQ==
X-Received: by 10.157.9.242 with SMTP id 47mr46600otz.128.1487131597225; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Tue, 14 Feb 2017 20:06:36 -0800 (PST)
In-Reply-To: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 14 Feb 2017 20:06:36 -0800
Message-ID: <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a113e451c964681054889cea9
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/I4wR66ta1B_tcLxG-Q2fiFj3wQs>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 04:06:39 -0000

--001a113e451c964681054889cea9
Content-Type: text/plain; charset=UTF-8

Hi Robert,
Section 5 Data Plane Theory of Operation has the following recommendation
on reading time value at ingress and egress:

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.


Do you find the text sufficient in providing guidance to an implementer of RTM?


Regards,

Greg


On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-mpls-residence-time-13
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-01-17
> IESG Telechat date: 2017-03-02
>
> Summary: Ready for publication as PS
>
> Thanks for addressing my comments.
> (I still think some discussion about taking arrival and departure time
> measurements would be helpful, even if it only said "do it
> consistently so you don't indicate jitter that's not really there".)
>
>

--001a113e451c964681054889cea9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>Section 5 Data Plane Theory of Operation ha=
s the following recommendation on reading time value at ingress and egress:=
</div><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre><pre class=3D"gmai=
l-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;co=
lor:rgb(0,0,0)"><br></pre><pre class=3D"gmail-newpage" style=3D"font-size:1=
3.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the=
 text sufficient in providing guidance to an implementer of RTM?</pre><pre =
class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-=
bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-newpage" style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">=
Regards,</pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;mar=
gin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre></div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Feb 13, 2017 a=
t 1:51 PM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@n=
ostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Reviewer: Robert Sparks<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-mpls-residence-<wbr>time-13<br>
Reviewer: Robert Sparks<br>
Review Date: 2017-02-13<br>
IETF LC End Date: 2017-01-17<br>
IESG Telechat date: 2017-03-02<br>
<br>
Summary: Ready for publication as PS<br>
<br>
Thanks for addressing my comments.<br>
(I still think some discussion about taking arrival and departure time<br>
measurements would be helpful, even if it only said &quot;do it<br>
consistently so you don&#39;t indicate jitter that&#39;s not really there&q=
uot;.)<br>
<br>
</blockquote></div><br></div>

--001a113e451c964681054889cea9--


From nobody Wed Feb 15 04:58:36 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DEA1295C1; Wed, 15 Feb 2017 04:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPmyj6w2sUYe; Wed, 15 Feb 2017 04:58:32 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D85991295F1; Wed, 15 Feb 2017 04:58:30 -0800 (PST)
Received: from givry.fdupont.fr (localhost [IPv6:::1]) by givry.fdupont.fr (8.14.7/8.14.7) with ESMTP id v1FCmL5E014275; Wed, 15 Feb 2017 13:48:21 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201702151248.v1FCmL5E014275@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 15 Feb 2017 13:48:21 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/JpkmaCvfpMRxEIZ86NMYYubHLQg>
Cc: draft-kivinen-802-15-ie.all@ietf.org
Subject: [Gen-art] review of draft-kivinen-802-15-ie-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 12:58:34 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-kivinen-802-15-ie-04.txt
Reviewer: Francis Dupont
Review Date: 20170210
IETF LC End Date: 20170214
IESG Telechat date: 20170224

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: 
 - ToC page 1 and 3 page 3 (title): Benefitting -> Benefiting

 - 3 page 3 (suggest):  CoRE etc, ->  CoRE, etc,

 - 4 page 3: reading the document I had a question about the "no need
  ... to specify the internal structure" but the reason became clear
  the next page. So I have no concern about this.

Regards 

Francis.Dupont@fdupont.fr


From nobody Wed Feb 15 05:06:18 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5153D129573; Wed, 15 Feb 2017 05:06:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148716397728.17360.7152265828165061314.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 05:06:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tQD4GDWgN-xOgIuw9PL_Cu7GnoE>
Cc: draft-freytag-lager-variant-rules.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-freytag-lager-variant-rules-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 13:06:17 -0000

Reviewer: Francis Dupont
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-freytag-lager-variant-rules-??
Reviewer: Francis Dupont
Review Date: 2017-02-15
IETF LC End Date: 2017-02-14
IESG Telechat date: 2017-02-16

Summary: Ready with Issues

Major issues: None

Minor issues: As I explained in my review of the 02 version this
document introduction should warn that the RFC 7940 must be read
before...

Nits/editorial comments: 



From nobody Wed Feb 15 07:49:48 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4AE1294FA; Wed, 15 Feb 2017 07:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8tZ9jlIxlgO; Wed, 15 Feb 2017 07:49:41 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A27F5129630; Wed, 15 Feb 2017 07:43:02 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1FFh0Sd047339 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 15 Feb 2017 09:43:01 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
Date: Wed, 15 Feb 2017 09:43:00 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8A6A2E153845792501B20E33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ipFq3wkxgmlcEvhEivHmKrJo0lA>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 15:49:43 -0000

This is a multi-part message in MIME format.
--------------8A6A2E153845792501B20E33
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit



On 2/14/17 10:06 PM, Greg Mirsky wrote:
> Hi Robert,
> Section 5 Data Plane Theory of Operation has the following 
> recommendation on reading time value at ingress and egress:
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface;
>     this should be done as close to the physical layer as possible to
>     ensure precise accuracy in time determination.
> Do you find the text sufficient in providing guidance to an implementer of RTM?
Well, no - that was point in the text from my review of -12 that caused 
me to make comment in the first place.

What does "precise accuracy" even _MEAN_? You're waving your hands with 
words that don't help the reader guess what you mean at the moment. The 
subsequent email exchange said the important part was that you measure 
_precisely_ (in that the measurements are always taken the same way), 
but accuracy isn't that important (you've (and here by "you" I mean the 
set of people that have responded to the review") told me it's not 
important whether the reading is taken at the beginning of the 
bit-stream, the end, or several 1000 nanoseconds after the last bit came 
off the physical media as long as it's done the same way for each 
packet). The fact that you're carrying a measurement that can talk about 
times smaller than the interarrival time for individual bits for some 
real world line speeds says that different implementations taking the 
measurement different ways is going to result in different residence 
time measurements, even if the residence time was really identical. 
You've told me that's not important to the protocol using the 
measurement as long as the an individual implementation doesn't 
introduce something that will look to the using protocol like jitter 
that's not really there.

The text does not say that to an implementer right now.

To restate that long paragraph with maybe a longer one,  assume a 
simplified world where everything is perfectly constant. Packets are all 
flowing at the same size and same rate. For reference, I assert that the 
time between the first bit of a packet entering the system taking the 
measurement and the first bit of that packet leaving the system is 
exactly T (every time). You are telling me that if the system returns cT 
for some constant T other than 1 (and not necessarily  close to 1), 
everything is fine. You're also telling me that if you replace the 
system with another that preserves T, but measures differently so that 
it returns c'T where c' != c, everything is fine. The important part to 
you is that c and c' don't change for their respective systems. (That 
surprises me, I can see how the way the clocks are going to use this 
will do the right thing, but I can't help but think someone later will 
look at the difference between the two systems and say something is 
wrong with one of them). What you've told me is not fine is that if you 
drop i a third system that also preserves T but reports aT where a 
_varies_ over some range.

Have I heard you correctly?
> Regards,
> Greg
>
> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>     Reviewer: Robert Sparks
>     Review result: Ready
>
>     I am the assigned Gen-ART reviewer for this draft. The General Area
>     Review Team (Gen-ART) reviews all IETF documents being processed
>     by the IESG for the IETF Chair. Please wait for direction from your
>     document shepherd or AD before posting a new version of the draft.
>
>     For more information, please see the FAQ at
>
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>
>     Document: draft-ietf-mpls-residence-time-13
>     Reviewer: Robert Sparks
>     Review Date: 2017-02-13
>     IETF LC End Date: 2017-01-17
>     IESG Telechat date: 2017-03-02
>
>     Summary: Ready for publication as PS
>
>     Thanks for addressing my comments.
>     (I still think some discussion about taking arrival and departure time
>     measurements would be helpful, even if it only said "do it
>     consistently so you don't indicate jitter that's not really there".)
>
>


--------------8A6A2E153845792501B20E33
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/14/17 10:06 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>Section 5 Data Plane Theory of Operation has the following
          recommendation on reading time value at ingress and egress:</div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
        </div>
      </div>
    </blockquote>
    Well, no - that was point in the text from my review of -12 that
    caused me to make comment in the first place.<br>
    <br>
    What does "precise accuracy" even _MEAN_? You're waving your hands
    with words that don't help the reader guess what you mean at the
    moment. The subsequent email exchange said the important part was
    that you measure _precisely_ (in that the measurements are always
    taken the same way), but accuracy isn't that important (you've (and
    here by "you" I mean the set of people that have responded to the
    review") told me it's not important whether the reading is taken at
    the beginning of the bit-stream, the end, or several 1000
    nanoseconds after the last bit came off the physical media as long
    as it's done the same way for each packet). The fact that you're
    carrying a measurement that can talk about times smaller than the
    interarrival time for individual bits for some real world line
    speeds says that different implementations taking the measurement
    different ways is going to result in different residence time
    measurements, even if the residence time was really identical.
    You've told me that's not important to the protocol using the
    measurement as long as the an individual implementation doesn't
    introduce something that will look to the using protocol like jitter
    that's not really there.<br>
    <br>
    The text does not say that to an implementer right now.<br>
    <br>
    To restate that long paragraph with maybe a longer one,  assume a
    simplified world where everything is perfectly constant. Packets are
    all flowing at the same size and same rate. For reference, I assert
    that the time between the first bit of a packet entering the system
    taking the measurement and the first bit of that packet leaving the
    system is exactly T (every time). You are telling me that if the
    system returns cT for some constant T other than 1 (and not
    necessarily  close to 1), everything is fine. You're also telling me
    that if you replace the system with another that preserves T, but
    measures differently so that it returns c'T where c' != c,
    everything is fine. The important part to you is that c and c' don't
    change for their respective systems. (That surprises me, I can see
    how the way the clocks are going to use this will do the right
    thing, but I can't help but think someone later will look at the
    difference between the two systems and say something is wrong with
    one of them). What you've told me is not fine is that if you drop i
    a third system that also preserves T but reports aT where a _varies_
    over some range.<br>
    <br>
    Have I heard you correctly?<br>
    <blockquote
cite="mid:CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, Robert
          Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer:
            Robert Sparks<br>
            Review result: Ready<br>
            <br>
            I am the assigned Gen-ART reviewer for this draft. The
            General Area<br>
            Review Team (Gen-ART) reviews all IETF documents being
            processed<br>
            by the IESG for the IETF Chair. Please wait for direction
            from your<br>
            document shepherd or AD before posting a new version of the
            draft.<br>
            <br>
            For more information, please see the FAQ at<br>
            <br>
            &lt;<a moz-do-not-send="true"
              href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
              rel="noreferrer" target="_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq</a>&gt;.<br>
            <br>
            Document: draft-ietf-mpls-residence-<wbr>time-13<br>
            Reviewer: Robert Sparks<br>
            Review Date: 2017-02-13<br>
            IETF LC End Date: 2017-01-17<br>
            IESG Telechat date: 2017-03-02<br>
            <br>
            Summary: Ready for publication as PS<br>
            <br>
            Thanks for addressing my comments.<br>
            (I still think some discussion about taking arrival and
            departure time<br>
            measurements would be helpful, even if it only said "do it<br>
            consistently so you don't indicate jitter that's not really
            there".)<br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------8A6A2E153845792501B20E33--


From nobody Wed Feb 15 08:32:18 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDC2E129564 for <gen-art@ietf.org>; Wed, 15 Feb 2017 08:32:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Jean Mahoney" <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148717633673.17336.12073235248277588991.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 08:32:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/NH8NBp_wdJJacFowYUivranVUAQ>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: mahoney@nostrum.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:32:17 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-02-16

Reviewer               Type      LC end     Draft
Orit Levin             Last Call 2017-01-31 draft-ietf-sidr-delta-protocol-07
Lucy Yong              Last Call 2017-01-30 draft-ietf-sidr-rpki-rtr-rfc6810-bis-08

For telechat 2017-03-02

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-02-20 draft-ietf-httpbis-rfc5987bis-04
Ralph Droms            Telechat  2017-02-07 draft-ietf-nfsv4-rfc5666bis-10 *
Meral Shirazipour      Telechat  2017-02-07 draft-ietf-nfsv4-rpcrdma-bidirection-07 *
Meral Shirazipour      Last Call 2017-02-10 draft-ietf-dmm-hnprenum-05
Peter Yee              Last Call 2017-03-01 draft-ietf-6man-rfc2460bis-08

For telechat 2017-03-16

Reviewer               Type      LC end     Draft
Stewart Bryant         Telechat  2017-01-30 draft-ietf-lamps-eai-addresses-06 *
Roni Even              Last Call 2017-02-27 draft-ietf-dime-load-07
Fernando Gont          Last Call 2017-01-23 draft-ietf-dime-agent-overload-09
Joel Halpern           Last Call 2017-02-28 draft-ietf-pce-stateful-pce-18
Christer Holmberg      Last Call 2017-02-28 draft-ietf-pce-stateful-sync-optimizations-08
Jouni Korhonen         Telechat  2016-10-24 draft-ietf-ccamp-ospf-availability-extension-09 *
Matthew Miller         Last Call 2017-03-13 draft-mm-wg-effect-encrypt-07

Last calls:

Reviewer               Type      LC end     Draft
Francis Dupont         Last Call 2017-02-24 draft-ietf-dmm-lma-controlled-mag-params-03
Fernando Gont          Last Call 2017-02-27 draft-ietf-urnbis-rfc2141bis-urn-20
Paul Kyzivat           Last Call 2017-03-10 draft-bchv-rfc6890bis-04
Dale Worley            Last Call 2017-02-20 draft-ietf-slim-negotiating-human-language-06

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Roni Even
  Fernando Gont
  Vijay Gurbani
  Wassim Haddad
  Joel Halpern
  Christer Holmberg
  Russ Housley
  Jouni Korhonen
  Paul Kyzivat
  Orit Levin

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Wed Feb 15 08:50:44 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 633CA1295B2; Wed, 15 Feb 2017 08:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ok8EPOgBdOIU; Wed, 15 Feb 2017 08:50:38 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E745D1294BF; Wed, 15 Feb 2017 08:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4817; q=dns/txt; s=iport; t=1487177438; x=1488387038; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LvaLyYXBEHd/sV2pU29zz1G76QP7etmzTklSI2CI5R0=; b=P9/il7gp/kWRZodNyqfenNij1OWOt1m3F44EcOl0ws6iZUsPtZpvXhyQ R5mnwpY1g1I5NOpUetexUjh7YW/X5kSXAHlvL5/I81hkhSu3Shrc4wSav rzSrbFJgwxkSw+Xub0xk1jHddlAQ5BrF954LvSc255U8X2JfJMWg9Rmfx M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAQBVhqRY/4UNJK1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1KBageNWqdGggyGIgKCEz8YAQIBAQEBAQEBYiiEcQYOLCsUEAIBCDY?= =?us-ascii?q?QMiUCBA4FiWuyVIs8AQEBAQEBAQEBAQEBAQEBAQEBAQEehk2Eb4QmEQGGAQWbd?= =?us-ascii?q?wGSE4F7hReJdJMWAR84eAhRFYUCHYFhdYgkgSGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,166,1484006400"; d="scan'208";a="386049403"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Feb 2017 16:50:36 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v1FGoaqY008674 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Feb 2017 16:50:36 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 15 Feb 2017 10:50:35 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Wed, 15 Feb 2017 10:50:35 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "Dale R. Worley" <worley@ariadne.com>
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSh6ugGmBv2a9UCEeirDF7S0m5iA==
Date: Wed, 15 Feb 2017 16:50:35 +0000
Message-ID: <D4C9C46E.259E23%sgundave@cisco.com>
References: <D4C63E24.2598D8%sgundave@cisco.com> <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <581AF40AA8C8B448A365053BBAEE2D0C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oe9h4Ut-0V7YIkZwbiOCvOnumaA>
Cc: "charles.perkins@earthlink.net" <charles.perkins@earthlink.net>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:50:39 -0000

HI Dale,

Thanks again for the comments. Please see inline.




On 2/13/17, 8:55 AM, "Dale R. Worley" <worley@ariadne.com> wrote:

>"Sri Gundavelli (sgundave)" <sgundave@cisco.com> writes:
>> When we discussed this issue in the past, the general feedback from
>> the WG was that the draft should provide some minimal amount of
>> details on the new identifier types, what the identifier is, how the
>> identifier is constructed, what is the access technology and a
>> reference to the specification that provides that definition. The idea
>> is NOT TO provide extensive details on the spec, but to enable a
>> reader with some high level details and a pointer to the
>> specification. I tend to think the text in the current specification
>> just does that. If the text is seen as redundant text, we can
>> certainly add a statement saying that the definition for the
>> identifier is provided in spec-XYZ and is repeated here for
>> convenience. May be other folks in the WG have some views on this.
>
>I take it that the following are typical comments from the WG:
>
>> Comments from 10/11/2015 email:
>>
>> "Some text on the motivation for defining new Types may be
>> helpful. Document is not just standardizing the currently
>> in-use/popular identifier types, its also introducing new types are
>> not in use. The reasons/interest for defining identifiers that are
>> tied to the physical elements of the device (RFID, MAC address ..etc)
>> and how it helps in deployment of the technology may be useful. Few
>> lines of text will really help."
>>
>> "I was hoping to see a sub-section for each of the types. We cannot
>> standardize a identifier type without providing any explanation on the
>> identifier type or the references to the base definitions. This can be
>> painful, but I'd have a small section for each of the types. It can be
>> 3 line text on the a.) Definition b.) Format c.) Example format d.)
>> Reference to the base spec that defines those identifiers."
>
>I can understand these desires, and I agree with following them.
>
>In regard to the first message, it seems to request "The
>reasons/interest for defining identifiers that are tied to the physical
>elements of the device (RFID, MAC address ..etc) and how it helps in
>deployment of the technology may be useful."  As far as I can tell, this
>isn't handled in section 4.9 (which is the part I was complaining
>about).  And I don't recall if the earlier parts of the draft are
>specific about "the reasons/interest" for any of the new types.  I
>believe from this discussion that the reason an identifier was included
>is that somebody told the authors that they wanted to use the identifier
>in question -- and that is quite legitimate.  Perhaps saying it
>explicitly in the early parts of the draft would help.
>
>In regard to the second message, it seems to request
>
>    a small section for each of the types. It can be
>    3 line text on the
>	a.) Definition
>	b.) Format
>	c.) Example format
>	d.) Reference to the base spec that defines those identifiers.
>
>Of course, (d) "reference to base spec" is necessary, and the
>sub-sections of 4.9 do that for each format, as does Table 1.
>
>For (a) "definition", the texts in 4.9 proper seem to be fairly good.
>E.g.,
>
>   The EPC encoding scheme for SGTIN permits the direct embedding of
>   EAN.UCC System standard GTIN and Serial Number codes on EPC tags.  In
>   all cases, the check digit is not encoded.  Two encoding schemes are
>   specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits).
>
>Based on that alone, I couldn't possibly construct a SGTIN-64 myself,
>but I have some idea of the information it contains and the technical
>terms to look up to find the real definition of the data items.
>
>However (b) "format" seems to be missing (except in the most abstract
>sense) and (c) "example format" seem to be missing entirely.  OTOH, I'm
>not sure that the space needed to specify those would be worth the
>effort.

[Sri] I agree. The goal was to make the spec complete. What ever
identifiers we are carrying in this option, we provide the format,
structure and semantics of construction and not treat it like an opaque
container. But, its a delicate balance, not ending up with a lot of
duplicated text, vs incomplete specification. I agree, its not worth the
efforts doing a significant re-write. The current text is probably fine.


>
>Summary:  After thinking about it more, I think it's not worth the
>effort to revise 4.9 heavily.  Most of that information is for the use
>of people who are familiar with the RFID identifiers and their formats,
>and if they are happy with it, there's no reason to change it.

[Sri] I agree with your summary.




>
>Dale


From nobody Wed Feb 15 09:21:08 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B46E129698; Wed, 15 Feb 2017 09:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5T4O587CNnWC; Wed, 15 Feb 2017 09:20:57 -0800 (PST)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFAD6129696; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
Received: by mail-ot0-x22e.google.com with SMTP id 19so10190279oti.2; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rRy/Ira7tW7hiadGek2cEb3JfgqVyhLnuAc3yFRlVts=; b=RbfEq1MYKaDltVnDd86h/Y/n8V/QES6hVcIXk4WsV4IbgqnnLzVMplLXZh2JiLUNab V8D2VQ6i2RfppjmgSSCrmkmmEKhdKR5jyuwQ24RsqS9/rV2Rx6oMuj4ZyCjgVGs2yHSo sFbAtUOalzzEZ15/UqaBS1lCLVmMJjdu9ZG6FYq7v1eO3sfnMUDddLrdB7FJhIYx048F kIMWJpn0t+Nvc8bceO2IBMduTNG5gCkOLAj+ev+yKEfPtz40MCFfWTzN35q0PKTFRxbb awh1CCWIsi+jwydoLquat+oPs9fQ8yzISWyd/ecDiQjlpOqQiWD/rXWgt9yZS0PdReox TNUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rRy/Ira7tW7hiadGek2cEb3JfgqVyhLnuAc3yFRlVts=; b=CoO+qECGbRDm9YyQTR94qq4784vTpyZ63FjzLP0aBDNgG5nXnMlnAZadPyALBV6qk6 wOLUp0I09wQfuso6FMI15MJ8/WBkafScwJ08NY8CQqTtjYdnJKXh/lMVNif2ucKJZI5u j+NR6iUNzJSFKGILk8HiuGAYN/d6BLyXEThBc6OwBOmGZy2SuJCoV9ZFYwSGno42u9zD 89EJWMjV+LhBMxx7wt69sVK1nVJ5J4U0j8PByWAQvBVcSs6S1bRwzS5E/VV7cVtWWJYW JzLQT+vPzOgsfikXEP/Fg16RS6kO7mKxn+nS4NRG2GBlinviQrekuUGsgL0DIMjth8ti Ju4w==
X-Gm-Message-State: AMke39krRQ9Dg+ZqYlyTn33PvF+PAoGz1M5VN3ss91xlLPenQvaUIMCE18ztz/cXfS9VW3fbG9Zu/ascogKf7g==
X-Received: by 10.157.16.9 with SMTP id h9mr18682836ote.40.1487179256229; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Wed, 15 Feb 2017 09:20:55 -0800 (PST)
In-Reply-To: <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 15 Feb 2017 09:20:55 -0800
Message-ID: <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a11402c0248f5be054894e765
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/pxasq0umBPqOt8oc5Ocp4l8iKbY>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 17:20:59 -0000

--001a11402c0248f5be054894e765
Content-Type: text/plain; charset=UTF-8

Hi Robert,
yes, you've absolutely correct in your example. The importance of RTM is to
exclude and quantify, as much as possible, jitter from propagation delay.
I've updated the wording to reflect that. Below is new text I propose,
please let me know if it makes it clearer.

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.

Regards,

Greg


On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

>
>
> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>
> Hi Robert,
> Section 5 Data Plane Theory of Operation has the following recommendation
> on reading time value at ingress and egress:
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface;
>    this should be done as close to the physical layer as possible to
>    ensure precise accuracy in time determination.
>
> Do you find the text sufficient in providing guidance to an implementer of RTM?
>
> Well, no - that was point in the text from my review of -12 that caused me
> to make comment in the first place.
>
> What does "precise accuracy" even _MEAN_? You're waving your hands with
> words that don't help the reader guess what you mean at the moment. The
> subsequent email exchange said the important part was that you measure
> _precisely_ (in that the measurements are always taken the same way), but
> accuracy isn't that important (you've (and here by "you" I mean the set of
> people that have responded to the review") told me it's not important
> whether the reading is taken at the beginning of the bit-stream, the end,
> or several 1000 nanoseconds after the last bit came off the physical media
> as long as it's done the same way for each packet). The fact that you're
> carrying a measurement that can talk about times smaller than the
> interarrival time for individual bits for some real world line speeds says
> that different implementations taking the measurement different ways is
> going to result in different residence time measurements, even if the
> residence time was really identical. You've told me that's not important to
> the protocol using the measurement as long as the an individual
> implementation doesn't introduce something that will look to the using
> protocol like jitter that's not really there.
>
> The text does not say that to an implementer right now.
>
> To restate that long paragraph with maybe a longer one,  assume a
> simplified world where everything is perfectly constant. Packets are all
> flowing at the same size and same rate. For reference, I assert that the
> time between the first bit of a packet entering the system taking the
> measurement and the first bit of that packet leaving the system is exactly
> T (every time). You are telling me that if the system returns cT for some
> constant T other than 1 (and not necessarily  close to 1), everything is
> fine. You're also telling me that if you replace the system with another
> that preserves T, but measures differently so that it returns c'T where c'
> != c, everything is fine. The important part to you is that c and c' don't
> change for their respective systems. (That surprises me, I can see how the
> way the clocks are going to use this will do the right thing, but I can't
> help but think someone later will look at the difference between the two
> systems and say something is wrong with one of them). What you've told me
> is not fine is that if you drop i a third system that also preserves T but
> reports aT where a _varies_ over some range.
>
> Have I heard you correctly?
>
> Regards,
>
> Greg
>
>
> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>> Reviewer: Robert Sparks
>> Review result: Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair. Please wait for direction from your
>> document shepherd or AD before posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-mpls-residence-time-13
>> Reviewer: Robert Sparks
>> Review Date: 2017-02-13
>> IETF LC End Date: 2017-01-17
>> IESG Telechat date: 2017-03-02
>>
>> Summary: Ready for publication as PS
>>
>> Thanks for addressing my comments.
>> (I still think some discussion about taking arrival and departure time
>> measurements would be helpful, even if it only said "do it
>> consistently so you don't indicate jitter that's not really there".)
>>
>>
>
>

--001a11402c0248f5be054894e765
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>yes, you&#39;ve absolutely correct in your =
example. The importance of RTM is to exclude and quantify, as much as possi=
ble, jitter from propagation delay. I&#39;ve updated the wording to reflect=
 that. Below is new text I propose, please let me know if it makes it clear=
er.</div><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-spa=
ce:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre><pre style=3D"color:rgb(0,0,0);word=
-wrap:break-word;white-space:pre-wrap">Regards,</pre><pre style=3D"color:rg=
b(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre></div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 15, 20=
17 at 7:43 AM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjspar=
ks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <p><br>
    </p>
    <br>
    <div class=3D"m_3072934530585377958moz-cite-prefix">On 2/14/17 10:06 PM=
, Greg Mirsky wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <div>Section 5 Data Plane Theory of Operation has the following
          recommendation on reading time value at ingress and egress:</div>
        <div>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RT=
M-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you fin=
d the text sufficient in providing guidance to an implementer of RTM?</pre>
        </div>
      </div>
    </blockquote></span>
    Well, no - that was point in the text from my review of -12 that
    caused me to make comment in the first place.<br>
    <br>
    What does &quot;precise accuracy&quot; even _MEAN_? You&#39;re waving y=
our hands
    with words that don&#39;t help the reader guess what you mean at the
    moment. The subsequent email exchange said the important part was
    that you measure _precisely_ (in that the measurements are always
    taken the same way), but accuracy isn&#39;t that important (you&#39;ve =
(and
    here by &quot;you&quot; I mean the set of people that have responded to=
 the
    review&quot;) told me it&#39;s not important whether the reading is tak=
en at
    the beginning of the bit-stream, the end, or several 1000
    nanoseconds after the last bit came off the physical media as long
    as it&#39;s done the same way for each packet). The fact that you&#39;r=
e
    carrying a measurement that can talk about times smaller than the
    interarrival time for individual bits for some real world line
    speeds says that different implementations taking the measurement
    different ways is going to result in different residence time
    measurements, even if the residence time was really identical.
    You&#39;ve told me that&#39;s not important to the protocol using the
    measurement as long as the an individual implementation doesn&#39;t
    introduce something that will look to the using protocol like jitter
    that&#39;s not really there.<br>
    <br>
    The text does not say that to an implementer right now.<br>
    <br>
    To restate that long paragraph with maybe a longer one,=C2=A0 assume a
    simplified world where everything is perfectly constant. Packets are
    all flowing at the same size and same rate. For reference, I assert
    that the time between the first bit of a packet entering the system
    taking the measurement and the first bit of that packet leaving the
    system is exactly T (every time). You are telling me that if the
    system returns cT for some constant T other than 1 (and not
    necessarily=C2=A0 close to 1), everything is fine. You&#39;re also tell=
ing me
    that if you replace the system with another that preserves T, but
    measures differently so that it returns c&#39;T where c&#39; !=3D c,
    everything is fine. The important part to you is that c and c&#39; don&=
#39;t
    change for their respective systems. (That surprises me, I can see
    how the way the clocks are going to use this will do the right
    thing, but I can&#39;t help but think someone later will look at the
    difference between the two systems and say something is wrong with
    one of them). What you&#39;ve told me is not fine is that if you drop i
    a third system that also preserves T but reports aT where a _varies_
    over some range.<br>
    <br>
    Have I heard you correctly?<span class=3D""><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</=
pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, Robert
          Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.c=
om" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Reviewer:
            Robert Sparks<br>
            Review result: Ready<br>
            <br>
            I am the assigned Gen-ART reviewer for this draft. The
            General Area<br>
            Review Team (Gen-ART) reviews all IETF documents being
            processed<br>
            by the IESG for the IETF Chair. Please wait for direction
            from your<br>
            document shepherd or AD before posting a new version of the
            draft.<br>
            <br>
            For more information, please see the FAQ at<br>
            <br>
            &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" r=
el=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wik=
i/GenArtfaq</a>&gt;.<br>
            <br>
            Document: draft-ietf-mpls-residence-time<wbr>-13<br>
            Reviewer: Robert Sparks<br>
            Review Date: 2017-02-13<br>
            IETF LC End Date: 2017-01-17<br>
            IESG Telechat date: 2017-03-02<br>
            <br>
            Summary: Ready for publication as PS<br>
            <br>
            Thanks for addressing my comments.<br>
            (I still think some discussion about taking arrival and
            departure time<br>
            measurements would be helpful, even if it only said &quot;do it=
<br>
            consistently so you don&#39;t indicate jitter that&#39;s not re=
ally
            there&quot;.)<br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </span></div>

</blockquote></div><br></div>

--001a11402c0248f5be054894e765--


From nobody Wed Feb 15 11:15:38 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2841293E0; Wed, 15 Feb 2017 11:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQibP_bl5vs5; Wed, 15 Feb 2017 11:15:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F9581296F2; Wed, 15 Feb 2017 11:15:30 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1FJFSuQ072323 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 15 Feb 2017 13:15:29 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
Date: Wed, 15 Feb 2017 13:15:28 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8EF8ACD6F400BCC5968C8777"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/hV2GviZqBz6wbHVIcwHqMV4t80E>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 19:15:34 -0000

This is a multi-part message in MIME format.
--------------8EF8ACD6F400BCC5968C8777
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit



On 2/15/17 11:20 AM, Greg Mirsky wrote:
> Hi Robert,
> yes, you've absolutely correct in your example. The importance of RTM 
> is to exclude and quantify, as much as possible, jitter from 
> propagation delay. I've updated the wording to reflect that. Below is 
> new text I propose, please let me know if it makes it clearer.
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface.
>     These actions should be done as close to the physical layer as
>     possible at the same point of packet processing striving to avoid
>     introduction of jitter in propogation delay to ensure precise
>     accuracy in time determination.
perhaps change "avoid introduction of jitter" to "avoid introducing the 
appearance of jitter that's not really there"?

(I'm about to board a plane, so further responses will be very delayed).
> Regards,
> Greg
>
> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>
>
>     On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>     Hi Robert,
>>     Section 5 Data Plane Theory of Operation has the following
>>     recommendation on reading time value at ingress and egress:
>>         Each RTM-capable
>>         node on the explicit path receives an RTM packet and records the time
>>         at which it receives that packet at its ingress interface as well as
>>         the time at which it transmits that packet from its egress interface;
>>         this should be done as close to the physical layer as possible to
>>         ensure precise accuracy in time determination.
>>     Do you find the text sufficient in providing guidance to an implementer of RTM?
>     Well, no - that was point in the text from my review of -12 that
>     caused me to make comment in the first place.
>
>     What does "precise accuracy" even _MEAN_? You're waving your hands
>     with words that don't help the reader guess what you mean at the
>     moment. The subsequent email exchange said the important part was
>     that you measure _precisely_ (in that the measurements are always
>     taken the same way), but accuracy isn't that important (you've
>     (and here by "you" I mean the set of people that have responded to
>     the review") told me it's not important whether the reading is
>     taken at the beginning of the bit-stream, the end, or several 1000
>     nanoseconds after the last bit came off the physical media as long
>     as it's done the same way for each packet). The fact that you're
>     carrying a measurement that can talk about times smaller than the
>     interarrival time for individual bits for some real world line
>     speeds says that different implementations taking the measurement
>     different ways is going to result in different residence time
>     measurements, even if the residence time was really identical.
>     You've told me that's not important to the protocol using the
>     measurement as long as the an individual implementation doesn't
>     introduce something that will look to the using protocol like
>     jitter that's not really there.
>
>     The text does not say that to an implementer right now.
>
>     To restate that long paragraph with maybe a longer one, assume a
>     simplified world where everything is perfectly constant. Packets
>     are all flowing at the same size and same rate. For reference, I
>     assert that the time between the first bit of a packet entering
>     the system taking the measurement and the first bit of that packet
>     leaving the system is exactly T (every time). You are telling me
>     that if the system returns cT for some constant T other than 1
>     (and not necessarily  close to 1), everything is fine. You're also
>     telling me that if you replace the system with another that
>     preserves T, but measures differently so that it returns c'T where
>     c' != c, everything is fine. The important part to you is that c
>     and c' don't change for their respective systems. (That surprises
>     me, I can see how the way the clocks are going to use this will do
>     the right thing, but I can't help but think someone later will
>     look at the difference between the two systems and say something
>     is wrong with one of them). What you've told me is not fine is
>     that if you drop i a third system that also preserves T but
>     reports aT where a _varies_ over some range.
>
>     Have I heard you correctly?
>>     Regards,
>>     Greg
>>
>>     On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks
>>     <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>
>>         Reviewer: Robert Sparks
>>         Review result: Ready
>>
>>         I am the assigned Gen-ART reviewer for this draft. The
>>         General Area
>>         Review Team (Gen-ART) reviews all IETF documents being processed
>>         by the IESG for the IETF Chair. Please wait for direction
>>         from your
>>         document shepherd or AD before posting a new version of the
>>         draft.
>>
>>         For more information, please see the FAQ at
>>
>>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>>
>>         Document: draft-ietf-mpls-residence-time-13
>>         Reviewer: Robert Sparks
>>         Review Date: 2017-02-13
>>         IETF LC End Date: 2017-01-17
>>         IESG Telechat date: 2017-03-02
>>
>>         Summary: Ready for publication as PS
>>
>>         Thanks for addressing my comments.
>>         (I still think some discussion about taking arrival and
>>         departure time
>>         measurements would be helpful, even if it only said "do it
>>         consistently so you don't indicate jitter that's not really
>>         there".)
>>
>>
>
>


--------------8EF8ACD6F400BCC5968C8777
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/15/17 11:20 AM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>yes, you've absolutely correct in your example. The
          importance of RTM is to exclude and quantify, as much as
          possible, jitter from propagation delay. I've updated the
          wording to reflect that. Below is new text I propose, please
          let me know if it makes it clearer.</div>
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
        </div>
      </div>
    </blockquote>
    perhaps change "avoid introduction of jitter" to "avoid introducing
    the appearance of jitter that's not really there"?<br>
    <br>
    (I'm about to board a plane, so further responses will be very
    delayed). <br>
    <blockquote
cite="mid:CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Feb 15, 2017 at 7:43 AM, Robert
          Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"><span class="">
                <p><br>
                </p>
                <br>
                <div class="m_3072934530585377958moz-cite-prefix">On
                  2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">Hi Robert,
                    <div>Section 5 Data Plane Theory of Operation has
                      the following recommendation on reading time value
                      at ingress and egress:</div>
                    <div>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
                    </div>
                  </div>
                </blockquote>
              </span> Well, no - that was point in the text from my
              review of -12 that caused me to make comment in the first
              place.<br>
              <br>
              What does "precise accuracy" even _MEAN_? You're waving
              your hands with words that don't help the reader guess
              what you mean at the moment. The subsequent email exchange
              said the important part was that you measure _precisely_
              (in that the measurements are always taken the same way),
              but accuracy isn't that important (you've (and here by
              "you" I mean the set of people that have responded to the
              review") told me it's not important whether the reading is
              taken at the beginning of the bit-stream, the end, or
              several 1000 nanoseconds after the last bit came off the
              physical media as long as it's done the same way for each
              packet). The fact that you're carrying a measurement that
              can talk about times smaller than the interarrival time
              for individual bits for some real world line speeds says
              that different implementations taking the measurement
              different ways is going to result in different residence
              time measurements, even if the residence time was really
              identical. You've told me that's not important to the
              protocol using the measurement as long as the an
              individual implementation doesn't introduce something that
              will look to the using protocol like jitter that's not
              really there.<br>
              <br>
              The text does not say that to an implementer right now.<br>
              <br>
              To restate that long paragraph with maybe a longer one, 
              assume a simplified world where everything is perfectly
              constant. Packets are all flowing at the same size and
              same rate. For reference, I assert that the time between
              the first bit of a packet entering the system taking the
              measurement and the first bit of that packet leaving the
              system is exactly T (every time). You are telling me that
              if the system returns cT for some constant T other than 1
              (and not necessarily  close to 1), everything is fine.
              You're also telling me that if you replace the system with
              another that preserves T, but measures differently so that
              it returns c'T where c' != c, everything is fine. The
              important part to you is that c and c' don't change for
              their respective systems. (That surprises me, I can see
              how the way the clocks are going to use this will do the
              right thing, but I can't help but think someone later will
              look at the difference between the two systems and say
              something is wrong with one of them). What you've told me
              is not fine is that if you drop i a third system that also
              preserves T but reports aT where a _varies_ over some
              range.<br>
              <br>
              Have I heard you correctly?<span class=""><br>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                    </div>
                  </div>
                  <div class="gmail_extra"><br>
                    <div class="gmail_quote">On Mon, Feb 13, 2017 at
                      1:51 PM, Robert Sparks <span dir="ltr">&lt;<a
                          moz-do-not-send="true"
                          href="mailto:rjsparks@nostrum.com"
                          target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">Reviewer: Robert Sparks<br>
                        Review result: Ready<br>
                        <br>
                        I am the assigned Gen-ART reviewer for this
                        draft. The General Area<br>
                        Review Team (Gen-ART) reviews all IETF documents
                        being processed<br>
                        by the IESG for the IETF Chair. Please wait for
                        direction from your<br>
                        document shepherd or AD before posting a new
                        version of the draft.<br>
                        <br>
                        For more information, please see the FAQ at<br>
                        <br>
                        &lt;<a moz-do-not-send="true"
                          href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
                          rel="noreferrer" target="_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                        <br>
                        Document: draft-ietf-mpls-residence-time<wbr>-13<br>
                        Reviewer: Robert Sparks<br>
                        Review Date: 2017-02-13<br>
                        IETF LC End Date: 2017-01-17<br>
                        IESG Telechat date: 2017-03-02<br>
                        <br>
                        Summary: Ready for publication as PS<br>
                        <br>
                        Thanks for addressing my comments.<br>
                        (I still think some discussion about taking
                        arrival and departure time<br>
                        measurements would be helpful, even if it only
                        said "do it<br>
                        consistently so you don't indicate jitter that's
                        not really there".)<br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </blockquote>
                <br>
              </span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------8EF8ACD6F400BCC5968C8777--


From nobody Wed Feb 15 12:40:42 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640EC1297EB; Wed, 15 Feb 2017 12:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVHchg1zRCfF; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADF8012943B; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id u143so92644911oif.3; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HknoOHI9NMdmFphiMYNbbn6Y4TjOkHz+lwQ2ajNqUjo=; b=kntMMhXl08J6pHJpI7dtzaRyJaX4gnjQRGgn6PDdv7jfEgt3KneScMxVTK07ZQogIq cpCDkURhgbAn7PGX5XZj+4fkEuVeExKkDLN+eWZuIOjfd6ZxSrccYQGApgrte/Ajv7N9 YsrtDKe1GZMN6YHTQCu8QlWwp3H+nH0mvEv1yDkYyUkBgD3a1pvbBQelRc3QmEAAhemH 7rQ4SIzzTN/jcTohTyNby0mWGTAEJ1bqt49g/T/3tlQAISGJybb8OR3V744qXlhuKadS EuVA4VMhg2LwgbNTmZFwg33MiY/ZzsQCeS5GhCMpVpR72p0hhukSui3O8qk87TCg1Sp3 x6BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HknoOHI9NMdmFphiMYNbbn6Y4TjOkHz+lwQ2ajNqUjo=; b=pXu46Ogb3JA7T969Af15gufFLh2Nc3s7a1N1RcG27u5hjwsHn3U4xwwUzllSv53EUv EHG7zkpvEgXvCLrNJQ5sh2nIA8w2/hgPDofoGvnD+bQDkUFsGAlM6c+07Il+qwyUacBU YbNlXkYPaPiTtp2KQthJ41bJsMzTVotLz0OnSI7xU6enGmpQCMaah/eQkNcvi/IslaWv yy7PuR9fNT1z+HcJvSqfjVlkZ5QfDCufo+XJDNPrI7su/XW6xpegAwYcEFWxOGXzripH /uQCmayg4hUqt+wRyiUSTlEqgVF3IrnzdVjd79je88Dqolmzx1OnlWFuk66O2ffYtM3k /tXw==
X-Gm-Message-State: AMke39mqCaMjnHkJtpcGYVkygl+Nn+1Iqkck5Qc2HStP6WJvHwxLE+8cuO4wCvdKK0KDREAxL+6t+NWRJdV0Sg==
X-Received: by 10.202.232.77 with SMTP id f74mr18251472oih.60.1487191229023; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Wed, 15 Feb 2017 12:40:28 -0800 (PST)
In-Reply-To: <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 15 Feb 2017 12:40:28 -0800
Message-ID: <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a1141b0a0eb4d66054897b029
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/oy7OFoalzfi37cET17Vy6MtAyqA>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:40:32 -0000

--001a1141b0a0eb4d66054897b029
Content-Type: text/plain; charset=UTF-8

Hi Robert,
safe travel and here's another version for your consideration. The point
I'm trying to convey is that the jitter is real but must be accounted not
as part of propagation delay but as residence time. Hope I'm getting close.

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time.

Regards,

Greg


On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com>
wrote:

>
>
> On 2/15/17 11:20 AM, Greg Mirsky wrote:
>
> Hi Robert,
> yes, you've absolutely correct in your example. The importance of RTM is
> to exclude and quantify, as much as possible, jitter from propagation
> delay. I've updated the wording to reflect that. Below is new text I
> propose, please let me know if it makes it clearer.
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface.
>    These actions should be done as close to the physical layer as
>    possible at the same point of packet processing striving to avoid
>    introduction of jitter in propogation delay to ensure precise
>    accuracy in time determination.
>
> perhaps change "avoid introduction of jitter" to "avoid introducing the
> appearance of jitter that's not really there"?
>
> (I'm about to board a plane, so further responses will be very delayed).
>
> Regards,
>
> Greg
>
>
> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>
>> Hi Robert,
>> Section 5 Data Plane Theory of Operation has the following recommendation
>> on reading time value at ingress and egress:
>>
>>    Each RTM-capable
>>    node on the explicit path receives an RTM packet and records the time
>>    at which it receives that packet at its ingress interface as well as
>>    the time at which it transmits that packet from its egress interface;
>>    this should be done as close to the physical layer as possible to
>>    ensure precise accuracy in time determination.
>>
>> Do you find the text sufficient in providing guidance to an implementer of RTM?
>>
>> Well, no - that was point in the text from my review of -12 that caused
>> me to make comment in the first place.
>>
>> What does "precise accuracy" even _MEAN_? You're waving your hands with
>> words that don't help the reader guess what you mean at the moment. The
>> subsequent email exchange said the important part was that you measure
>> _precisely_ (in that the measurements are always taken the same way), but
>> accuracy isn't that important (you've (and here by "you" I mean the set of
>> people that have responded to the review") told me it's not important
>> whether the reading is taken at the beginning of the bit-stream, the end,
>> or several 1000 nanoseconds after the last bit came off the physical media
>> as long as it's done the same way for each packet). The fact that you're
>> carrying a measurement that can talk about times smaller than the
>> interarrival time for individual bits for some real world line speeds says
>> that different implementations taking the measurement different ways is
>> going to result in different residence time measurements, even if the
>> residence time was really identical. You've told me that's not important to
>> the protocol using the measurement as long as the an individual
>> implementation doesn't introduce something that will look to the using
>> protocol like jitter that's not really there.
>>
>> The text does not say that to an implementer right now.
>>
>> To restate that long paragraph with maybe a longer one,  assume a
>> simplified world where everything is perfectly constant. Packets are all
>> flowing at the same size and same rate. For reference, I assert that the
>> time between the first bit of a packet entering the system taking the
>> measurement and the first bit of that packet leaving the system is exactly
>> T (every time). You are telling me that if the system returns cT for some
>> constant T other than 1 (and not necessarily  close to 1), everything is
>> fine. You're also telling me that if you replace the system with another
>> that preserves T, but measures differently so that it returns c'T where c'
>> != c, everything is fine. The important part to you is that c and c' don't
>> change for their respective systems. (That surprises me, I can see how the
>> way the clocks are going to use this will do the right thing, but I can't
>> help but think someone later will look at the difference between the two
>> systems and say something is wrong with one of them). What you've told me
>> is not fine is that if you drop i a third system that also preserves T but
>> reports aT where a _varies_ over some range.
>>
>> Have I heard you correctly?
>>
>> Regards,
>>
>> Greg
>>
>>
>> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>
>>> Reviewer: Robert Sparks
>>> Review result: Ready
>>>
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair. Please wait for direction from your
>>> document shepherd or AD before posting a new version of the draft.
>>>
>>> For more information, please see the FAQ at
>>>
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>
>>> Document: draft-ietf-mpls-residence-time-13
>>> Reviewer: Robert Sparks
>>> Review Date: 2017-02-13
>>> IETF LC End Date: 2017-01-17
>>> IESG Telechat date: 2017-03-02
>>>
>>> Summary: Ready for publication as PS
>>>
>>> Thanks for addressing my comments.
>>> (I still think some discussion about taking arrival and departure time
>>> measurements would be helpful, even if it only said "do it
>>> consistently so you don't indicate jitter that's not really there".)
>>>
>>>
>>
>>
>
>

--001a1141b0a0eb4d66054897b029
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>safe travel and here&#39;s another version =
for your consideration. The point I&#39;m trying to convey is that the jitt=
er is real but must be accounted not as part of propagation delay but as re=
sidence time. Hope I&#39;m getting close.</div><div><pre style=3D"color:rgb=
(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-wor=
d;white-space:pre-wrap">Regards,</pre><pre style=3D"color:rgb(0,0,0);word-w=
rap:break-word;white-space:pre-wrap">Greg</pre></div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,=
 Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com=
" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <p><br>
    </p>
    <br>
    <div class=3D"m_2800513769154960288moz-cite-prefix">On 2/15/17 11:20 AM=
, Greg Mirsky wrote:<br>
    </div>
    </span><blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <span class=3D""><div>yes, you&#39;ve absolutely correct in your ex=
ample. The
          importance of RTM is to exclude and quantify, as much as
          possible, jitter from propagation delay. I&#39;ve updated the
          wording to reflect that. Below is new text I propose, please
          let me know if it makes it clearer.</div>
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
        </div>
      </span></div>
    </blockquote>
    perhaps change &quot;avoid introduction of jitter&quot; to &quot;avoid =
introducing
    the appearance of jitter that&#39;s not really there&quot;?<br>
    <br>
    (I&#39;m about to board a plane, so further responses will be very
    delayed). <br><div><div class=3D"h5">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Regards,</pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 7:43 AM, Robert
          Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.c=
om" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                <p><br>
                </p>
                <br>
                <div class=3D"m_2800513769154960288m_3072934530585377958moz=
-cite-prefix">On
                  2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                </div>
                <blockquote type=3D"cite">
                  <div dir=3D"ltr">Hi Robert,
                    <div>Section 5 Data Plane Theory of Operation has
                      the following recommendation on reading time value
                      at ingress and egress:</div>
                    <div>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidanc=
e to an implementer of RTM?</pre>
                    </div>
                  </div>
                </blockquote>
              </span> Well, no - that was point in the text from my
              review of -12 that caused me to make comment in the first
              place.<br>
              <br>
              What does &quot;precise accuracy&quot; even _MEAN_? You&#39;r=
e waving
              your hands with words that don&#39;t help the reader guess
              what you mean at the moment. The subsequent email exchange
              said the important part was that you measure _precisely_
              (in that the measurements are always taken the same way),
              but accuracy isn&#39;t that important (you&#39;ve (and here b=
y
              &quot;you&quot; I mean the set of people that have responded =
to the
              review&quot;) told me it&#39;s not important whether the read=
ing is
              taken at the beginning of the bit-stream, the end, or
              several 1000 nanoseconds after the last bit came off the
              physical media as long as it&#39;s done the same way for each
              packet). The fact that you&#39;re carrying a measurement that
              can talk about times smaller than the interarrival time
              for individual bits for some real world line speeds says
              that different implementations taking the measurement
              different ways is going to result in different residence
              time measurements, even if the residence time was really
              identical. You&#39;ve told me that&#39;s not important to the
              protocol using the measurement as long as the an
              individual implementation doesn&#39;t introduce something tha=
t
              will look to the using protocol like jitter that&#39;s not
              really there.<br>
              <br>
              The text does not say that to an implementer right now.<br>
              <br>
              To restate that long paragraph with maybe a longer one,=C2=A0
              assume a simplified world where everything is perfectly
              constant. Packets are all flowing at the same size and
              same rate. For reference, I assert that the time between
              the first bit of a packet entering the system taking the
              measurement and the first bit of that packet leaving the
              system is exactly T (every time). You are telling me that
              if the system returns cT for some constant T other than 1
              (and not necessarily=C2=A0 close to 1), everything is fine.
              You&#39;re also telling me that if you replace the system wit=
h
              another that preserves T, but measures differently so that
              it returns c&#39;T where c&#39; !=3D c, everything is fine. T=
he
              important part to you is that c and c&#39; don&#39;t change f=
or
              their respective systems. (That surprises me, I can see
              how the way the clocks are going to use this will do the
              right thing, but I can&#39;t help but think someone later wil=
l
              look at the difference between the two systems and say
              something is wrong with one of them). What you&#39;ve told me
              is not fine is that if you drop i a third system that also
              preserves T but reports aT where a _varies_ over some
              range.<br>
              <br>
              Have I heard you correctly?<span><br>
                <blockquote type=3D"cite">
                  <div dir=3D"ltr">
                    <div>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Regards,</pre>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Greg</pre>
                    </div>
                  </div>
                  <div class=3D"gmail_extra"><br>
                    <div class=3D"gmail_quote">On Mon, Feb 13, 2017 at
                      1:51 PM, Robert Sparks <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>=
&gt;</span>
                      wrote:<br>
                      <blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Robert Spark=
s<br>
                        Review result: Ready<br>
                        <br>
                        I am the assigned Gen-ART reviewer for this
                        draft. The General Area<br>
                        Review Team (Gen-ART) reviews all IETF documents
                        being processed<br>
                        by the IESG for the IETF Chair. Please wait for
                        direction from your<br>
                        document shepherd or AD before posting a new
                        version of the draft.<br>
                        <br>
                        For more information, please see the FAQ at<br>
                        <br>
                        &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                        <br>
                        Document: draft-ietf-mpls-residence-time<wbr>-13<br=
>
                        Reviewer: Robert Sparks<br>
                        Review Date: 2017-02-13<br>
                        IETF LC End Date: 2017-01-17<br>
                        IESG Telechat date: 2017-03-02<br>
                        <br>
                        Summary: Ready for publication as PS<br>
                        <br>
                        Thanks for addressing my comments.<br>
                        (I still think some discussion about taking
                        arrival and departure time<br>
                        measurements would be helpful, even if it only
                        said &quot;do it<br>
                        consistently so you don&#39;t indicate jitter that&=
#39;s
                        not really there&quot;.)<br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </blockquote>
                <br>
              </span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div>

--001a1141b0a0eb4d66054897b029--


From nobody Wed Feb 15 12:40:50 2017
Return-Path: <jhw@google.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A949129B6A for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2017 12:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEKT817PukWp for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A489E129B62 for <gen-art@ietf.org>; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
Received: by mail-pf0-x22d.google.com with SMTP id e4so33890372pfg.1 for <gen-art@ietf.org>; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zpsU83HZUABHROuNLA5qxCxvMEac8TxHWj8C1bSZAfI=; b=Tw3EzgMBN+S109+1tBcxsC+d2wUvv/Qe/aOS4oRIwHhZzGAWOPWKAn+Q8rwbQMansi X+6N6f1k6S+59p8M7sS+qXUuoSBApnL9ZhiPNRHB6OPYnJW7N+Qg00nJ87BrmIkj3YNh 7w/Gk7LqA41Hs1kcTk/tsnN+O2DWvbqa09+hb7oFyvoP+ZCl3qIGTKyX30JRkgLdvs7n 635xVu4FJ0HqAjOZBJMIwAcSF/UQjrfqjAkiWTce7L+BVkszt4vPMwqu4CBje8afsmqs 07lKnVm96FnkGO9CTK85mC8r61uca8RF7pxloGxrRxSa2gj15/tiWSuwREs59mGpHd95 yfNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zpsU83HZUABHROuNLA5qxCxvMEac8TxHWj8C1bSZAfI=; b=oojTAGhroKU6ONtdAtOxVgXuK773IQZ9Dalqwz0aQOO0vqQguusVNEMrLZd+IgdcdW Es/TqjV2vVX80oWlUBkBd8K32hpCKqyNYLlP6hQLuJC7/dWR4+SRSqm9Nc4mR5PdBrgs 7ew2AczbSJMger3SoTS0QeBBWQMSnlLUaZRuhaEeWDndH+7P5ZNYrbdHrIroG96G3LJL vtkZyEYoqJ4tPUQ6eVlTMgwVMYOAednqW5rmAEhAQpGi6685a1EGJ+3g1W57kaDx51uj uM3GW7NZGPKcx/sEmYgHWWhdyvlOGVe9MI0a+N68uaq82YtguA/relbfNDfwtXXdQvF9 vUyg==
X-Gm-Message-State: AMke39nxMZhvySemRALPj28FIzuXXFHmHtWKNcox81IjqpbDmP0qZjsecDxAI5iEoUizLtss
X-Received: by 10.99.39.70 with SMTP id n67mr40570667pgn.203.1487191234190; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id a25sm9209081pgd.26.2017.02.15.12.40.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 12:40:33 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <99AFD44C-06B7-435D-A14C-951680EA2355@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 15 Feb 2017 12:40:32 -0800
In-Reply-To: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/xT_cjeumN20qfFwXVZKXIWXGmDI>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:40:36 -0000

--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 14, 2017, at 15:00, Templin, Fred L <Fred.L.Templin@boeing.com> =
wrote:
>=20
> Unless there is operational assurance of some size X>1280, however, =
tunnels have to use fragmentation to guarantee that - at a minimum - =
packets up to 1280 will get through.

Given the growing prevalence of IPv6 using 6LoWPAN on IEEE 802.15.4, =
which is always MTU=3D1280 everywhere, c.f. RFC 4944, I think we can =
forget about ever getting that operational assurance in practice.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 14, 2017, at 15:00, Templin, Fred L &lt;<a =
href=3D"mailto:Fred.L.Templin@boeing.com" =
class=3D"">Fred.L.Templin@boeing.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Unless there is operational assurance =
of&nbsp;</span><span style=3D"font-family: Menlo-Regular; font-size: =
11px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">some size X&gt;1280, however, =
tunnels have to use fragmentation to&nbsp;</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">guarantee that - at a minimum - packets up to =
1280 will get through.</span></div></blockquote><br =
class=3D""></div><div>Given the growing prevalence of IPv6 using 6LoWPAN =
on IEEE 802.15.4, which is always MTU=3D1280 everywhere, c.f. RFC 4944, =
I think we can forget about ever getting that operational assurance in =
practice.</div><div><br class=3D""></div><br class=3D""><div class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0--


From nobody Wed Feb 15 13:09:19 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E53129B67; Wed, 15 Feb 2017 13:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q35r9USeQVjr; Wed, 15 Feb 2017 13:09:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70598129B64; Wed, 15 Feb 2017 13:09:10 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FL8m87008923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:08:49 -0800 (PST)
To: otroan@employees.org, Stewart Bryant <stewart.bryant@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <b7a65660-2cc5-8461-c1c4-21b94fd65166@isi.edu>
Date: Wed, 15 Feb 2017 13:08:47 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Content-Type: multipart/alternative; boundary="------------007E84B2003B9732A6018B39"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/NlFByWaF4WgjEFeuEERNZ1G9sOc>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:09:12 -0000

This is a multi-part message in MIME format.
--------------007E84B2003B9732A6018B39
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Hi, Ole,


On 2/14/2017 10:33 AM, otroan@employees.org wrote:
>> *If*  you care about packet loss, then your only option is to probe the path with with
>> synthetic data that exactly mimics the live data, or not to probe at all and live
>> with the 1280. As I said 1280 is pretty close to 1496 which is all most networks
>> will give you in practice.
> Yes, but sending at 1280 does not work for IP tunnels. The whole purpose of the minimum MTU was to give space for tunnel headers (1500-1280).
I'm in the process of revising draft-intarea-tunnels to make this more
clear, as well as to provide a TSV ART review of this doc, but in preface:

There are two IPv6 minimum sizes: link MTU of 1280 and EMTU_R of 1500.

Support for source fragmentation and the difference between these two
values is what gives space for tunnel headers.

No amount of link MTU management can ever avoid source fragmentation
without violating the link MTU minimums in RFC2460.

Joe

--------------007E84B2003B9732A6018B39
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, Ole,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/14/2017 10:33 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
    </div>
    <blockquote
      cite="mid:57307617-C87C-4430-B92A-59E28C6779CD@employees.org"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap=""><b class="moz-txt-star"><span class="moz-txt-tag">*</span>If<span class="moz-txt-tag">*</span></b>  you care about packet loss, then your only option is to probe the path with with
synthetic data that exactly mimics the live data, or not to probe at all and live
with the 1280. As I said 1280 is pretty close to 1496 which is all most networks
will give you in practice.
</pre>
      </blockquote>
      <pre wrap="">Yes, but sending at 1280 does not work for IP tunnels. The whole purpose of the minimum MTU was to give space for tunnel headers (1500-1280).
</pre>
    </blockquote>
    I'm in the process of revising draft-intarea-tunnels to make this
    more clear, as well as to provide a TSV ART review of this doc, but
    in preface:<br>
    <br>
    There are two IPv6 minimum sizes: link MTU of 1280 and EMTU_R of
    1500.<br>
    <br>
    Support for source fragmentation and the difference between these
    two values is what gives space for tunnel headers.<br>
    <br>
    No amount of link MTU management can ever avoid source fragmentation
    without violating the link MTU minimums in RFC2460.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------007E84B2003B9732A6018B39--


From nobody Wed Feb 15 13:12:47 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBCBA129B86; Wed, 15 Feb 2017 13:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OuXQK4ryeb_2; Wed, 15 Feb 2017 13:12:41 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AF311297E4; Wed, 15 Feb 2017 13:12:41 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLCF9V009704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:12:15 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
Date: Wed, 15 Feb 2017 13:12:14 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
Content-Type: multipart/alternative; boundary="------------31EA21CD2E92C7ACFA919F7B"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CG9hytrOKpRy6VXS2W0HGkpAE88>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:12:43 -0000

This is a multi-part message in MIME format.
--------------31EA21CD2E92C7ACFA919F7B
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Brian (et al.),


On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>> practice the
>> Internet breaks the mechanism. However it breaks it is a way that seems
>> disruptive to some user traffic. The document is really guidance
>> one how hosts might use  ICMP for optimization, and arguable need
>> not be a standard at all.
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes
PMTUD is an optimization to avoid fragmentation.

Without it, you use fragmentation (which has overheads and other
consequences, notably for IPv4).

However, it is only *with* PMTUD (and ICMP blocking) that you get black
holes.

Joe

--------------31EA21CD2E92C7ACFA919F7B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Brian (et al.),<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/10/2017 11:45 AM, Brian E
      Carpenter wrote:<br>
    </div>
    <blockquote
      cite="mid:9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">practice the
Internet breaks the mechanism. However it breaks it is a way that seems
disruptive to some user traffic. The document is really guidance
one how hosts might use  ICMP for optimization, and arguable need
not be a standard at all.
</pre>
      </blockquote>
      <pre wrap="">I think that's a mischaracterisation of the mechanism (and the draft).
PMTUD is not an optimisation. Without it, you get black holes</pre>
    </blockquote>
    PMTUD is an optimization to avoid fragmentation.<br>
    <br>
    Without it, you use fragmentation (which has overheads and other
    consequences, notably for IPv4).<br>
    <br>
    However, it is only *with* PMTUD (and ICMP blocking) that you get
    black holes. <br>
    <br>
    Joe<br>
  </body>
</html>

--------------31EA21CD2E92C7ACFA919F7B--


From nobody Wed Feb 15 13:26:53 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD891129556; Wed, 15 Feb 2017 13:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fXaPWLlugr5; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7394A129B96; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: by mail-pg0-x241.google.com with SMTP id 75so12085933pgf.3; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=oubWh6KObmZKhsFrc9dZol3y1lYgRBAryBnz3gPWMOM=; b=fho/bPrw9PNcJ05R3n1nqEAxNCTWmXX7O1qZfHb+swuq+BZ4g+tI1ET6yLa1Qc+Hpt mmICk1uXHWV/bB9PXOmUj+cVeF422LIHicLtRiveJlJygWGsM9aHus+QhNFF0Uq4RdoE UxDXtqEoz3Ye8O9hS72vnoUG7NS0b2FXQasJI94SmuwT/9EGUWcmYKDlcp6HkqyfaTS+ RRAadJvvLeapUEe8B477ZYBgTcXGmHhEG304dJvoF0PIJ3nfVXV6IXGTr4GQIwf2mgzY WlMreQvyxNPzQtvx2LjnVp9Tre4QW8EIPyf1MbZpTdm0UV3A4el79cIUcla8S21czqrk rEiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=oubWh6KObmZKhsFrc9dZol3y1lYgRBAryBnz3gPWMOM=; b=R6gt9/SEIRwfWRa7tWiZeGjNOA2vsskLs+HO3/EGV2Mus+fQe+hNDi4yBV5CclR9G3 idvxTZkykU2I0mxmEMOYJofeMkQsaDtlK6lBMxjT53ObV9Ek+ikZCgtIfQlY4wegcxHp PHtAmJZEEtD8X0Z0VqMuQKOGTkMvlgTUxXc6nSgyyI1e+/joZo1jastmuXJpwBM1xiNg tqhmW/fYZmvpYN9cj5HU57JN3mfPLxTwKlFQQoKBanWd78jVpj3FdM3z/8ErH8ErwVvS tkC6a4K0FqFrPdPTJZmIkeABaojlEN/YB2/72YOkjZ7vKaxVXmIi0P9PEMWilZTBlvKw rywQ==
X-Gm-Message-State: AMke39nnqJdItD3yHNKgTEArbmlEG+DGWDgwosr3GSSfACnFtKH+79463bkcfBgEoaxpwg==
X-Received: by 10.98.212.23 with SMTP id a23mr40461055pfh.18.1487194010033; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: from [192.168.178.21] ([118.148.112.221]) by smtp.gmail.com with ESMTPSA id n70sm9250021pfg.34.2017.02.15.13.26.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 13:26:49 -0800 (PST)
To: Joe Touch <touch@isi.edu>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com> <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
Date: Thu, 16 Feb 2017 10:26:50 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/tSsgTT2xhJOuyUml0Lg7JwEpKdY>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:26:52 -0000

On 16/02/2017 10:12, Joe Touch wrote:
> Brian (et al.),
> 
> 
> On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>>> practice the
>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>> disruptive to some user traffic. The document is really guidance
>>> one how hosts might use  ICMP for optimization, and arguable need
>>> not be a standard at all.
>> I think that's a mischaracterisation of the mechanism (and the draft).
>> PMTUD is not an optimisation. Without it, you get black holes
> PMTUD is an optimization to avoid fragmentation.
> 
> Without it, you use fragmentation (which has overheads and other
> consequences, notably for IPv4).

In IPv6, you don't even know you *need* fragmentation without PMTUD,
since only the source is allowed to fragment. (That was one of the
many failure modes for 6to4, which is why the only safe approach was
to use 1280 always.) 

> However, it is only *with* PMTUD (and ICMP blocking) that you get black
> holes.

True for v4.

   Brian


From nobody Wed Feb 15 13:32:48 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E515D129862; Wed, 15 Feb 2017 13:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngSgcK46G-_l; Wed, 15 Feb 2017 13:32:45 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49B28129860; Wed, 15 Feb 2017 13:32:45 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLWMH2013445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:32:22 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com> <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu> <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <9be213f6-59a4-459e-0312-7c3720c567b3@isi.edu>
Date: Wed, 15 Feb 2017 13:32:20 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XIv-djVNUA6NRBC7C9FkJEPyrpQ>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:32:47 -0000

Hi, Brian,


On 2/15/2017 1:26 PM, Brian E Carpenter wrote:
> On 16/02/2017 10:12, Joe Touch wrote:
>> Brian (et al.),
>>
>>
>> On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>>>> practice the
>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>> disruptive to some user traffic. The document is really guidance
>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>> not be a standard at all.
>>> I think that's a mischaracterisation of the mechanism (and the draft).
>>> PMTUD is not an optimisation. Without it, you get black holes
>> PMTUD is an optimization to avoid fragmentation.
>>
>> Without it, you use fragmentation (which has overheads and other
>> consequences, notably for IPv4).
> In IPv6, you don't even know you *need* fragmentation without PMTUD,
> since only the source is allowed to fragment. (That was one of the
> many failure modes for 6to4, which is why the only safe approach was
> to use 1280 always.) 
A compliant IPv6 source can send 1500 byte packets that a source without
PMTUD, which would need to be fragmented based on the assumption that
the path MTU is at its required minimum of 1280.

A compliant IPv6 source can send larger packets, which would work if the
receiver supported larger reassembly limits than 1500. There is no
currently standard mechanism to determine the receiver reassembly limit
in IPv6, but this IS supported in TCP.

Joe


From nobody Wed Feb 15 16:12:28 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AB1129C05; Wed, 15 Feb 2017 16:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.22
X-Spam-Level: 
X-Spam-Status: No, score=-2.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_-DOq02oh9L; Wed, 15 Feb 2017 16:12:18 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D608129C04; Wed, 15 Feb 2017 16:12:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1487203937; bh=6xZt+yDlj3PAWRldWyCmsApEBdF76ryJU6LB bVM8DgI=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=hGb9JT+ gO6JsaPeYAo4M4Bu6R+8pwHfrvv5ZI4kdyTtC39VdXjWkWXwBrKholQfMNU6/sB0d5C xryWG8YwCCq9xLJu5GYQq0G0hbztxKosUUFYNESlZjXAzSyq9z+Cj7bDe2IW8YZiF56 K0De4fWpVKtcOoEE3l+qMzayfNMAXHQdGQSY42G0+5MpGH6/5ueav/WDqcmAywLlW2D fZ1sU+yJXMxI3N5PpOKVoNHUvpeVWviH/+MpFwvdvI5BvJNVtk2hHwoCKGaz+RIK+U/ SZJzLxF+gGGmR0MtrbklXCUQvv0UsXGp5qoAHzzk+t+HN0q7gTBSHVkCB8ROi9z25FA ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=NJ9LXRtzCBUu2iOnnG64fGcrPtXAAMzstu/6C+np+x1YvRRFM65Uo8K/BXdcuUQgQWOc6fGPLUqZLxha/BB4xeVdTIFjsZg1IXAQDKFTg1HLDax9Co4P+mYaqBNIzXt+LdjYTcoy92sJYj0PyqB8Gt4eZ0tClUmrOGeL8CCLpoGv+j1J1S3iERUqmFmSy+DpMzOTvY9TQIZBh5UjIhpLin5FeUhezJCUHO3MUizyfNVaGn+SH5/kqxCuObCvXe8xgbl8pEete8lmc1lRTNVNvtEqVjbK/lk4mLHhnTj0PTrF04jO/SXPqN+FDMBd2XPJeCb4uDQgB1Y89viFF0Ty2A==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ce9gB-0002ZY-MQ; Wed, 15 Feb 2017 19:12:11 -0500
To: "Dale R. Worley" <worley@ariadne.com>
References: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <f6e2cba3-6de8-af60-2a55-9c908863bb70@earthlink.net>
Date: Wed, 15 Feb 2017 16:12:04 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac78030d2dc13a190b468de9a8be97af0f3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jRWDkL8SJPJdzgoInBqfrxkXkQA>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] [DMM] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 00:12:20 -0000

Hello Dale,

O.K.  I will take a crack at making this reorganization.  If you have 
text of course that will be appreciated.  Right now I don't see why 
anyone in the WG would object, but I hope at least some people will take 
a look.

I can have the revised draft ready in a few days.  I think this resolves 
the last point of discussion that has been raised about the draft.

Regards,
Charlie P.


On 2/14/2017 5:04 PM, Dale R. Worley wrote:
> Charlie Perkins <charles.perkins@earthlink.net> writes:
>> I am hesitant to replace so many MNID types by a single URN type with
>> substructure.  What would you think about replacing the existing
>> RFID-*-URI types with a single URN type, but leaving the existing binary
>> types?  This gets the benefit you suggest for future extensibility, but
>> retains the shorter forms that may often be advantageous.
> Suddenly today I realized something I should have realized in the
> review, which would have saved us much time in discussion.  Viz.,
> consider this proposal:
>
> - one MNID type for *all* the EPC binary schemes
>
> - one MNID type for *all* URNs, *including* the EPC URI forms
>
> This would work, since (1) (not surprisingly) the EPC binary schemes are
> all differentiated by their first 8 bits.  (see table on page 19 of the
> tag-data standard,
> http://www.gs1.org/gsmp/kc/epcglobal/tds/tds_1_1_rev_1_27-standard-20050510.pdf)
> and (2) all URNs are differentiated by their namespace part.
>
> (This parallels using one MNID number for all DUID types, since DUIDs
> have an internal indicator for the four types.)
>
> This approach has all the desirable properties anyone has mentioned so
> far:
>
> - includes all EPC binary and URI forms
> - automatically includes all existing and future EPC binary forms
> - automatically includes all existing and future URN forms *including*
>    all existing and future EPC URI forms
> - doesn't have a proliferation of MNID type numbers which duplicate
>    information that can be fairly easily extracted from the
>    identifier itself
> - includes all the short EPC forms, allowing brevity when that is
>    desirable
>
> This seems to be practical, simple, and almost as elegant as possible.
> What do you think?
>
>> I changed the text as follows:
>>
>>>      Some MNIDs contain sensitive identifiers which, as used in protocols
>>>      specified by other SDOs, are only used for signaling during initial
>>>      network entry.  In such protocols, subsequent exchanges then rely on
>>>      a temporary identifier allocated during the initial network entry.
>>>      Managing the association between long-lived and temporary identifiers
>>>      is outside the scope of this document.
>> I can't remember exactly why this text was added - it was a long time
>> ago.  But anyway the main point is to simply mention that there may be
>> associations between some of the MNID types that might be important from
>> a security standpoint, without meaning to go into examples.
> Certainly the new text is clear enough.
>
> Dale
>


From nobody Wed Feb 15 21:23:02 2017
Return-Path: <yan@cnnic.cn>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0E71299C4; Wed, 15 Feb 2017 21:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdtxdVhbHjyy; Wed, 15 Feb 2017 21:23:00 -0800 (PST)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id E80831299B2; Wed, 15 Feb 2017 21:22:57 -0800 (PST)
Received: from yanzhiwei (unknown [218.241.111.47]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcJQmN6VYwGCAKg--.15782S2;  Thu, 16 Feb 2017 13:22:46 +0800 (CST)
Date: Thu, 16 Feb 2017 13:22:44 +0800
From: "Z.W. Yan" <yan@cnnic.cn>
To: "Meral Shirazipour" <meral.shirazipour@ericsson.com>, "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DA@eusaamb107.ericsson.se>
Message-ID: <201702161322440072149@cnnic.cn>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon314277770557_====="
X-CM-TRANSID: AQAAf0BpcJQmN6VYwGCAKg--.15782S2
X-Coremail-Antispam: 1UD129KBjvJXoWxXF1fCr4DKw1UCF1kKr1xKrg_yoW5WF4Upa 97Kws3J3s7XryUCws7uw48Z345uas3C3yUXFyUXw18Zrs8Ga4ktr42kr4FqrZrW348AF4D XF4I9FZ8Xw1FvaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUmlb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r4j6ryUM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Gr0_Xr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVWxJr0_GcWl84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202 j2C_Xr0_Wr1l5I8CrVAqjxCE14ACF2xKxwAqx4xG64kEw2xG04xIwI0_Jr0_Gr1l5I8CrV CF0I0E4I0vr24lYx0E2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE14v26r1j6r4UMcvj eVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACY4xI67k04243AVAKzVAKj4xxM4 xvF2IEb7IF0Fy26I8I3I1lc2xSY4AK67AK6r4rMxAIw28IcxkI7VAKI48JMxC20s026xCa FVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_Jr Wlx4CE17CEb7AF67AKxVWUAVWUtwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j 6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Wr 1j6rW3Jr1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8 JbIYCTnIWIevJa73UjIFyTuYvjxUqF1vDUUUU
X-CM-SenderInfo: x1dqqupqqluhdfq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/21wz4xDN3q32V5y183VdQjAHDzU>
Cc: xl <xl@cnnic.cn>, dmm-chairs <dmm-chairs@ietf.org>, Jong-Hyouk Lee <jonghyouk@smu.ac.kr>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 05:23:02 -0000

This is a multi-part message in MIME format.

--=====003_Dragon314277770557_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

RGVhciBNZXJhbCwNCkJhc2VkIG9uIHlvdSBjb21tZW50cywgYSBuZXcgdmVyc2lvbiBvZiB0aGlz
IGRyYWZ0IHdhcyBnZW5lcmF0ZWQgYW5kIHN1Ym1pdHRlZC4NClRoYW5rIHlvdSBzbyBtdWNoIGZv
ciBwdXNoaW5nIHRoaXMgd29yay4NCkJSLA0KWmhpd2VpDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDYudHh0
DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFpoaXdlaSBZYW4gYW5kIHBvc3Rl
ZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCk5hbWU6IGRyYWZ0LWlldGYtZG1tLWhucHJlbnVt
DQpSZXZpc2lvbjogMDYNClRpdGxlOiBIb21lIE5ldHdvcmsgUHJlZml4IFJlbnVtYmVyaW5nIGlu
IFBNSVB2Ng0KRG9jdW1lbnQgZGF0ZTogMjAxNy0wMi0xNQ0KR3JvdXA6IGRtbQ0KUGFnZXM6IDkN
ClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtaWV0Zi1kbW0taG5wcmVudW0tMDYudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0vDQpIdG1saXplZDog
ICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZG1tLWhucHJlbnVt
LTA2DQpEaWZmOiAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRy
YWZ0LWlldGYtZG1tLWhucHJlbnVtLTA2DQpBYnN0cmFjdDoNCiAgIEluIHRoZSBiYXNpYyBQcm94
eSBNb2JpbGUgSVB2NiAoUE1JUHY2KSBzcGVjaWZpY2F0aW9uLCBhIE1vYmlsZSBOb2RlDQogICAo
TU4pIGlzIGFzc2lnbmVkIHdpdGggYSBIb21lIE5ldHdvcmsgUHJlZml4IChITlApIGR1cmluZyBp
dHMgaW5pdGlhbA0KICAgYXR0YWNobWVudCBhbmQgdGhlIE1OIGNvbmZpZ3VyZXMgaXRzIEhvbWUg
QWRkcmVzcyAoSG9BKSB3aXRoIHRoZSBITlAuDQogICBEdXJpbmcgdGhlIG1vdmVtZW50IG9mIHRo
ZSBNTiwgdGhlIEhOUCByZW1haW5zIHVuY2hhbmdlZCB0byBrZWVwDQogICBvbmdvaW5nIGNvbW11
bmljYXRpb25zIGFzc29jaWF0ZWQgd2l0aCB0aGUgSG9BLiAgSG93ZXZlciwgdGhlIGN1cnJlbnQN
CiAgIFBNSVB2NiBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgcmVsYXRlZCBvcGVyYXRp
b25zIHdoZW4gYW4gSE5QDQogICByZW51bWJlcmluZyBoYXMgaGFwcGVuZWQgKGUuZy4gZHVlIHRv
IGNoYW5nZSBvZiBzZXJ2aWNlIHByb3ZpZGVyLA0KICAgY2hhbmdlIG9mIHNpdGUgdG9wb2xvZ3ks
IGV0Yy4pLiAgSW4gdGhpcyBkb2N1bWVudCwgYSBzb2x1dGlvbiB0bw0KICAgc3VwcG9ydCB0aGUg
SE5QIHJlbnVtYmVyaW5nIGlzIHByb3Bvc2VkLCBhcyBhbiB1cGRhdGUgb2YgdGhlIFBNSVB2Ng0K
ICAgc3BlY2lmaWNhdGlvbi4NCg0KDQoNCg0Kt6K8/sjLo7ogTWVyYWwgU2hpcmF6aXBvdXIgDQq3
osvNyrG85KO6IDIwMTctMDItMTEgIDA2OjA0OjQxIA0KytW8/sjLo7ogZHJhZnQtaWV0Zi1kbW0t
aG5wcmVudW0uYWxsQHRvb2xzLmlldGYub3JnOyBnZW4tYXJ0QGlldGYub3JnIA0Ks63LzaO6IA0K
1vfM4qO6IEdlbi1BUlQgTGFzdCBDYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWRtbS1obnByZW51
bS0wNSANCiANCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJh
ZnQuIFRoZSBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElF
VEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hh
aXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0
IGNhbGwgY29tbWVudHMuDQpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFR
IGF0IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0
ZmFxPi4gDQogDQogDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDUNClJldmll
d2VyOiBNZXJhbCBTaGlyYXppcG91cg0KUmV2aWV3IERhdGU6IDIwMTctMDItMTANCklFVEYgTEMg
RW5kIERhdGU6ICAgMjAxNy0wMi0xMA0KSUVTRyBUZWxlY2hhdCBkYXRlOiAtDQogDQogDQpTdW1t
YXJ5Og0KVGhpcyBkcmFmdCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgU3RhbmRhcmRzIFRy
YWNrIFJGQyBidXQgSSBoYXZlIGNvbW1lbnRzLg0KIA0KTWFqb3IgaXNzdWVzOg0KTWlub3IgaXNz
dWVzOg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQotQWJzdHJhY3Q6DQpDdXJyZW50OiANCiJI
b3dldmVyLCB0aGUgY3VycmVudCBQTUlQdjYgc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCBzcGVjaWZ5
IHJlbGF0ZWQgb3BlcmF0aW9ucyB3aGVuIGFuIEhOUCByZW51bWJlcmluZyBpcyBoYXBwZW5lZC4i
Lg0KU3VnZ2VzdGlvbiBmb3IgbW9yZSBjbGFyaXR5Og0KIkhvd2V2ZXIsIHRoZSBjdXJyZW50IFBN
SVB2NiBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgcmVsYXRlZCBvcGVyYXRpb25zIHdo
ZW4gYW4gSE5QIHJlbnVtYmVyaW5nIGhhcyBoYXBwZW5lZCAoZS5nLiBkdWUgdG8gY2hhbmdlIG9m
IHNlcnZpY2UgcHJvdmlkZXIsIGNoYW5nZSBvZiBzaXRlIHRvcG9sb2d5LCBldGMuKS4iLg0KLVtQ
YWdlIDNdLCAidG8gYW4gTUFHIi0tLS0+InRvIGEgTUFHIg0KIA0KLVtQYWdlIDddLCAidGhlIHBy
b2NlZHVlciItLS0+InRoZSBwcm9jZWR1cmUiDQogDQpCZXN0IFJlZ2FyZHMsDQpNZXJhbA0KLS0t
DQpNZXJhbCBTaGlyYXppcG91cg0KRXJpY3Nzb24gUmVzZWFyY2gNCnd3dy5lcmljc3Nvbi5jb20N
Cg==

--=====003_Dragon314277770557_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4bWxu
czp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46c2No
ZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptID0gDQoiaHR0cDovL3NjaGVt
YXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIj48SEVBRD4NCjxNRVRBIGNvbnRl
bnQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIiIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlPg0K
PE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNIVE1MIDguMDAuNzYwMS4xNzUxNCI+DQo8
U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IENhbWJyaWEgTWF0aDsNCn0NCkBmb250
LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiBDYWxpYnJpOw0KfQ0KQHBhZ2UgV29yZFNlY3Rpb24xIHtz
aXplOiA4LjVpbiAxMS4waW47IG1hcmdpbjogMS4waW4gMS4waW4gMS4waW4gMS4waW47IH0NClAu
TXNvTm9ybWFsIHsNCglNQVJHSU46IDBpbiAwaW4gMHB0OyBGT05ULUZBTUlMWTogIkNhbGlicmki
LHNhbnMtc2VyaWY7IEZPTlQtU0laRTogMTFwdA0KfQ0KTEkuTXNvTm9ybWFsIHsNCglNQVJHSU46
IDBpbiAwaW4gMHB0OyBGT05ULUZBTUlMWTogIkNhbGlicmkiLHNhbnMtc2VyaWY7IEZPTlQtU0la
RTogMTFwdA0KfQ0KRElWLk1zb05vcm1hbCB7DQoJTUFSR0lOOiAwaW4gMGluIDBwdDsgRk9OVC1G
QU1JTFk6ICJDYWxpYnJpIixzYW5zLXNlcmlmOyBGT05ULVNJWkU6IDExcHQNCn0NCkE6bGluayB7
DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUtcHJp
b3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVD
T1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUtcHJpb3JpdHk6IDk5DQp9DQpBOnZpc2l0ZWQg
ew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lOyBtc28tc3R5bGUt
cHJpb3JpdHk6IDk5DQp9DQpTUEFOLk1zb0h5cGVybGlua0ZvbGxvd2VkIHsNCglDT0xPUjogcHVy
cGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZTsgbXNvLXN0eWxlLXByaW9yaXR5OiA5OQ0K
fQ0KU1BBTi5FbWFpbFN0eWxlMTcgew0KCUZPTlQtRkFNSUxZOiAiQ2FsaWJyaSIsc2Fucy1zZXJp
ZjsgQ09MT1I6IHdpbmRvd3RleHQ7IG1zby1zdHlsZS10eXBlOiBwZXJzb25hbC1jb21wb3NlDQp9
DQouTXNvQ2hwRGVmYXVsdCB7DQoJRk9OVC1GQU1JTFk6ICJDYWxpYnJpIixzYW5zLXNlcmlmOyBt
c28tc3R5bGUtdHlwZTogZXhwb3J0LW9ubHkNCn0NCkRJVi5Xb3JkU2VjdGlvbjEgew0KCXBhZ2U6
IFdvcmRTZWN0aW9uMQ0KfQ0KPC9TVFlMRT4NCjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2Vu
ZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVk
aXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+
PC94bWw+PCFbZW5kaWZdLS0+DQo8TUVUQSBuYW1lPUdFTkVSQVRPUiBjb250ZW50PSJNU0hUTUwg
Ni4wMC4yOTAwLjIxODAiPg0KPFNUWUxFPkBmb250LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiDLzszl
Ow0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IFZlcmRhbmE7DQp9DQpAZm9udC1mYWNl
IHsNCglmb250LWZhbWlseTogQMvOzOU7DQp9DQpAcGFnZSBTZWN0aW9uMSB7c2l6ZTogNTk1LjNw
dCA4NDEuOXB0OyBtYXJnaW46IDcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDsgbGF5b3V0LWdy
aWQ6IDE1LjZwdDsgfQ0KUC5Nc29Ob3JtYWwgew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dy
YXBoOyBURVhULUFMSUdOOiBqdXN0aWZ5OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlM
WTogIlRpbWVzIE5ldyBSb21hbiI7IEZPTlQtU0laRTogMTAuNXB0DQp9DQpMSS5Nc29Ob3JtYWwg
ew0KCVRFWFQtSlVTVElGWTogaW50ZXItaWRlb2dyYXBoOyBURVhULUFMSUdOOiBqdXN0aWZ5OyBN
QVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVzIE5ldyBSb21hbiI7IEZPTlQt
U0laRTogMTAuNXB0DQp9DQpESVYuTXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6IGludGVyLWlk
ZW9ncmFwaDsgVEVYVC1BTElHTjoganVzdGlmeTsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1G
QU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4iOyBGT05ULVNJWkU6IDEwLjVwdA0KfQ0KQTpsaW5rIHsN
CglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NClNQQU4uTXNvSHlw
ZXJsaW5rIHsNCglDT0xPUjogYmx1ZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0NCkE6
dmlzaXRlZCB7DQoJQ09MT1I6IHB1cnBsZTsgVEVYVC1ERUNPUkFUSU9OOiB1bmRlcmxpbmUNCn0N
ClNQQU4uTXNvSHlwZXJsaW5rRm9sbG93ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JB
VElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLkVtYWlsU3R5bGUxNyB7DQoJRk9OVC1TVFlMRTogbm9y
bWFsOyBGT05ULUZBTUlMWTogVmVyZGFuYTsgQ09MT1I6IHdpbmRvd3RleHQ7IEZPTlQtV0VJR0hU
OiBub3JtYWw7IFRFWFQtREVDT1JBVElPTjogbm9uZTsgbXNvLXN0eWxlLXR5cGU6IHBlcnNvbmFs
LWNvbXBvc2UNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjENCn0NClVOS05PV04g
ew0KCUZPTlQtU0laRTogMTBwdA0KfQ0KQkxPQ0tRVU9URSB7DQoJTUFSR0lOLVRPUDogMHB4OyBN
QVJHSU4tQk9UVE9NOiAwcHg7IE1BUkdJTi1MRUZUOiAyZW0NCn0NCk9MIHsNCglNQVJHSU4tVE9Q
OiAwcHg7IE1BUkdJTi1CT1RUT006IDBweA0KfQ0KVUwgew0KCU1BUkdJTi1UT1A6IDBweDsgTUFS
R0lOLUJPVFRPTTogMHB4DQp9DQo8L1NUWUxFPg0KPC9IRUFEPg0KPEJPRFkgc3R5bGU9Ik1BUkdJ
TjogMTBweDsgRk9OVC1GQU1JTFk6IHZlcmRhbmE7IEZPTlQtU0laRTogMTBwdCI+DQo8RElWPjxG
T05UIGNvbG9yPSMwMDAwODAgc2l6ZT0yIGZhY2U9VmVyZGFuYT5EZWFyIE1lcmFsLDwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDA4MD5CYXNlZCBvbiB5b3UgY29tbWVudHMsIGEg
bmV3IHZlcnNpb24gb2YgdGhpcyBkcmFmdCB3YXMgDQpnZW5lcmF0ZWQgYW5kIHN1Ym1pdHRlZC48
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwODA+VGhhbmsgeW91IHNvIG11Y2gg
Zm9yIHB1c2hpbmcgdGhpcyB3b3JrLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAw
MDA4MD5CUiw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwODA+Wmhpd2VpPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMDgwPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgY29sb3I9IzAwMDA4MD4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yIA0KZmFjZT1WZXJkYW5hPkEmbmJzcDtuZXcmbmJzcDt2
ZXJzaW9uJm5ic3A7b2YmbmJzcDtJLUQsJm5ic3A7ZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDYu
dHh0PC9ESVY+DQo8RElWPg0KPERJVj5oYXMmbmJzcDtiZWVuJm5ic3A7c3VjY2Vzc2Z1bGx5Jm5i
c3A7c3VibWl0dGVkJm5ic3A7YnkmbmJzcDtaaGl3ZWkmbmJzcDtZYW4mbmJzcDthbmQmbmJzcDtw
b3N0ZWQmbmJzcDt0byZuYnNwO3RoZTwvRElWPg0KPERJVj5JRVRGJm5ic3A7cmVwb3NpdG9yeS48
L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPk5hbWU6IGRyYWZ0LWlldGYtZG1tLWhucHJlbnVtPC9E
SVY+DQo8RElWPlJldmlzaW9uOiAwNjwvRElWPg0KPERJVj5UaXRsZTogDQpIb21lJm5ic3A7TmV0
d29yayZuYnNwO1ByZWZpeCZuYnNwO1JlbnVtYmVyaW5nJm5ic3A7aW4mbmJzcDtQTUlQdjY8L0RJ
Vj4NCjxESVY+RG9jdW1lbnQmbmJzcDtkYXRlOiAyMDE3LTAyLTE1PC9ESVY+DQo8RElWPkdyb3Vw
OiBkbW08L0RJVj4NCjxESVY+UGFnZXM6IDk8L0RJVj4NCjxESVY+VVJMOiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
O2h0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWRtbS1obnBy
ZW51bS0wNi50eHQ8L0RJVj4NCjxESVY+U3RhdHVzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2h0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWlldGYtZG1tLWhucHJlbnVtLzwvRElWPg0KPERJVj5IdG1saXplZDombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDY8L0RJVj4NCjxESVY+RGlmZjombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDtodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1kbW0taG5wcmVu
dW0tMDY8L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPkFic3RyYWN0OjwvRElWPg0KPERJVj4mbmJz
cDsmbmJzcDsmbmJzcDtJbiZuYnNwO3RoZSZuYnNwO2Jhc2ljJm5ic3A7UHJveHkmbmJzcDtNb2Jp
bGUmbmJzcDtJUHY2Jm5ic3A7KFBNSVB2NikmbmJzcDtzcGVjaWZpY2F0aW9uLCZuYnNwO2EmbmJz
cDtNb2JpbGUmbmJzcDtOb2RlPC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwOyhNTikmbmJz
cDtpcyZuYnNwO2Fzc2lnbmVkJm5ic3A7d2l0aCZuYnNwO2EmbmJzcDtIb21lJm5ic3A7TmV0d29y
ayZuYnNwO1ByZWZpeCZuYnNwOyhITlApJm5ic3A7ZHVyaW5nJm5ic3A7aXRzJm5ic3A7aW5pdGlh
bDwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDthdHRhY2htZW50Jm5ic3A7YW5kJm5ic3A7
dGhlJm5ic3A7TU4mbmJzcDtjb25maWd1cmVzJm5ic3A7aXRzJm5ic3A7SG9tZSZuYnNwO0FkZHJl
c3MmbmJzcDsoSG9BKSZuYnNwO3dpdGgmbmJzcDt0aGUmbmJzcDtITlAuPC9ESVY+DQo8RElWPiZu
YnNwOyZuYnNwOyZuYnNwO0R1cmluZyZuYnNwO3RoZSZuYnNwO21vdmVtZW50Jm5ic3A7b2YmbmJz
cDt0aGUmbmJzcDtNTiwmbmJzcDt0aGUmbmJzcDtITlAmbmJzcDtyZW1haW5zJm5ic3A7dW5jaGFu
Z2VkJm5ic3A7dG8mbmJzcDtrZWVwPC9ESVY+DQo8RElWPiZuYnNwOyZuYnNwOyZuYnNwO29uZ29p
bmcmbmJzcDtjb21tdW5pY2F0aW9ucyZuYnNwO2Fzc29jaWF0ZWQmbmJzcDt3aXRoJm5ic3A7dGhl
Jm5ic3A7SG9BLiZuYnNwOyZuYnNwO0hvd2V2ZXIsJm5ic3A7dGhlJm5ic3A7Y3VycmVudDwvRElW
Pg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDtQTUlQdjYmbmJzcDtzcGVjaWZpY2F0aW9uJm5ic3A7
ZG9lcyZuYnNwO25vdCZuYnNwO3NwZWNpZnkmbmJzcDtyZWxhdGVkJm5ic3A7b3BlcmF0aW9ucyZu
YnNwO3doZW4mbmJzcDthbiZuYnNwO0hOUDwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDty
ZW51bWJlcmluZyZuYnNwO2hhcyZuYnNwO2hhcHBlbmVkJm5ic3A7KGUuZy4mbmJzcDtkdWUmbmJz
cDt0byZuYnNwO2NoYW5nZSZuYnNwO29mJm5ic3A7c2VydmljZSZuYnNwO3Byb3ZpZGVyLDwvRElW
Pg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDtjaGFuZ2UmbmJzcDtvZiZuYnNwO3NpdGUmbmJzcDt0
b3BvbG9neSwmbmJzcDtldGMuKS4mbmJzcDsmbmJzcDtJbiZuYnNwO3RoaXMmbmJzcDtkb2N1bWVu
dCwmbmJzcDthJm5ic3A7c29sdXRpb24mbmJzcDt0bzwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsm
bmJzcDtzdXBwb3J0Jm5ic3A7dGhlJm5ic3A7SE5QJm5ic3A7cmVudW1iZXJpbmcmbmJzcDtpcyZu
YnNwO3Byb3Bvc2VkLCZuYnNwO2FzJm5ic3A7YW4mbmJzcDt1cGRhdGUmbmJzcDtvZiZuYnNwO3Ro
ZSZuYnNwO1BNSVB2NjwvRElWPg0KPERJVj4mbmJzcDsmbmJzcDsmbmJzcDtzcGVjaWZpY2F0aW9u
LjwvRElWPjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDA4MCBzaXplPTIgZmFj
ZT1WZXJkYW5hPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxIUiBjb2xvcj0jYjVjNGRmIFNJWkU9MT4N
Cg0KPERJVj48Rk9OVCBzaXplPTIgZmFjZT1WZXJkYW5hPjxTVFJPTkc+t6K8/sjLo7o8L1NUUk9O
Rz4gTWVyYWwgU2hpcmF6aXBvdXIgDQo8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MiBm
YWNlPVZlcmRhbmE+PFNUUk9ORz63osvNyrG85KO6PC9TVFJPTkc+IDIwMTctMDItMTEmbmJzcDsg
MDY6MDQ6NDEgDQo8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9MiBmYWNlPVZlcmRhbmE+
PFNUUk9ORz7K1bz+yMujujwvU1RST05HPiANCmRyYWZ0LWlldGYtZG1tLWhucHJlbnVtLmFsbEB0
b29scy5pZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9yZyA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U
IHNpemU9MiBmYWNlPVZlcmRhbmE+PFNUUk9ORz6zrcvNo7o8L1NUUk9ORz4gPC9GT05UPjwvRElW
Pg0KPERJVj48Rk9OVCBzaXplPTIgZmFjZT1WZXJkYW5hPjxTVFJPTkc+1vfM4qO6PC9TVFJPTkc+
IEdlbi1BUlQgTGFzdCBDYWxsIHJldmlldyBvZiANCmRyYWZ0LWlldGYtZG1tLWhucHJlbnVtLTA1
IDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yIGZhY2U9VmVyZGFuYT48L0ZPTlQ+IDwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTIgZmFjZT1WZXJkYW5hPg0KPERJViBjbGFzcz1Xb3JkU2Vj
dGlvbjE+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZp
ZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIA0KR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIChHZW4t
QVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgDQp0aGUg
SUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuJm5ic3A7IFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50
cyBqdXN0IGxpa2UgYW55IA0Kb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLjxvOnA+PC9vOnA+PC9Q
Pg0KPFAgY2xhc3M9TXNvTm9ybWFsPkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQgDQombHQ7aHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93
aWtpL0dlbkFydGZhcSZndDsuIDxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPjxv
OnA+Jm5ic3A7PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+
PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPkRvY3VtZW50OiBkcmFmdC1pZXRmLWRtbS1obnByZW51
bS0wNTxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPlJldmlld2VyOiBNZXJhbCBT
aGlyYXppcG91cjxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPlJldmlldyBEYXRl
OiAyMDE3LTAyLTEwPG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+SUVURiBMQyBF
bmQgRGF0ZTombmJzcDsmbmJzcDsgMjAxNy0wMi0xMDxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9
TXNvTm9ybWFsPklFU0cgVGVsZWNoYXQgZGF0ZTogLTxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9
TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+
Jm5ic3A7PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPlN1bW1hcnk6PG86cD48L286cD48
L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+VGhpcyBkcmFmdCBpcyByZWFkeSB0byBiZSBwdWJsaXNo
ZWQgYXMgU3RhbmRhcmRzIFRyYWNrIFJGQyANCmJ1dCBJIGhhdmUgY29tbWVudHMuPG86cD48L286
cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L1A+DQo8UCBjbGFz
cz1Nc29Ob3JtYWw+TWFqb3IgaXNzdWVzOjxvOnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9y
bWFsPk1pbm9yIGlzc3Vlczo8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5OaXRz
L2VkaXRvcmlhbCBjb21tZW50czo8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD4t
QWJzdHJhY3Q6PG86cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+Q3VycmVudDogPG86
cD48L286cD48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+Ikhvd2V2ZXIsIHRoZSBjdXJyZW50IFBN
SVB2NiBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgDQpyZWxhdGVkIG9wZXJhdGlvbnMg
d2hlbiBhbiBITlAgcmVudW1iZXJpbmcgaXMgaGFwcGVuZWQuIi48bzpwPjwvbzpwPjwvUD4NCjxQ
IGNsYXNzPU1zb05vcm1hbD5TdWdnZXN0aW9uIGZvciBtb3JlIGNsYXJpdHk6PG86cD48L286cD48
L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+Ikhvd2V2ZXIsIHRoZSBjdXJyZW50IFBNSVB2NiBzcGVj
aWZpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgDQpyZWxhdGVkIG9wZXJhdGlvbnMgd2hlbiBhbiBI
TlAgcmVudW1iZXJpbmcgaGFzIGhhcHBlbmVkIChlLmcuIGR1ZSB0byBjaGFuZ2Ugb2YgDQpzZXJ2
aWNlIHByb3ZpZGVyLCBjaGFuZ2Ugb2Ygc2l0ZSB0b3BvbG9neSwgZXRjLikuIi48bzpwPjwvbzpw
PjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD48bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05v
cm1hbD4tW1BhZ2UgM10sICJ0byBhbiBNQUciLS0tLSZndDsidG8gYSBNQUciPG86cD48L286cD48
L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L1A+DQo8UCBjbGFzcz1N
c29Ob3JtYWw+LVtQYWdlIDddLCAidGhlIHByb2NlZHVlciItLS0mZ3Q7InRoZSANCnByb2NlZHVy
ZSI8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwv
UD4NCjxQIGNsYXNzPU1zb05vcm1hbD5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L1A+DQo8UCBj
bGFzcz1Nc29Ob3JtYWw+TWVyYWw8bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD4t
LS08bzpwPjwvbzpwPjwvUD4NCjxQIGNsYXNzPU1zb05vcm1hbD5NZXJhbCBTaGlyYXppcG91cjxv
OnA+PC9vOnA+PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsPkVyaWNzc29uIFJlc2VhcmNoPG86cD48
L286cD48L1A+DQo8UCANCmNsYXNzPU1zb05vcm1hbD53d3cuZXJpY3Nzb24uY29tPG86cD48L286
cD48L1A+PC9ESVY+PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

--=====003_Dragon314277770557_=====--



From nobody Wed Feb 15 21:42:47 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1AB129511; Wed, 15 Feb 2017 21:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rCGaP7KQsmPp; Wed, 15 Feb 2017 21:42:43 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49795120725; Wed, 15 Feb 2017 21:42:43 -0800 (PST)
X-AuditID: c618062d-d5fff700000009d8-11-58a54bd7b25b
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id A5.D7.02520.7DB45A85; Thu, 16 Feb 2017 07:51:06 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Thu, 16 Feb 2017 00:42:39 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Z.W. Yan" <yan@cnnic.cn>, Meral Shirazipour <meral.shirazipour@ericsson.com>, "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
Thread-Index: AQHSiBSzXamITAGcTE+3iRE38PAYXaFrg2IA
Date: Thu, 16 Feb 2017 05:42:38 +0000
Message-ID: <1909D5BD-B82E-419D-9B28-5783DF61F514@ericsson.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4E8883DA@eusaamb107.ericsson.se> <201702161322440072149@cnnic.cn>
In-Reply-To: <201702161322440072149@cnnic.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="utf-8"
Content-ID: <329966F86059844A8CB39721A72EE74F@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDIsWRmVeSWpSXmKPExsUyuXRPrO4t76URBnPP61h0nN7MbHH+fC+z xdVXn1ksvv18ymSxcL68xbw5J5gd2Dw2XZP0WLLkJ5PH2ZcX2Dy+XP7MFsASxWWTkpqTWZZa pG+XwJXxYcsOxoJHyhVzbixgb2B8o9TFyMkhIWAisXH2T6YuRi4OIYH1jBLLd/9jgXCWM0rc uP2LDaSKDahqw87PYFUiArcZJWau+QjkcHAwC8RJ3P/lCFIjLOAssXvNPRaQsIiAi8TcdZUQ ppHEk5W5IBUsAqoSE49/ZQaxeQXsJb5c28cCYgsJFEhMeb2EEcTmFNCVuPT5F1icUUBM4vup NUwgNrOAuMStJ/OZIG4WkFiy5zwzhC0q8fLxP1YQW1RAT2LjhWnsEHEliY+/57NDHKkpsX6X PsQYa4lz28+zQtiKElO6H7JDnCMocXLmE5YJjOKzkGybhdA9C0n3LCTds5B0L2BkXcXIUVpc kJObbmSwiREYh8ck2HR3MN6f7nmIUYCDUYmH12Dpkggh1sSy4srcQ4wSHMxKIrxtzEsjhHhT EiurUovy44tKc1KLDzFKc7AoifPGrb4fLiSQnliSmp2aWpBaBJNl4uCUamB0N9NSF+Dl2eu4 +U2QcGVWwMu8d1k7WLd8vsDBEDzVouKR9JV/pcsbyx2OSj+YstHM+dfPRfr2stXKt8sfZMjo sf3ad4jl8AVdY0V/oeV3/nZdPiRTGRq86NbnmJuZ/z5OkZv1364m5v5ekZlpQlLbl69OfKr9 5mw8A6vn/I3n9/z1kXrG7vVJiaU4I9FQi7moOBEAW7GSxr8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/y1IBTYhxh3uz1qMTeZkegH6bjxg>
Cc: xl <xl@cnnic.cn>, dmm-chairs <dmm-chairs@ietf.org>, Jong-Hyouk Lee <jonghyouk@smu.ac.kr>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-dmm-hnprenum-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 05:42:45 -0000

VGhhbmtzIE1lcmFsIGFuZCBaaGl3ZWkuDQoNClJlZ2FyZHMNClN1cmVzaA0KDQpPbiAyLzE2LzE3
LCAxMjoyMiBBTSwgIlouVy4gWWFuIiA8eWFuQGNubmljLmNuPiB3cm90ZToNCg0KICAgIERlYXIg
TWVyYWwsDQogICAgQmFzZWQgb24geW91IGNvbW1lbnRzLCBhIG5ldyB2ZXJzaW9uIG9mIHRoaXMg
ZHJhZnQgd2FzIGdlbmVyYXRlZCBhbmQgc3VibWl0dGVkLg0KICAgIFRoYW5rIHlvdSBzbyBtdWNo
IGZvciBwdXNoaW5nIHRoaXMgd29yay4NCiAgICBCUiwNCiAgICBaaGl3ZWkNCiAgICAgDQogICAg
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgICBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQt
aWV0Zi1kbW0taG5wcmVudW0tMDYudHh0DQogICAgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1p
dHRlZCBieSBaaGl3ZWkgWWFuIGFuZCBwb3N0ZWQgdG8gdGhlDQogICAgSUVURiByZXBvc2l0b3J5
Lg0KICAgIE5hbWU6IGRyYWZ0LWlldGYtZG1tLWhucHJlbnVtDQogICAgUmV2aXNpb246IDA2DQog
ICAgVGl0bGU6IEhvbWUgTmV0d29yayBQcmVmaXggUmVudW1iZXJpbmcgaW4gUE1JUHY2DQogICAg
RG9jdW1lbnQgZGF0ZTogMjAxNy0wMi0xNQ0KICAgIEdyb3VwOiBkbW0NCiAgICBQYWdlczogOQ0K
ICAgIFVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv
ZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDYudHh0DQogICAgU3RhdHVzOiAgICAgICAgIGh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtZG1tLWhucHJlbnVtLw0KICAg
IEh0bWxpemVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1k
bW0taG5wcmVudW0tMDYNCiAgICBEaWZmOiAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
cmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtZG1tLWhucHJlbnVtLTA2DQogICAgQWJzdHJhY3Q6DQog
ICAgICAgSW4gdGhlIGJhc2ljIFByb3h5IE1vYmlsZSBJUHY2IChQTUlQdjYpIHNwZWNpZmljYXRp
b24sIGEgTW9iaWxlIE5vZGUNCiAgICAgICAoTU4pIGlzIGFzc2lnbmVkIHdpdGggYSBIb21lIE5l
dHdvcmsgUHJlZml4IChITlApIGR1cmluZyBpdHMgaW5pdGlhbA0KICAgICAgIGF0dGFjaG1lbnQg
YW5kIHRoZSBNTiBjb25maWd1cmVzIGl0cyBIb21lIEFkZHJlc3MgKEhvQSkgd2l0aCB0aGUgSE5Q
Lg0KICAgICAgIER1cmluZyB0aGUgbW92ZW1lbnQgb2YgdGhlIE1OLCB0aGUgSE5QIHJlbWFpbnMg
dW5jaGFuZ2VkIHRvIGtlZXANCiAgICAgICBvbmdvaW5nIGNvbW11bmljYXRpb25zIGFzc29jaWF0
ZWQgd2l0aCB0aGUgSG9BLiAgSG93ZXZlciwgdGhlIGN1cnJlbnQNCiAgICAgICBQTUlQdjYgc3Bl
Y2lmaWNhdGlvbiBkb2VzIG5vdCBzcGVjaWZ5IHJlbGF0ZWQgb3BlcmF0aW9ucyB3aGVuIGFuIEhO
UA0KICAgICAgIHJlbnVtYmVyaW5nIGhhcyBoYXBwZW5lZCAoZS5nLiBkdWUgdG8gY2hhbmdlIG9m
IHNlcnZpY2UgcHJvdmlkZXIsDQogICAgICAgY2hhbmdlIG9mIHNpdGUgdG9wb2xvZ3ksIGV0Yy4p
LiAgSW4gdGhpcyBkb2N1bWVudCwgYSBzb2x1dGlvbiB0bw0KICAgICAgIHN1cHBvcnQgdGhlIEhO
UCByZW51bWJlcmluZyBpcyBwcm9wb3NlZCwgYXMgYW4gdXBkYXRlIG9mIHRoZSBQTUlQdjYNCiAg
ICAgICBzcGVjaWZpY2F0aW9uLg0KICAgIA0KICAgICANCiAgICBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQogICAg5Y+R5Lu25Lq677yaIE1lcmFsIFNoaXJhemlwb3Vy
IA0KICAgIOWPkemAgeaXtumXtO+8miAyMDE3LTAyLTExICAwNjowNDo0MSANCiAgICDmlLbku7bk
urrvvJogZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0uYWxsQHRvb2xzLmlldGYub3JnOyBnZW4tYXJ0
QGlldGYub3JnDQogICAgDQogICAg5oqE6YCB77yaIA0KICAgIOS4u+mimO+8miBHZW4tQVJUIExh
c3QgQ2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1kbW0taG5wcmVudW0tMDUNCiAgICANCiAgICAN
CiAgICBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBU
aGUgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRv
Y3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAg
UGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxs
IGNvbW1lbnRzLg0KICAgIEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEg
YXQgPGh0dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRm
YXE+Lg0KICAgIA0KICAgICANCiAgICAgDQogICAgRG9jdW1lbnQ6IGRyYWZ0LWlldGYtZG1tLWhu
cHJlbnVtLTA1DQogICAgUmV2aWV3ZXI6IE1lcmFsIFNoaXJhemlwb3VyDQogICAgUmV2aWV3IERh
dGU6IDIwMTctMDItMTANCiAgICBJRVRGIExDIEVuZCBEYXRlOiAgIDIwMTctMDItMTANCiAgICBJ
RVNHIFRlbGVjaGF0IGRhdGU6IC0NCiAgICAgDQogICAgIA0KICAgIFN1bW1hcnk6DQogICAgVGhp
cyBkcmFmdCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgU3RhbmRhcmRzIFRyYWNrIFJGQyBi
dXQgSSBoYXZlIGNvbW1lbnRzLg0KICAgICANCiAgICBNYWpvciBpc3N1ZXM6DQogICAgTWlub3Ig
aXNzdWVzOg0KICAgIE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KICAgIC1BYnN0cmFjdDoNCiAg
ICBDdXJyZW50OiANCiAgICAiSG93ZXZlciwgdGhlIGN1cnJlbnQgUE1JUHY2IHNwZWNpZmljYXRp
b24gZG9lcyBub3Qgc3BlY2lmeSByZWxhdGVkIG9wZXJhdGlvbnMgd2hlbiBhbiBITlAgcmVudW1i
ZXJpbmcgaXMgaGFwcGVuZWQuIi4NCiAgICBTdWdnZXN0aW9uIGZvciBtb3JlIGNsYXJpdHk6DQog
ICAgIkhvd2V2ZXIsIHRoZSBjdXJyZW50IFBNSVB2NiBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHNw
ZWNpZnkgcmVsYXRlZCBvcGVyYXRpb25zIHdoZW4gYW4gSE5QIHJlbnVtYmVyaW5nIGhhcyBoYXBw
ZW5lZCAoZS5nLiBkdWUgdG8gY2hhbmdlIG9mIHNlcnZpY2UgcHJvdmlkZXIsIGNoYW5nZSBvZiBz
aXRlIHRvcG9sb2d5LCBldGMuKS4iLg0KICAgIA0KICAgIC1bUGFnZSAzXSwgInRvIGFuIE1BRyIt
LS0tPiJ0byBhIE1BRyINCiAgICAgDQogICAgLVtQYWdlIDddLCAidGhlIHByb2NlZHVlciItLS0+
InRoZSBwcm9jZWR1cmUiDQogICAgIA0KICAgIEJlc3QgUmVnYXJkcywNCiAgICBNZXJhbA0KICAg
IC0tLQ0KICAgIE1lcmFsIFNoaXJhemlwb3VyDQogICAgRXJpY3Nzb24gUmVzZWFyY2gNCiAgICB3
d3cuZXJpY3Nzb24uY29tDQogICAgDQogICAgDQogICAgDQoNCg==


From nobody Thu Feb 16 03:16:20 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676D21299ED; Thu, 16 Feb 2017 03:16:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r12rAYB1rbyg; Thu, 16 Feb 2017 03:16:11 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 813B3129A95; Thu, 16 Feb 2017 03:16:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF5572CEB1; Thu, 16 Feb 2017 13:16:05 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdZTPBFA7836; Thu, 16 Feb 2017 13:16:05 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4D25D2CCBA; Thu, 16 Feb 2017 13:16:05 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B5B48FA3-8BDE-46EF-B954-A5F7C806850B"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <23D53438-3D90-4FC9-9984-3CDA0E0F5B9D@ericsson.com>
Date: Thu, 16 Feb 2017 13:16:05 +0200
Message-Id: <97C5BFC3-EB81-4421-B85B-F99EAC05715E@piuha.net>
References: <148623668946.2758.17261798423102538026.idtracker@ietfa.amsl.com> <23D53438-3D90-4FC9-9984-3CDA0E0F5B9D@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/hnLiPqZvJGqvX5P9pErP6V3DrII>
Cc: Gen art <gen-art@ietf.org>, "draft-ietf-6tisch-minimal.all@ietf.org" <draft-ietf-6tisch-minimal.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6tisch-minimal-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:16:19 -0000

--Apple-Mail=_B5B48FA3-8BDE-46EF-B954-A5F7C806850B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 05 Feb 2017, at 19:43, Suresh Krishnan <suresh.krishnan@ericsson.com> =
wrote:

> Thanks a lot for your review Brian.

+1

Jari


--Apple-Mail=_B5B48FA3-8BDE-46EF-B954-A5F7C806850B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpYn1AAoJEM80gCTQU46qzlcP/2PG7URA1hjqvQ+ncAuHWx5K
hgN3o+6bFAGz+mFqQWfVQRkl36EXR13ozb1TSD34KjD627ZithkfOV5Wa2qUU7nV
2GC2Jf/8aolTR5iKan9FbC3X+jsLjVv1llog+e9U654vRIf8ir9hfrUcQKS7WZ9X
IMONTuAQqQU1H+sPPkD6y3fHWI3CHnYzklgYSn4ks8D00YV6y9YIwt+XO+2/uCaD
G9j+uN/y3ehVgiWVmdNBUBpVg76so0qcJ7WwSNt5LRXGMZxNA2t5YRPDDtbNNazY
XrCW+T2Uqq10s+PZSRIvu9V1PvUB9cQZi6WTAUhST9IzAgeCmgSqr0PqrdAvo0Mc
Dk5KxNaGVJWnl22APWbiPY4eo9thA1uW1qymqNPmAV1M2eVAAJG7GkrOCGX9OYCy
I48xkvtdTQEEKgk9Fkvt3+hXCNavfCetlnMw++gelsHa1OgDSGEcq8K81xUmma02
P6Nj5D4Yo78IAxIvZtf3+mDhRa7ouAdBV75zlnrjZYQFzarYgbEZV+e5+a+J1m7h
KBXqChmzgYdAZF/uDnxK22GsEsZDIIfUBVABHFXM9srWoz4XDzACObfNqCqOD3Ec
90At21KpCmTSewD9r+YEIbSeb6sU4JKgve7tG+ZIHlCw1+uaJEEeiMNG9cTBW/+v
06SxcPDHQOSwPUVhPViO
=8j8A
-----END PGP SIGNATURE-----

--Apple-Mail=_B5B48FA3-8BDE-46EF-B954-A5F7C806850B--


From nobody Thu Feb 16 03:55:53 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28BC4129735; Thu, 16 Feb 2017 03:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQGvKadaARvb; Thu, 16 Feb 2017 03:55:50 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1650B129563; Thu, 16 Feb 2017 03:55:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3173F2CEB1; Thu, 16 Feb 2017 13:55:49 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RM4-0O1cINg1; Thu, 16 Feb 2017 13:55:48 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7CF842CCBA; Thu, 16 Feb 2017 13:55:48 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D4DDE6F9-30B0-4A43-B8EB-E8B1E3CFDC3A"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 13:55:47 +0200
Message-Id: <EA4025AC-695C-475F-950C-2AA8DEA294F8@piuha.net>
References: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Db4hI_DC3hAWnO9i7wQkARmrppU>
Cc: Gen art <gen-art@ietf.org>, oauth@ietf.org, draft-ietf-oauth-jwsreq.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-oauth-jwsreq-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:55:52 -0000

--Apple-Mail=_D4DDE6F9-30B0-4A43-B8EB-E8B1E3CFDC3A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Many thanks for your review, Joel.

I have balloted no-objection for this document on today=92s IESG =
telechat.

Jari

On 03 Feb 2017, at 01:03, Joel Halpern <jmh@joelhalpern.com> wrote:

> Reviewer: Joel Halpern
> Review result: Not Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-oauth-jwsreq-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-02
> IETF LC End Date: 2017-02-13
> IESG Telechat date: 2017-02-16
>=20
> Summary: This document is ready for publication as a Proposed
> Standard
>=20
> Major issues: N/A
>=20
> Minor issues:
>    Why is the example if section 4 (and others later on) described
> as
> "non-normative"?  Is it incomplete?  incorrect?  An example is, by
> definition, not a full specification.  The language seems designed to
> reduce the value of the example.  I would recommend removing all the
> "non-normative" notes from the examples.  They are clearly stated to
> be examples.
>=20
> Nits/editorial comments:
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_D4DDE6F9-30B0-4A43-B8EB-E8B1E3CFDC3A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZNEAAoJEM80gCTQU46q9qgQALAqVO+Fq3ngC7gNtrtIL6KY
0rJ3MRhLGdE5MzXP2c2Gb749J2BBlaRuMHb0uVRV51Lg1b9/LjmzF+6LSC/gDvlT
x4+sqQM6ldvlBJ92UxznzIWPIrEoxM9InDU3Qh1GohEqgw0+zcBshwtyLI0By/yr
yORUMyXZMNxxfrFAS3LJ8Wt3XWD8HA1OYrWYlHWygFj+UzTYlol/fZVOeP/LQuna
wgijEUxZ3X+xz6iG/prbM8vKrxTGPFLP4jIam8wAdswDX+iqi7f61zNpHiHkdbnR
RF6BeJd1A4Prf6v0HxN6uHmFGBb8RxbdLNFHGbmKrvyN6bJal8iGZ304RbUNjOuX
qYiGJGA+YHetJOs27Krerd77Dt0ccKsfaGZ4P3vTe4MWeiaveb63DUaY3pEeJpP0
iaIDziBZaUp3yLrawFVTIqwQxsUzEF3b+z7gX/anZNGv18dIjP/5491lGSN3wJVR
lQln/vAeiQb3kULFpN2jDd/MHlY8xhTWlvcxpSSxc0+RYrnXtTjiOTFT9PrVBac5
22apTzkrNe/yGNfMV9OigKQmPact/JXxYiyL6uMm+8Ifdhb/zZkVBcFukAoCVZRt
pdN4aWQV7wmb89gBR6DdJpSxodIg4NJnhSgkBs/J2XJlC5rnJopCIKoG8ftQI9PV
nhiHUiHVN3qTs9qHMC/j
=jkDx
-----END PGP SIGNATURE-----

--Apple-Mail=_D4DDE6F9-30B0-4A43-B8EB-E8B1E3CFDC3A--


From nobody Thu Feb 16 03:58:06 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B248129735; Thu, 16 Feb 2017 03:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44gzcTKTa0Ze; Thu, 16 Feb 2017 03:58:04 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D1D2B1294C8; Thu, 16 Feb 2017 03:58:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2A75A2CEB1; Thu, 16 Feb 2017 13:58:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMQVPHAWHZll; Thu, 16 Feb 2017 13:58:02 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id AF53E2CCBA; Thu, 16 Feb 2017 13:58:02 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
Date: Thu, 16 Feb 2017 13:58:02 +0200
Message-Id: <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
References: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
To: Orit Levin <oritl@microsoft.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aYaC1_2ssTOvX0FzoQC9baU8-aI>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:58:05 -0000

--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Orit!

(Authors, did you note the comment?)

Jari


--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZPKAAoJEM80gCTQU46qed4P/3pzWrR9+kmINEBeZ+wivV7s
cWdAOYiBhbRj/Qplm9dFbLGi7gWBVJ75sBrFhxsHvbow3rVty7aSZ45m/IpPArFV
nv9WVtbCGjjCl1dHNPoOmyMtYN4+d0DcJqpBDRs8VoC5BVmDYr8Uk/b6Mtk6Qd1r
dCffEyJ1pf0kOTH9+OGE7KOP5A2RDuugbtXBwtJ4g96NC7BgFHwOnZdVOZF7bonJ
EXfWU+AYz7ky7qLSm5FSU2bh/a8jNkNTQFz9/jGSc+dk/WDuBQovpAagXtHGpPU6
K7mrTJbNXBBys9/8Gn6VfSGxHXyRZ4+vQDXotmTy9psmtTr6dKCPbDatCphw22bN
GJMvz52ByZwM5c7esPAosETrXqmTI8/kYY49fyRf6JyE3YdxQ/VaGN+I61LBT+Zd
2N8QjoOKtVAKGbzjaEKy6b4X5hOhOo2VHzqnNARzWrH3O1n6aFFVd65TCN6ZfbDp
2JWmFyLQTSmUKKUg4JmI1zWDYbqINAGFGKjCJOsiHgIGN++6/qQZuBcH4Du/FKQ3
sf3JPzB0Baj6zf4b0nHpZvxv25vBi/HG0qDb90H5XNM7YN4O0cP+MfhnaGbVlEV6
VbUe9SuI2xD5DUauk3rXPbm7cP/yRMuLvYvL68yk30swDSSAFppKVCb57MWp6su9
fsDPTlv58+CGB8PxCuXq
=p2Da
-----END PGP SIGNATURE-----

--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141--


From nobody Thu Feb 16 04:04:11 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA85F1294E6; Thu, 16 Feb 2017 04:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khIB9vCfk830; Thu, 16 Feb 2017 04:04:02 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5939A129563; Thu, 16 Feb 2017 04:04:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF6BA2CEB1; Thu, 16 Feb 2017 14:04:01 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gz-uZ9gl_iij; Thu, 16 Feb 2017 14:04:01 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2A3632CCBA; Thu, 16 Feb 2017 14:04:01 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:04:00 +0200
Message-Id: <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com>
To: Roni Even <roni.even@mail01.huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/DWd4jEozquOniEaLjG_E9CvU2s0>
Cc: dhcwg@ietf.org, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:04:04 -0000

--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Roni: thanks for your detailed review. I also appreciate
the responses and changes by you Tianxiang. I have
balloted no-objection for this document for today=92s
IESG telechat, and expect that the discussed changes
will find themselves into a new document version at
some point.

Jari


--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZUwAAoJEM80gCTQU46qJrQP/2Q3KFZv7t9N/+MIRJoIej15
ZkQNNWzW/yp7Xw33FPLHet7cFA2Bz0Qijudj0UmplChFxLxzDLeAu8rKxN21yb6n
Vb6gJs7kITlHyWsyElialCKmVsCIULZ5oAzP5VmKQzPSNUzBh9abp+6eEP4NsmMb
k9FMxPt8iDWhCmfZGg4JHn8XPx5cMe0ccH5bs84tugEaQh4dQU34O/lhFH7I7uYd
8TZGV68W3hE6rZKSCp+Po7qlIDWZ0txT6UlmqFXLhvknm9uNLSev9RKvry+YFWSV
NvO+uXMd1xEpQjm5PPgihYpcqnvjFZA+d+gZdOKTCaqUYQUrYufu71NKrFmU4hSr
Wp4jEI6FaWPOXemapDIU/tsAHG0hEKpNDGH6Tky009oIQv4PS2R7BB6Otb6fU1zC
dtCoTgYAufK/hyuZxmO7rRskasSKO1k/0SOxQy8A06LmJFMcmDuOGK1KIAO0NVzq
3FNhG9Ta+K86eJXx0my/vUfEezdKcdmoBVx+qSS15qkUC8J4O1aFyleyA8I+AAo2
toKrWWuaPnG+mFoGLevGtJdAUf7sHsv5SpPIVq4N4XwuxbfUEQlvU/xy0et5xzcH
c6NqEMNPotWHfqlnJ9upn81ADghggwop9WlryRB7D4LA1Lw9t2uZ6Onng6myELPp
tRzqX6N/uNBaGjrQYX3/
=gTNY
-----END PGP SIGNATURE-----

--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC--


From nobody Thu Feb 16 04:25:17 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDFA129ABB; Thu, 16 Feb 2017 04:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-_MLEy6ZGkE; Thu, 16 Feb 2017 04:25:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id A1028129AB8; Thu, 16 Feb 2017 04:25:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F0E562CEB1; Thu, 16 Feb 2017 14:25:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFfAbCOkf2kk; Thu, 16 Feb 2017 14:25:06 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 637782CCBA; Thu, 16 Feb 2017 14:25:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:25:05 +0200
Message-Id: <9FDE8001-485B-47F9-A05A-831680693868@piuha.net>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
To: Dale Worley <worley@ariadne.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/GCZZJleBHbbfCM9w-9LTN2sdxd4>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dmm-4283mnids-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:25:10 -0000

--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dale:

Many thanks for this review, which indeed was exceptionally useful. =
(=93Super=94 as Charlie put it.)

I have placed a no-objection position for this document for tonight=92s =
IESG telechat. But I think your discussion on the details of changes =
inspired by Dale=92s review probably needs to continue, and I also see =
that there are other points made by my AD colleagues =97 that is another =
discussion that needs to finish.

Jari


--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZoiAAoJEM80gCTQU46qfEUQAKmmOFzjI9bnDohcwkO+U1pa
JNE7yIB6O7gL233Mc5rIAXA6HzvuLLf0BEL3oxZMzKitl7gRdxiU+spANxgCr/Gx
WpMDNFtXMa1Mh2rET0m2bQNI7/sHTFg14RfeH7PQIcV3jtVXGGhd/Zwou328s3Oo
xyj5JNNuX83/FAdqiklk+DTdh80km1yagx3836MVnUaieYCBQrN0XD0odnuKrzRa
14n6Bb6hIsd4O2M3zntwqPM+UAsJVoTgaPmULQnnZ28eky/4ZnuRXYs8iCsaPjGR
0NLjjNqY4Av96qk076YiCB2c+BewRmlND9ZzquHGCpGjCBxAohX0G+8LokNB0rNs
YWyT4nvi8i9a/nopFBagf0kLl/eVf6mszObuxU+k1epIUuygzEzJAlPbvGRSuj/p
8+MkKHIbd+gq85fH4tTQYicjxkDLTNUWibJAHIfarFxexYhtEtkQ5tkg+t2fOKwD
rNy5+j/3iO+kz11Qv5ouOnu/pHCTKQpyLQTm7DRpNP/Nl96sX+dA/TA9HF2nlWF6
LPp2yr1D0rewYICb5kXXAgvWvey5eReuNUH/GKhQq2RALzpPWZesChiTHeBbMRYn
4P/E5oIhRSXO2Do6BOjakpdo/QJATdZlfRq5vCH3Ji+wcDfvAXWQ3RWu3CAl8KVv
Rm2RtfguzVwT/OWQK6lT
=R9VL
-----END PGP SIGNATURE-----

--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D--


From nobody Thu Feb 16 04:41:26 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB7AF129ACA; Thu, 16 Feb 2017 04:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SU8Z20zLRIcs; Thu, 16 Feb 2017 04:41:20 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 85D46129AC1; Thu, 16 Feb 2017 04:41:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 05FF62CEB1; Thu, 16 Feb 2017 14:41:19 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GRudGIvt2-y; Thu, 16 Feb 2017 14:41:18 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 76B4A2CCBA; Thu, 16 Feb 2017 14:41:18 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_BAE09164-2D93-4507-889E-3F50B23DFA0A"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:41:17 +0200
Message-Id: <D81E8E01-4C14-4071-9EB5-1C939ED648D6@piuha.net>
References: <148676904616.29176.18172899169844310297.idtracker@ietfa.amsl.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/wDkOogb6XaXe8kULrKUI0Foj_18>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, gen-art@ietf.org, ccamp@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:41:21 -0000

--Apple-Mail=_BAE09164-2D93-4507-889E-3F50B23DFA0A
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your (re)-review Pete

Jari


--Apple-Mail=_BAE09164-2D93-4507-889E-3F50B23DFA0A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZ3tAAoJEM80gCTQU46q7+sP/i15tUvXrBQi3tut7daJqPSd
PgpyQom0ccoidpCl7vBEvcTYpFr3dje05y/3yHek/ixXPhz2NOKVPbXuFKyo9yRF
9SZCMxBjD4oryfH/hEk9wxSKv6TO6A4SdWGbiMsY2tmYfSt3ReBL9+22RJ//OCF2
m2f+/pFQ3AvSz899JRn7d8Frrk6YP/lmhqmB/SOzZZnfykGUR0tkXUkh9nNL5mrM
FtlbmnQSYBr/o/crZKIJtz0vPzkAE/6MASVuyZpmT+LS85pJyzxqXWttizc5WaTg
i7CmN1Jl8sLKkUd9Am2T2Up7cKW47qBJynNT83ndST67R+1QkcIWZ4GUrmU8Rx/s
pzojL6xNOtBWKoWM/YmIsBIYFWP3bx/qtBs8Fdw0QvRTZctPHmblrSfMQjcSRS5J
a39fwYkT2zE8gPBkdEhG5l69rOnMPrWmGNvI4Ztjv9AqrYl1CBTGV4rGaB0kKxxo
OdcGoNCkSziQb5DgE81ReEkiHltIQ3oud216l6z1SFUTNgrxf23AUNjMHvIzWJY7
nziQydjEc3I3/qC/DyhEXOi+SM03NL28kALCgHzam4WSH6+JnUzouILobJHqBQc4
yKi84y+UHHC9i5Ei9s032ZHfz+CayAKlXP12S91/5Z/pAmn1IPJ/hxNHLi8aVrrP
Pd4HBm3+o6tlxtCGg2BT
=Tk2U
-----END PGP SIGNATURE-----

--Apple-Mail=_BAE09164-2D93-4507-889E-3F50B23DFA0A--


From nobody Thu Feb 16 04:42:10 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DEA9129ACA for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2017 04:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CCpk3bXPjEC for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2017 04:42:07 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B8D78129566 for <gen-art@ietf.org>; Thu, 16 Feb 2017 04:42:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 188EC2CEB1; Thu, 16 Feb 2017 14:42:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80b00YIJPtOB; Thu, 16 Feb 2017 14:42:05 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FE632CCBA; Thu, 16 Feb 2017 14:42:05 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E16423EF-1300-4368-B369-A9E826CCBC95"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFD8FEF@ESESSMB209.ericsson.se>
Date: Thu, 16 Feb 2017 14:42:05 +0200
Message-Id: <39499DD9-05A3-45AF-A047-E2DDD460D3AF@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B4BFD8FEF@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/FMxuqygcnz4UmFz5fHb7Pu2U9o0>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dnsop-edns-key-tag.all@tools.ietf.org" <draft-ietf-dnsop-edns-key-tag.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-edns-key-tag-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:42:08 -0000

--Apple-Mail=_E16423EF-1300-4368-B369-A9E826CCBC95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks!

On 01 Feb 2017, at 23:18, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document:                       draft-ietf-dnsop-edns-key-tag-04.txt
> Reviewer:                         Christer Holmberg
> Review Date:                   1 February 2017
> IETF LC End Date:           14 February 2017
> IETF Telechat Date:        16 February 2017
>=20
> Summary: My comments on a previous version (-03) of the document have =
been addressed, and the document is now ready for publication.
> Major Issues: None
>=20
> Minor Issues: None
>=20
> Editorial Issues: None
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_E16423EF-1300-4368-B369-A9E826CCBC95
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZ4dAAoJEM80gCTQU46qyEIQALPrYY/M6cKO08hlSp7vSUYn
nc6rUtBoWJQw3icM3IgRclJgQqkckQSX1fI1Rj+t7eRbvX2cLxP8ljNGjoi7beZ6
yoZWsHlv5utvBVfH/jTXJGBBPcv0bUWRt8O5L3/UjjjoJzD2RSjwQMMZeEb95Oeo
LcxDvyN7kyCCTxwRmmcAd9+Me5QOnnsoEWwYkKp4REkeHp6/wLXNtR8XCgMuDpQ4
q37hbcjmqH1cMui2qzSWWQ7WQn9u3R0BPFoGbbsFLe8M0UXe0gjkWBoDCEQi/1yk
mbOB1LLO1++dJLFudBTcbXjJrgy5VYm+EIjGZkPOzT1Ck1JURvvgvhKh7nCmA8Cg
xF/1CHqHPs85IItSaYd+LuVrhAu/HvGqNImsMvmLo1VyBZAhSkKDkoUCXUZFR9hg
jsdrTO/NuEYnfyQ941LJPPXcTVr8+TKL2HnJ0Pc+/Ic6Nc2H/UAWnvBu9+XNzmfy
snl4uUKjHprBXY0vbcd67eqI/QdEPX3x5ldGq/QRj4VRr8IqLgqKD7eL7zB1EviI
Rj+ep+jrhPnSO+BKN0yf8jw9RS2gt/J79gNC7GLaJCWT+yOOxBR/7S5zd15FQv0G
MEnPv/SrDckKHX8A9ocxIORUo4usBTGu9ceKat1AYU88juDTBf46XbM56tbvUmtn
OjmTV6blqJxl6RaG6YzK
=wnAD
-----END PGP SIGNATURE-----

--Apple-Mail=_E16423EF-1300-4368-B369-A9E826CCBC95--


From nobody Thu Feb 16 04:44:35 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8C9F129CEC; Thu, 16 Feb 2017 04:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z3BOvKzl98Pi; Thu, 16 Feb 2017 04:44:33 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A9831129578; Thu, 16 Feb 2017 04:44:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E2A282CFA8; Thu, 16 Feb 2017 14:44:31 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOCteq07tZLp; Thu, 16 Feb 2017 14:44:31 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5F72E2CCBA; Thu, 16 Feb 2017 14:44:31 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_8FF22788-A972-4177-99A0-B2A8709E537D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9ce42a7d-64d3-4003-93ee-9119afc78283@gmail.com>
Date: Thu, 16 Feb 2017 14:44:31 +0200
Message-Id: <1B881633-B6E1-4741-874D-D727BAC2C161@piuha.net>
References: <148451784736.3226.15889507299394185360.idtracker@ietfa.amsl.com> <a35bfb84-091b-a408-9a53-0b6dbd5cd003@pi.nu> <54feb39c-0e5b-9c12-0ae2-d5757316c9c3@cisco.com> <F64C10EAA68C8044B33656FA214632C85DE45354@MISOUT7MSGUSRDE.ITServices.sbc.com> <9ce42a7d-64d3-4003-93ee-9119afc78283@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Xv-U1BkjUyqKMi5E_g96ez7w6Js>
Cc: Benoit Claise <bclaise@cisco.com>, "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "BRUNGARD, DEBORAH A" <db3546@att.com>, Loa Andersson <loa@pi.nu>
Subject: Re: [Gen-art] [mpls] Review of draft-ietf-mpls-tp-linear-protection-mib-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:44:34 -0000

--Apple-Mail=_8FF22788-A972-4177-99A0-B2A8709E537D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

All: thanks for the review and discussion. I plan to vote =93no-objection=94=
 for this document in tonight=92s IESG telechat.

Jari


--Apple-Mail=_8FF22788-A972-4177-99A0-B2A8709E537D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZ6vAAoJEM80gCTQU46q+cgQAIIFt6nf82vuLWOpdDCbY9fQ
4wq5tzeEcGURnAQW6wVXzmt0K1C+M6EXtLtzXmTfOpHv2NS47SkWbTQS+8jStbUy
+OBOCfbUSW5+t6U5mjrDfgEcpFaIBqwUwNj2i6rl6bo5sOkVvLCJA/b6T8W4DMTw
Gl7AwecEoDpG/rBhSnTIYvPI5lJMu0mRB/QYzVcFE8WLxqv5433MhzHruw7Fv2mr
1cj0kumVPNzo3q86qUok/oOBj9tXxWs3LPC3Nhi1S4DCvVcADFWjnvQXw2KDV2Xd
//QBAYIuvBS4sqJOI6KvtgG9h9xYx9pf7+j/lsgqEbmEsaAB7GSsVp17wBHihCsH
mizbDaN/LuTRn4qrsdeyoK62xgN9fRSRyf2RX9zWdqaXz9YyPJsUiDdLyg2c2jcy
z4f1HQDzXNQhPEZX6pikP1qnyYSVt5phV9+LvnflslHm4cGkMwBuZMdQDiKRmnij
yKABOCONUkchGxyRZDTpJUA3paCQ+hU70BNiKpSqvl/nKLzP6tdNiziQlOmmtFrI
zKt3EIEeqM8wwzLwR4InYzJuY7b1N91lvw05gtZfeiyjBHqgBWcVrKIOSzluWQG9
GMrVSvk3r/piRP4bVZKymh+v3kMlbdjm5EZVOe9jsfzUOAuSOGwyW3kDNEt+FyNc
5ZyTJk0awboMJzpt86A8
=pDhG
-----END PGP SIGNATURE-----

--Apple-Mail=_8FF22788-A972-4177-99A0-B2A8709E537D--


From nobody Thu Feb 16 04:45:38 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80D941299E9; Thu, 16 Feb 2017 04:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, TVD_SPACE_RATIO=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1muk9JJp1kO; Thu, 16 Feb 2017 04:45:31 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 55BC6129595; Thu, 16 Feb 2017 04:45:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AD7E92CEB1; Thu, 16 Feb 2017 14:45:30 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fX6OYejIBaHh; Thu, 16 Feb 2017 14:45:30 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3E0112CCBA; Thu, 16 Feb 2017 14:45:30 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_418A98C5-A853-405B-BEF9-7DAB71234614"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9007DD69-14A7-4B15-9F2C-A8CB0223E817@ericsson.com>
Date: Thu, 16 Feb 2017 14:45:29 +0200
Message-Id: <5C1211FA-A82D-42AB-9AFE-0A56AF0B6827@piuha.net>
References: <148676797054.29317.17761463000129345942.idtracker@ietfa.amsl.com> <9007DD69-14A7-4B15-9F2C-A8CB0223E817@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/RxYUCKgtFoC-4JhboWGAgg4REcM>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-sctp-sdp-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:45:32 -0000

--Apple-Mail=_418A98C5-A853-405B-BEF9-7DAB71234614
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Brian, Christer: thanks.

Jari



--Apple-Mail=_418A98C5-A853-405B-BEF9-7DAB71234614
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZ7pAAoJEM80gCTQU46ql6QQALcxEP9o/y+gqrZCH6nZbuLa
sljywMpkCVIqfft5zD6kSsrX/UWz61AZse8AJfTBhXdFNP7AOLGeF7mmha5tdoIl
cnJIBMHwyH6r4AKHgJB9YmPcLLBL9WqKg6W6Gi3cNBytgM+MjsKex4kWuEekD6O9
uVJ8aOxI6zQZ1Hk+nuZnnVOwor16mG7WRSVrNneRtdIQGgVQ5so7Vufyn6uonar2
9idhyyWg1+8+WfgbwAqduluq/28ZFe2aI5xG6mVq+vsbwcp5tlzweoQEAGD8eZ21
yvx96sUu5/FetvZTLc7Btdm6urzdnqCDJT6K12wUEgivm/DQKKu3up4pJRLoaAOc
KSUpdxYEHe06ndch6bJaC74yTGBFUHi7aVffjsEHtjgC4UZWaVghfFM2rCWPfKEe
p3FoYnxQBVOFN5NBmSvJTXcRrH+hN9WORv15AQszzqhBu5XFxGW8osls38bwp7Fq
2hH5phUwdeP0VnOHC0yYhV6Jg1ASn7TiUPUBl7VZ3jraBAG9jyn1yLLBa4kA9Kyf
Gd4CPdw+PhZNOv/oYujqVbznMzg8wIbv6TjMRaNWeyaRF700U3JLjx7oSGsdGxiD
CIK4jeBTjollU+VBFbF/HcCNh4UCOhJ9VSSOJGvfswGcLpv+xeaJw+RNXds1N5PU
JyA9sBGZD39RTpqJy6GG
=F5wj
-----END PGP SIGNATURE-----

--Apple-Mail=_418A98C5-A853-405B-BEF9-7DAB71234614--


From nobody Thu Feb 16 04:47:07 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E6C129546; Thu, 16 Feb 2017 04:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WyNfbCrIQDw; Thu, 16 Feb 2017 04:47:04 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 881AC1204D9; Thu, 16 Feb 2017 04:47:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DEC072CEB1; Thu, 16 Feb 2017 14:47:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vn7vIOq0t6Lx; Thu, 16 Feb 2017 14:47:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 40FFD2CCBA; Thu, 16 Feb 2017 14:47:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4DDFA575-8B79-488C-BEE0-C77A3D3D1FD4"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201701241633.v0OGXSBE087413@givry.fdupont.fr>
Date: Thu, 16 Feb 2017 14:47:02 +0200
Message-Id: <6D68BE00-1E51-44C4-BDC1-B2EDD7CA8AE3@piuha.net>
References: <201701241633.v0OGXSBE087413@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/sCRjt2tmkAHJFKvVGV9f5nkmmP4>
Cc: gen-art@ietf.org, draft-ietf-bmwg-ipv6-nd.all@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-bmwg-ipv6-nd-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:47:06 -0000

--Apple-Mail=_4DDFA575-8B79-488C-BEE0-C77A3D3D1FD4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for the detailed review, Francis!

Authors =97 did you make a note of the comments? Did not see a response=85=


Jari

On 24 Jan 2017, at 18:33, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-bmwg-ipv6-nd-04.txt
> Reviewer: Francis Dupont
> Review Date: 20170116
> IETF LC End Date: 20170123
> IESG Telechat date: unknown
>=20
> Summary: Ready with nits
>=20
> Major issues: none
>=20
> Minor issues: the title (and the Abstract) is a bit misleading: it is
> not the benchmarking of the ND protocol which has ~12 different
> functions but the benchmarking of a particular function on a router.
> Now it is the critical one so my concern is more the document is
> limited to only this one...
>=20
> Nits/editorial comments:
> - ToC page 2 and 7 page 12: Acknowledgements -> Acknowledgments
>=20
> - 1 page 2: the limit to a router explains why the verb send is
>  replaced by forward... and why there is nothing about redirection
>=20
> - 1 page 2: determine the IPv6 next-hop's link-layer address
>  -> determine the outgoing interface and the IPv6 next-hop's
>   link-layer address
>=20
> - 2.2.1 page 5: et cetera -> etc
>=20
> - 3.1.2 page 9 (twice) and 3.2.2 page 10; recieved -> received
>=20
> - 3.1.2 page 9: IMHO you should define the "initial" term (for final
>  the meaning is obvious)
>=20
> - 3.2.1 page 10: (i.e.,IPv6 -> (i.e., IPv6
>=20
> - 3.2.2 page 10: in "packets-received will either be
>   equal to zero or packets-received." the last received -> sent.
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_4DDFA575-8B79-488C-BEE0-C77A3D3D1FD4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpZ9GAAoJEM80gCTQU46qINUP/AmC9deGdlEECiCu5+Cvw8dh
67sSl7KPnSQJpKB2AR6JRZnpAfrIKZTfLN4pU/QkVTqZZ8btXAju7WN0lRV2psGm
S6yPtjeVBAEVw2sYLXblBPZ5RJCnsyF505crbiHhX6MsvrkoCzff8frh4wWONWb9
JbEGnY9LtKmvp2kRaTy63qZsESTujidqolZqoFIXyvuqsYSZwE8SSp+qlzjZgcec
FNnS6hVa8ORut++zq65DHu98ZOfVrPPIagXdAmOMg2UGciU1twoEVFe6dRfqdNJ8
UK93iSMZh9ec189XIuoJlZRbMuww0gsOmfoIf4PTADk9nmyEHoWu/q2523DRBn3h
GZGcUnHG3KlBVYxajVWYgp+vDFRrAC11xr4tnIhZhAsivc4mdeI9YxdIdv4DJnaW
gXGwwLbcrqYNPQ8Gtt7i1MGUu1heLOj3sVf6ChpNVH0MzDEHMSfeKa+TNO26ZNzA
Mj6qDOQmI4QtiWpd1ngeEQp66/qNcnFSJtQpHL62yJ39Q3P1Mi50QC+ZFj/1uTTj
8dCozuZiP/aYaVU9skmYLffmGQywTfHnJHCllg2F/mQOaEENSjYKkacBA4MxM5Wi
Ptu88Y7YYHmOvC/4rVAUPKqpup2Qpy6UQjeToOwjDJ9Px9uzn15ggEffxhAThzSS
eW6qikjiPW3Y0Zh6nuFH
=nXRy
-----END PGP SIGNATURE-----

--Apple-Mail=_4DDFA575-8B79-488C-BEE0-C77A3D3D1FD4--


From nobody Thu Feb 16 05:19:48 2017
Return-Path: <acmorton@att.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7231295A7; Thu, 16 Feb 2017 05:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level: 
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5BUt3m1O0-2; Thu, 16 Feb 2017 05:19:39 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 395D6129481; Thu, 16 Feb 2017 05:19:36 -0800 (PST)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v1GDFJ9C018832; Thu, 16 Feb 2017 08:19:35 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 28nax6t0dy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 08:19:35 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDJYng004856; Thu, 16 Feb 2017 08:19:34 -0500
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDJRQ7004726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Feb 2017 08:19:30 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 16 Feb 2017 13:19:20 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDJJXq001018; Thu, 16 Feb 2017 07:19:20 -0600
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDJFaW000859; Thu, 16 Feb 2017 07:19:15 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-blue.research.att.com (Postfix) with ESMTP id 5089CEF831; Thu, 16 Feb 2017 08:19:15 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Thu, 16 Feb 2017 08:19:15 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Joel Halpern <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Review of draft-ietf-bmwg-virtual-net-04
Thread-Index: AQHSf/jwpPG7afFfS0SRwGrkrzC5RaFrpodQ
Date: Thu, 16 Feb 2017 13:19:13 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF68BF69@njmtexg5.research.att.com>
References: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
In-Reply-To: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.246.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160131
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/pH7i10K997AMK0W1E4Se8Rf7bQI>
Cc: "draft-ietf-bmwg-virtual-net.all@ietf.org" <draft-ietf-bmwg-virtual-net.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-bmwg-virtual-net-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:19:40 -0000

SGkgSm9lbCwNClRoYW5rcyBmb3IgeW91ciByZXZpZXcsIHBsZWFzZSBzZWUgYmVsb3cuDQpBbA0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEpvZWwgSGFscGVybiBbbWFp
bHRvOmptaEBqb2VsaGFscGVybi5jb21dDQo+IFNlbnQ6IFN1bmRheSwgRmVicnVhcnkgMDUsIDIw
MTcgNDo0NCBQTQ0KPiBUbzogZ2VuLWFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1ibXdn
LXZpcnR1YWwtbmV0LmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4gYm13Z0BpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA0DQo+
IA0KPiBSZXZpZXdlcjogSm9lbCBIYWxwZXJuDQo+IFJldmlldyByZXN1bHQ6IFJlYWR5DQo+IA0K
Li4uDQo+IERvY3VtZW50OiBkcmFmdC1pZXRmLWJtd2ctdmlydHVhbC1uZXQtPz8NCj4gUmV2aWV3
ZXI6IEpvZWwgSGFscGVybg0KPiBSZXZpZXcgRGF0ZTogMjAxNy0wMi0wNQ0KPiBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTAyLTE1DQo+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBm
b3IgYSB0ZWxlY2hhdA0KPiANCj4gU3VtbWFyeTogVGhpcyBkb2N1bWVudCBpcyByZWFkeSBmb3Ig
cHVibGljYXRpb24gYXMgYW4gSW5mb3JtYXRpb25hbA0KPiBSRkMuDQo+IA0KPiBNYWpvciBpc3N1
ZXM6DQo+IA0KPiBNaW5vciBpc3N1ZXM6DQo+ICAgICBUaGUgc2Vjb25kIGZpZ3VyZSBpbiBzZWN0
aW9uIDQuNCB0YWxrcyBhYm91dCB0aGUgdXNlIG9mIG11bHRpcGxlDQo+IDN4MyB0YWJsZXMsIGJ1
dCBhcHBlYXJzIHRvIHNob3cgdGhlIHVzZSBvZiBtdWx0aXBsZSA0eDQgdGFibGVzLiAgVGhpcw0K
PiByZWFkZXIgZm91bmQgaGltc2VsZiBjb25mdXNlZC4NCg0KW0FDTV0gDQpUaGUgIjN4MyBtYXRy
aXgiIHJlZmVycyB0byB0aGUgY2VsbHMgb2YgdGhlIHRhYmxlIHdoZXJlIA0KdXNlciBlbnRyaWVz
IGFwcGVhci4gVGhlIEhlYWRlciBSb3cgYW5kIEhlYWRlciBDb2x1bW4NCmFyZW4ndCBpbmNsdWRl
ZCBpbiB0aGUgM3gzIG1hdHJpeCwgYnV0IHRoZXkgZG8gbWFrZSB0aGUgDQp0YWJsZSBhcHBlYXIg
YXMgNHg0LCBhcyBpbiB0aGUgZmlyc3QgZmlndXJlIG9mIHNlYzQuNC4gDQpUaGUgSGVhZGluZ3Mg
ZGlzYXBwZWFyIGluIHRoZSBzZWNvbmQgZmlndXJlIA0KKGR1ZSB0byBzaXplIGNvbnN0cmFpbnRz
KSwgYnV0IHRoZSB0YWJsZXMgaW5jbHVkZQ0KdGhlIDN4MyBtYXRyaXggYXMgYmVmb3JlLg0KDQoN
Cj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPiANCg0K


From nobody Thu Feb 16 07:12:17 2017
Return-Path: <wcerveny@arbor.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB73129611; Thu, 16 Feb 2017 07:12:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thescout.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BO3JiFZTMmLg; Thu, 16 Feb 2017 07:12:13 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0120.outbound.protection.outlook.com [104.47.42.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A3061295E7; Thu, 16 Feb 2017 07:12:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thescout.onmicrosoft.com; s=selector1-arbor-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=x88YDvUF0Tld3dKztByp/eraGqkyjOHSK5UX3iU/NMI=; b=iGIE09nWIqA9lHTAGi8rec9d8YkXEvL8COTiEzYLb0fmkJ7Hn4sdSbi0/9Oe+8S9he2L8s8p4kXaPDXiGyqWNbQ5ELVui+gCBJHrjoqBHbm+UeWOyrod/h+oDCmEy8CGkHy/iHEM+IEBGxv7ipuf1hzehMtEOEvGPOuPld6kLmk=
Received: from CY1PR0101MB0780.prod.exchangelabs.com (10.160.138.154) by CY1PR0101MB0777.prod.exchangelabs.com (10.160.138.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Thu, 16 Feb 2017 15:12:10 +0000
Received: from CY1PR0101MB0780.prod.exchangelabs.com ([10.160.138.154]) by CY1PR0101MB0780.prod.exchangelabs.com ([10.160.138.154]) with mapi id 15.01.0888.030; Thu, 16 Feb 2017 15:12:09 +0000
From: "Cerveny, Bill" <wcerveny@arbor.net>
To: Jari Arkko <jari.arkko@piuha.net>, Francis Dupont <Francis.Dupont@fdupont.fr>
Thread-Topic: [Gen-art] review of draft-ietf-bmwg-ipv6-nd-04.txt
Thread-Index: AQHSdmDljU9se4PGGEyBegBXcq0gu6FruMgA///UuAA=
Date: Thu, 16 Feb 2017 15:12:09 +0000
Message-ID: <D2074128-83C3-4193-AF36-C524A348E232@arbor.net>
References: <201701241633.v0OGXSBE087413@givry.fdupont.fr> <6D68BE00-1E51-44C4-BDC1-B2EDD7CA8AE3@piuha.net>
In-Reply-To: <6D68BE00-1E51-44C4-BDC1-B2EDD7CA8AE3@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wcerveny@arbor.net; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [216.130.192.4]
x-ms-office365-filtering-correlation-id: b1a42bb2-260d-4dfe-fa71-08d4567e2da5
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:CY1PR0101MB0777; 
x-microsoft-exchange-diagnostics: 1; CY1PR0101MB0777; 7:8VVxQqYSZLrsQo2VjtYhJXw4aJiva6TskD7bNwgsN7EWcvkdOixstRh+e7PcpTkS3+JzjIXsf7dJEBlfxt1RdNsQE9YEjE3bxQmogR7Q9Z58KLeSXHeXfv7gY6xkKpJzvl68nzPvp0t2dSuVWAHrgzbQnyloML1RfJXGUwQyqvFNM/ZUCgYTvknRfYI3v+8ysY76/S+Kcy109EzzkGeohR7/zI5RyDJw13269m7vcS8BsVY0Wl5Y91YfEd+CNBZcwc8IV/fHOgtcTmkhIqi/sWYoV456qjkb6vAzDE0aq3UYnB/cZ6GM+HAQ4+nS+6EQOjXG33yrHlYZHChvk47qQA==
x-microsoft-antispam-prvs: <CY1PR0101MB07773D15909CC73781C55CADC05A0@CY1PR0101MB0777.prod.exchangelabs.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123560025)(20161123562025)(20161123564025)(20161123558025)(20161123555025)(6072148); SRVR:CY1PR0101MB0777; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0101MB0777; 
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(199003)(377454003)(189002)(24454002)(51914003)(305945005)(5660300001)(7736002)(101416001)(2950100002)(38730400002)(3280700002)(105586002)(8676002)(6512007)(25786008)(106356001)(33656002)(389900003)(66066001)(229853002)(6486002)(99286003)(77096006)(6436002)(106116001)(68736007)(6306002)(6506006)(54906002)(53546005)(81166006)(81156014)(76176999)(189998001)(230783001)(3660700001)(2900100001)(97736004)(92566002)(2906002)(102836003)(4326007)(3846002)(6246003)(53936002)(8936002)(83716003)(86362001)(82746002)(54356999)(36756003)(50986999)(122556002)(6116002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0101MB0777; H:CY1PR0101MB0780.prod.exchangelabs.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: arbor.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <93D33960F4DDEE49AF756B97680B7A22@prod.exchangelabs.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: arbor.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 15:12:09.5927 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 54f11205-d4aa-4809-bd36-0b542199c5b2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0101MB0777
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jkeBaIGV-GeZbiry3gN1VDKJwDk>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-bmwg-ipv6-nd.all@ietf.org" <draft-ietf-bmwg-ipv6-nd.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-bmwg-ipv6-nd-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:12:16 -0000

SGkgSmFyaQ0KDQpJ4oCZbGwgcmV2aWV3IHRoZSBjb21tZW50cyBhbmQgcmVzcG9uZCB0byB0aGVt
Lg0KDQpUaGFua3MsDQoNCkJpbGwgQ2VydmVueQ0KDQpPbiAyLzE2LzE3LCA3OjQ3IEFNLCAiSmFy
aSBBcmtrbyIgPGphcmkuYXJra29AcGl1aGEubmV0PiB3cm90ZToNCg0KICAgIFRoYW5rcyBmb3Ig
dGhlIGRldGFpbGVkIHJldmlldywgRnJhbmNpcyENCiAgICANCiAgICBBdXRob3JzIOKAlCBkaWQg
eW91IG1ha2UgYSBub3RlIG9mIHRoZSBjb21tZW50cz8gRGlkIG5vdCBzZWUgYSByZXNwb25zZeKA
pg0KICAgIA0KICAgIEphcmkNCiAgICANCiAgICBPbiAyNCBKYW4gMjAxNywgYXQgMTg6MzMsIEZy
YW5jaXMgRHVwb250IDxGcmFuY2lzLkR1cG9udEBmZHVwb250LmZyPiB3cm90ZToNCiAgICANCiAg
ICA+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRo
ZSBHZW5lcmFsIEFyZWENCiAgICA+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJ
RVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQNCiAgICA+IGJ5IHRoZSBJRVNHIGZvciB0aGUg
SUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQogICAgPiBsaWtl
IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQogICAgPiANCiAgICA+IEZvciBtb3JlIGlu
Zm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCiAgICA+IA0KICAgID4gPGh0dHBzOi8v
dHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQogICAgPiANCiAgICA+IERv
Y3VtZW50OiBkcmFmdC1pZXRmLWJtd2ctaXB2Ni1uZC0wNC50eHQNCiAgICA+IFJldmlld2VyOiBG
cmFuY2lzIER1cG9udA0KICAgID4gUmV2aWV3IERhdGU6IDIwMTcwMTE2DQogICAgPiBJRVRGIExD
IEVuZCBEYXRlOiAyMDE3MDEyMw0KICAgID4gSUVTRyBUZWxlY2hhdCBkYXRlOiB1bmtub3duDQog
ICAgPiANCiAgICA+IFN1bW1hcnk6IFJlYWR5IHdpdGggbml0cw0KICAgID4gDQogICAgPiBNYWpv
ciBpc3N1ZXM6IG5vbmUNCiAgICA+IA0KICAgID4gTWlub3IgaXNzdWVzOiB0aGUgdGl0bGUgKGFu
ZCB0aGUgQWJzdHJhY3QpIGlzIGEgYml0IG1pc2xlYWRpbmc6IGl0IGlzDQogICAgPiBub3QgdGhl
IGJlbmNobWFya2luZyBvZiB0aGUgTkQgcHJvdG9jb2wgd2hpY2ggaGFzIH4xMiBkaWZmZXJlbnQN
CiAgICA+IGZ1bmN0aW9ucyBidXQgdGhlIGJlbmNobWFya2luZyBvZiBhIHBhcnRpY3VsYXIgZnVu
Y3Rpb24gb24gYSByb3V0ZXIuDQogICAgPiBOb3cgaXQgaXMgdGhlIGNyaXRpY2FsIG9uZSBzbyBt
eSBjb25jZXJuIGlzIG1vcmUgdGhlIGRvY3VtZW50IGlzDQogICAgPiBsaW1pdGVkIHRvIG9ubHkg
dGhpcyBvbmUuLi4NCiAgICA+IA0KICAgID4gTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQogICAg
PiAtIFRvQyBwYWdlIDIgYW5kIDcgcGFnZSAxMjogQWNrbm93bGVkZ2VtZW50cyAtPiBBY2tub3ds
ZWRnbWVudHMNCiAgICA+IA0KICAgID4gLSAxIHBhZ2UgMjogdGhlIGxpbWl0IHRvIGEgcm91dGVy
IGV4cGxhaW5zIHdoeSB0aGUgdmVyYiBzZW5kIGlzDQogICAgPiAgcmVwbGFjZWQgYnkgZm9yd2Fy
ZC4uLiBhbmQgd2h5IHRoZXJlIGlzIG5vdGhpbmcgYWJvdXQgcmVkaXJlY3Rpb24NCiAgICA+IA0K
ICAgID4gLSAxIHBhZ2UgMjogZGV0ZXJtaW5lIHRoZSBJUHY2IG5leHQtaG9wJ3MgbGluay1sYXll
ciBhZGRyZXNzDQogICAgPiAgLT4gZGV0ZXJtaW5lIHRoZSBvdXRnb2luZyBpbnRlcmZhY2UgYW5k
IHRoZSBJUHY2IG5leHQtaG9wJ3MNCiAgICA+ICAgbGluay1sYXllciBhZGRyZXNzDQogICAgPiAN
CiAgICA+IC0gMi4yLjEgcGFnZSA1OiBldCBjZXRlcmEgLT4gZXRjDQogICAgPiANCiAgICA+IC0g
My4xLjIgcGFnZSA5ICh0d2ljZSkgYW5kIDMuMi4yIHBhZ2UgMTA7IHJlY2lldmVkIC0+IHJlY2Vp
dmVkDQogICAgPiANCiAgICA+IC0gMy4xLjIgcGFnZSA5OiBJTUhPIHlvdSBzaG91bGQgZGVmaW5l
IHRoZSAiaW5pdGlhbCIgdGVybSAoZm9yIGZpbmFsDQogICAgPiAgdGhlIG1lYW5pbmcgaXMgb2J2
aW91cykNCiAgICA+IA0KICAgID4gLSAzLjIuMSBwYWdlIDEwOiAoaS5lLixJUHY2IC0+IChpLmUu
LCBJUHY2DQogICAgPiANCiAgICA+IC0gMy4yLjIgcGFnZSAxMDogaW4gInBhY2tldHMtcmVjZWl2
ZWQgd2lsbCBlaXRoZXIgYmUNCiAgICA+ICAgZXF1YWwgdG8gemVybyBvciBwYWNrZXRzLXJlY2Vp
dmVkLiIgdGhlIGxhc3QgcmVjZWl2ZWQgLT4gc2VudC4NCiAgICA+IA0KICAgID4gUmVnYXJkcw0K
ICAgID4gDQogICAgPiBGcmFuY2lzLkR1cG9udEBmZHVwb250LmZyDQogICAgPiANCiAgICA+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgPiBHZW4t
YXJ0IG1haWxpbmcgbGlzdA0KICAgID4gR2VuLWFydEBpZXRmLm9yZw0KICAgID4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9nZW4tYXJ0DQogICAgDQogICAgDQoNCg==


From nobody Thu Feb 16 07:30:03 2017
Return-Path: <tim@ripe.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58CAD12943F; Thu, 16 Feb 2017 07:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FePiiU-q-ox3; Thu, 16 Feb 2017 07:30:01 -0800 (PST)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 493A6129509; Thu, 16 Feb 2017 07:30:01 -0800 (PST)
Received: from nene.ripe.net ([193.0.23.10]) by molamola.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1ceO0L-000Axr-EP; Thu, 16 Feb 2017 16:29:58 +0100
Received: from sslvpn.ripe.net ([193.0.20.230] helo=vpn-196.ripe.net) by nene.ripe.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1ceO0L-00064R-B3; Thu, 16 Feb 2017 16:29:57 +0100
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Tim Bruijnzeels <tim@ripe.net>
In-Reply-To: <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
Date: Thu, 16 Feb 2017 16:29:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <32AE4173-90C7-4E4D-A196-B3AD7F99E099@ripe.net>
References: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com> <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3124)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: ---------
X-RIPE-Spam-Report: Spam Total Points:   -9.4 points pts rule name              description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED            Passed through trusted hosts only via SMTP -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 784d7acfe6559f2a0b602ec6519a0719029fab8b99d9f797342878b1d9335ce9
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nlZUPNJlxbetFWnZOMqmI1PhzA4>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:30:02 -0000

Hi Jari, all,

Comment noted and should make it to an update when we process the other =
comments received!

Tim


> On 16 Feb 2017, at 12:58, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> Thanks for your review, Orit!
>=20
> (Authors, did you note the comment?)
>=20
> Jari
>=20


From nobody Thu Feb 16 07:34:44 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69050129659 for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2017 07:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNmDt6tim2zd for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2017 07:34:40 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 06B76129621 for <gen-art@ietf.org>; Thu, 16 Feb 2017 07:34:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8BF5C2CEB1; Thu, 16 Feb 2017 17:34:38 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ad056JZBkIf; Thu, 16 Feb 2017 17:34:38 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 01C2F2CCBA; Thu, 16 Feb 2017 17:34:37 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_45C97573-94F1-45AD-8EDE-75141CC625AD"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <32AE4173-90C7-4E4D-A196-B3AD7F99E099@ripe.net>
Date: Thu, 16 Feb 2017 17:34:37 +0200
Message-Id: <3081424C-540D-471A-BFC5-870F43B9D0C4@piuha.net>
References: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com> <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net> <32AE4173-90C7-4E4D-A196-B3AD7F99E099@ripe.net>
To: Tim Bruijnzeels <tim@ripe.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/rlkeEOpYZ7-Fu7QbLyXc4zhNH64>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:34:42 -0000

--Apple-Mail=_45C97573-94F1-45AD-8EDE-75141CC625AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks!

On 16 Feb 2017, at 17:29, Tim Bruijnzeels <tim@ripe.net> wrote:

> Hi Jari, all,
>=20
> Comment noted and should make it to an update when we process the =
other comments received!
>=20
> Tim
>=20
>=20
>> On 16 Feb 2017, at 12:58, Jari Arkko <jari.arkko@piuha.net> wrote:
>>=20
>> Thanks for your review, Orit!
>>=20
>> (Authors, did you note the comment?)
>>=20
>> Jari
>>=20
>=20


--Apple-Mail=_45C97573-94F1-45AD-8EDE-75141CC625AD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYpcaNAAoJEM80gCTQU46quzAQAMCrkPV/IexQ8cJr66aiVevb
2wuLutMyJ4PP/2Fh6cMHUNkaa9vn7dWcuhbQuj09Sr4vUZzfISX5EGgd5WQtQzVa
6SiXNCdiJX+xAOXnYDrhmi07eoqUaFjDyYI1BwNM4fmF/kxPhOA97I5qG9inNpjD
HrgIJAQ4hhPYan7FNSbw8lnkUzkiMExgEefaWdZrKEZEr9JdCCSGBeZyVv/Hv6aq
KgKV44J8reUzTefVsIbb6YT8zNFUHSxbQznXy1O3aZsxRMdNgrSq6MOUf+JHFTqx
KQ/kbaNReBfiaQRMpXjpyNWN1y7eCjocoDAj4C0MIHFQ1mFpmZByy3A3KbR7dUe5
6gauXlnAmXuVhJrMc0fD4FzWv9opx8xRPjva3KTsgLrLBtSArqggZPCbMWTNdPKC
IwERToAeCm4Rl0sM8uTZRbWPxPS/Mv85EF2cOB6qmwTOv6DrbyqK1ppeFMgGvOM5
TlBnDWOv6c+b+VTA8jzTJv+qdxo4sjAAspFZxp7TocZJqs4T1lyuVGEykd2XRqSt
7h2mRk93DSmXCd0HZdXZiT6k/VnntIHodPuiQmwzc8OIg3no7oYY49DGwOnRbSPM
GmoD2vJB25weRWgvi5MTY1tnrKZmr0otg8USYwmL7tXJ0m3sMhIt7meiGrWkdfTx
yIBsmljKExpwPv3kUmVR
=BE+w
-----END PGP SIGNATURE-----

--Apple-Mail=_45C97573-94F1-45AD-8EDE-75141CC625AD--


From nobody Thu Feb 16 08:00:09 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4887A129D66; Thu, 16 Feb 2017 08:00:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENByfhJsiiYm; Thu, 16 Feb 2017 08:00:02 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 104DE12944C; Thu, 16 Feb 2017 08:00:02 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id v77so3813303wmv.0; Thu, 16 Feb 2017 08:00:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=BOhvQRcmRYmHrD6F8dcTiu8EKCno78mChnG5Ca8PCvQ=; b=hoY+GrEg+VmvRzrXKj5m3/M9vzMwu+PM0VuX9tASZtKVHbSwvBCSnPpvGQ9hGY74pU D4ZRwx4ONrJ60Z6COcwQMF6uwQlL5Za+Uf3+HbVlyivtjiYeryTyxx6+AV3kKccKiWMR RPbhJ3V7nClGRNR+jJ8U+z/Lw0ofehyHkanEIOW9FmuUz8hvYPD97pxryM0bntwpBnkf uHN84R2oM7vgBYq08C+AUxh09ImnAuBQkN+lLIh4griTpdcTrDEm/tZWjYx1SWuyHGj5 xE0qNgG1HtA70LXPa5u5D0cYYTKYhzNrcMj077poq0caTlCgezLWMbvOrpBaCLMi+oa2 zQPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BOhvQRcmRYmHrD6F8dcTiu8EKCno78mChnG5Ca8PCvQ=; b=HPFs0d6BFbNgYMMmxdXnsiaczyxsVGaP+72jo15dzOLtci6ERkqOM8jDtUBSzqMaIH XgtPPH0XHb4sqL34yaKvKXVA7c16vcaIIcQRa6mtI2ayQKNEwhOpUv0xu0RhlkzkAH0Q BBei4kGYZOnRpzpP1AuiuzaqGlm8bhpoRewOkRmg3V9TTH+XRqlZnydyAJeisEWuEGfU qMSl/2dZjmcFvrbQ2clJJCUoU9wYMXNzWjZStZ0BC+LCJoizw3PFf2NTuPySD94csr7e Cl3bQUVEeFcu+KrdHTLmlLgzdf/KSg6HTALfgRgaMRaCOJZEYGBnf29xyxtNMh/0dTXN NkHg==
X-Gm-Message-State: AMke39lSjTTaoZCcmEe82CMJCLS1d2aBWGlQv3tHTg7QOJDLpM+l9D40+fXFveoH3T7Hng==
X-Received: by 10.28.142.73 with SMTP id q70mr3225527wmd.3.1487260800492; Thu, 16 Feb 2017 08:00:00 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 65sm9442521wri.53.2017.02.16.07.59.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 07:59:59 -0800 (PST)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Date: Thu, 16 Feb 2017 15:59:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/lGiNF51qp0XSo1bCvTZKXEHTbIw>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 16:00:08 -0000

On 14/02/2017 23:00, Templin, Fred L wrote:
> Unless there is operational assurance of
> some size X>1280, however, tunnels have to use fragmentation to
> guarantee that - at a minimum - packets up to 1280 will get through.

In that case there really needs to be a note about MPLS.

You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.

Stewart


From nobody Thu Feb 16 10:12:56 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC6A127077; Thu, 16 Feb 2017 10:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvaY9NeFSzw8; Thu, 16 Feb 2017 10:12:52 -0800 (PST)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 241FB1294F8; Thu, 16 Feb 2017 10:12:51 -0800 (PST)
Received: by mail-ot0-x229.google.com with SMTP id 45so16562607otd.2; Thu, 16 Feb 2017 10:12:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9zdbH0lzB0xr4x+0E7Y9fLhoxqODMxajQ/9ZOJFAhlg=; b=bbrtje2YKCE59y+SR9isQjCQ+pnA5CAvCuqhOX+QfLK8tAb5N7895UrpGpkF8SQa03 rNdKYLjY3TU0DODgaRMtwdcI+yGaiEXKr593PWtyupvJIwtfhoS2s+t7SItMki9QDWPb qp7XvZij7vRW8+PVeTQyX+Xq7JZnfmUpmGaFRMUntDBIRL443sT08KPfG88S/9OMhdkz 8fcMElRc1Va336wNYNyp5Y5zzRLJ0NC87OOMrJTM+1Yp+WDCv+2rUhCAYdHnwi/Tsalu OToaQJL3saVBGnLak8FU/XPiyUWFFsYccTLjkXkQg1ZE5ZwBubA0YKTBnJQ+vkI0jaUU p2sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9zdbH0lzB0xr4x+0E7Y9fLhoxqODMxajQ/9ZOJFAhlg=; b=jmioVtnX/M0jftIRf7V3+Q67QAtiPdY23gGItceIqaeivG4XG8DwHmely9IZIAbBcl b2y0uxrP0xbNQWqq7zA906SVvNRRAh46J1IJee+zCrwBUahMNCmRy/nHSaPss0sEyvbZ qAb7Jar/e3NWRNACH9eeM6Cx9saaNu+GWKbMzpK4LmFJMsDIhazG1SfahKPq9tzugLST rhdLz0B6rXyU601RmVcV6zcbBK4EinlhQDYzP7YDUR3Vsn5UjrAib6nJaKFAv+dTcEY8 yJDIo1OwgGQqUzf3HMOC9aWZHHWNZgyp7/D14bIghQiUglyqYqUEQTxofasCMgHqp6fc UFWA==
X-Gm-Message-State: AMke39mlFicM4T0Gihsktmayisgs2xXdvUWJqwRs1MHV6oOKTWBdlOPB4NSAdDSPh5F0rp+FH+8uGcReSAWvpw==
X-Received: by 10.157.8.42 with SMTP id 39mr1799724oty.249.1487268770557; Thu, 16 Feb 2017 10:12:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.159.42 with HTTP; Thu, 16 Feb 2017 10:12:30 -0800 (PST)
In-Reply-To: <baf6ae46-3d87-4930-9d9f-1e7febfb07e9@gmail.com>
References: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com> <baf6ae46-3d87-4930-9d9f-1e7febfb07e9@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 16 Feb 2017 13:12:30 -0500
Message-ID: <CAA=duU0jV=dTKdwm3+j4s24Pk7-5qvtU2_64Lih==kUs47cZ7g@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary=94eb2c048a90c1371f0548a9be09
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/uHOYuCGWj7NTJH10KZQ-fovm0Oo>
Cc: draft-ietf-pals-mpls-tp-dual-homing-protection.all@ietf.org, General Area Review Team <gen-art@ietf.org>, "BRUNGARD,  DEBORAH A \(ATTLABS\)" <db3546@att.com>
Subject: Re: [Gen-art] Review of draft-ietf-pals-mpls-tp-dual-homing-protection-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:12:54 -0000

--94eb2c048a90c1371f0548a9be09
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Russ,

This isn=E2=80=99t normal practice, but based on your comment, the IPR decl=
aration
has been reissued explicitly for the WG draft.

Cheers,
Andy


On Wed, Feb 8, 2017 at 1:53 PM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> Hi Russ
>
> Thank you for the review.
>
> I would like to respond to one point:
>
>
> Notes:
>>
>> I see that draft-cheng-pwe3-mpls-tp-dual-homing-protection the
>> earlier
>> Internet-Draft file name for this document.  An IPR declaration was
>> issued against that earlier name.  The shepherd write-up indicates
>> that
>> "The WG were not concerned about the IPR disclosure." However, it is
>> unclear to me whether we should ask for the IPR declaration to be
>> issued
>> against the current Internet-Draft file name.
>>
>>
> The authors all responded including of course the author from the company
> that
> filed the IPR. All indicated that no additional IPR was known about.
>
> The IPR disclosure shows up in datatracker.
>
> We do not normally chase companies to update their IPR disclosures, as
> documents progress, and indeed if we chase them to do this update we need
> to chase them shortly for a further one as the draft becomes an RFC.
>
> Since you pointed it out we have asked the author to ask his patent dept
> to do the update, but I hope that this does not become an IETF policy
> making it even harder to pass the IPR checks that we put in place in RTG.
>
> Thanks
>
> Stewart
>
>
>

--94eb2c048a90c1371f0548a9be09
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Russ,<div><br></div><div>This isn=E2=80=99t normal practic=
e, but based on your comment, the IPR declaration has been reissued explici=
tly for the WG draft.</div><div><br></div><div>Cheers,</div><div>Andy</div>=
<div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 8, 2017 at 1:53 PM, Stewart Bryant <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:stewart.bryant@gmail.com" target=3D"_blank">stewart.bryant@=
gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Russ<=
br>
<br>
Thank you for the review.<br>
<br>
I would like to respond to one point:<span class=3D""><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Notes:<br>
<br>
I see that draft-cheng-pwe3-mpls-tp-dual-<wbr>homing-protection the<br>
earlier<br>
Internet-Draft file name for this document.=C2=A0 An IPR declaration was<br=
>
issued against that earlier name.=C2=A0 The shepherd write-up indicates<br>
that<br>
&quot;The WG were not concerned about the IPR disclosure.&quot; However, it=
 is<br>
unclear to me whether we should ask for the IPR declaration to be<br>
issued<br>
against the current Internet-Draft file name.<br>
<br>
</blockquote>
<br></span>
The authors all responded including of course the author from the company t=
hat<br>
filed the IPR. All indicated that no additional IPR was known about.<br>
<br>
The IPR disclosure shows up in datatracker.<br>
<br>
We do not normally chase companies to update their IPR disclosures, as<br>
documents progress, and indeed if we chase them to do this update we need<b=
r>
to chase them shortly for a further one as the draft becomes an RFC.<br>
<br>
Since you pointed it out we have asked the author to ask his patent dept<br=
>
to do the update, but I hope that this does not become an IETF policy<br>
making it even harder to pass the IPR checks that we put in place in RTG.<b=
r>
<br>
Thanks<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Stewart<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--94eb2c048a90c1371f0548a9be09--


From nobody Thu Feb 16 10:50:42 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CED91294F8; Thu, 16 Feb 2017 10:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAWj4OS1eig9; Thu, 16 Feb 2017 10:50:39 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1BD4127077; Thu, 16 Feb 2017 10:50:39 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GIo0Ch014046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 10:50:00 -0800 (PST)
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
Date: Thu, 16 Feb 2017 10:49:58 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KRkbGj3ww7Mx3Ib0EAzURnMtMQ8>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:50:41 -0000

On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>
>
> On 14/02/2017 23:00, Templin, Fred L wrote:
>> Unless there is operational assurance of
>> some size X>1280, however, tunnels have to use fragmentation to
>> guarantee that - at a minimum - packets up to 1280 will get through.
>
> In that case there really needs to be a note about MPLS.

IMO, this doc shouldn't be discussing tunneling as any different from
any other link.

> You can fragment into an IP tunnel, but not an MPLS tunnel, because
> you cannot fragment the payload as you can in IPv4 and you cannot
> fragment MPLS.

There's no such thing as an "MPLS tunnel"; at best, it's "MPLS over X",
e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
while it can't support fragmentation it would never need it either. It
would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
needed fragmentation.  If that can't be supported, then the addition of
MPLS would just reduce the effective MTU of the MPLS-over-X link.

Joe


From nobody Thu Feb 16 11:59:23 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB6C8128E18; Thu, 16 Feb 2017 11:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-1xR3y5oRJE; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FC6512941A; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 5so2784828pgj.0; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=X1cwIjUWucI+Lm+4BgQ3TByDEhr7m1fkd2WkaXLhYIQ=; b=AkwYn8LKsSaiO5Ty8DO6eGNIf5O9pkzLFnAYMkmHdvEps5uAF8xCjLSP2Sj7Bp58Fr 3rC6Q2MOlvNg8PJaU/Sx/dox11ZH/cY2POgjiE7ptV8uBIy+rNtgTPdKUddZ8Cj7gKMR I2dyA24iaFPnDKR7nw/U/JoMjcVH1326IIdgdGmHL3OWg8vxlc0Jc7LOVTCTwf3sAlnv 5DezQiaFxSBkubZhMHeX3arvkzwFdCoPtK7BJejruSkiWLWZIDRU4z+60MwdFeULJnR1 VEENyhxyjiCZ2mXS2OVd+QGBhhIipFwl0O7vfSWN6310qVZdCYPomG1dsAxXm28gHBo3 sc7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=X1cwIjUWucI+Lm+4BgQ3TByDEhr7m1fkd2WkaXLhYIQ=; b=tyGgviY2CNzzafkD9TMfKWkRzBU94q67pEPLLS4gzLWf/7gYiOkTRVVKVwSFRq4ntJ yNiB8T+wXgvkGZ7f50qlFGUqDR5YjaOHyKs+S2H4eGnXpgCkfUbU6MXQXAaRti5FwxH/ F84T8gzB/lR2dYFTxxIRjcCAE+X4qUvV5S7ZMFAXuBa+BBRt1N3RnKukfOE/8TZhxmdg fbwCwq7kD4uzLG5q36EMQq0ADApil9joT2/FFxzDSVPmEykxnSr2lPwMixSy5MlxdPvf v650dnr4L9QIzrfumQcC5hgq+0y8fxdox8dJDzgaLmpyiAVSFVIUn9UPDkrCOd9fuwqu pWqA==
X-Gm-Message-State: AMke39lwl5mKP22P5/oIFspsmfT4RaRxKo1tZJWelmbtBnVbmXlBcXDKdg1CUCYE54lzHw==
X-Received: by 10.98.70.12 with SMTP id t12mr4734944pfa.47.1487275151951; Thu, 16 Feb 2017 11:59:11 -0800 (PST)
Received: from ?IPv6:2406:e007:68c5:1:28cc:dc4c:9703:6781? ([2406:e007:68c5:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id e129sm15210411pfe.8.2017.02.16.11.59.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 11:59:11 -0800 (PST)
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
Date: Fri, 17 Feb 2017 08:59:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/a7NQmGQRxPDOt7n7PGx0Q-cdM1Y>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:59:14 -0000

On 17/02/2017 04:59, Stewart Bryant wrote:
> 
> 
> On 14/02/2017 23:00, Templin, Fred L wrote:
>> Unless there is operational assurance of
>> some size X>1280, however, tunnels have to use fragmentation to
>> guarantee that - at a minimum - packets up to 1280 will get through.
> 
> In that case there really needs to be a note about MPLS.
> 
> You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
> cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.

I'm confused. A tunnel end point that accepts IPv6 packets MUST accept packets
of 1280 bytes (or shorter) and MUST emit them. How it gets them through the
tunnel is irrelevant - if it's an ATM tunnel it has to chop them into 48 byte
fragments and re-assemble them at the other end - if it's an avian carrier tunnel
it might have to use several pigeons per packet*. None of this matters to the IPv6
nodes concerned; the physical MTU of the tunnel technology is irrelevant except
to the tunnel end points.

   Brian

*In RFC 6214, we didn't consider this, but we should have.


From nobody Thu Feb 16 13:10:51 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C781296DF; Thu, 16 Feb 2017 13:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrWqTj9udy46; Thu, 16 Feb 2017 13:10:31 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22B001296A6; Thu, 16 Feb 2017 13:10:31 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GL9fQK017392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 13:09:42 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <9f298dea-88c9-3784-c87e-d33384fe8308@isi.edu>
Date: Thu, 16 Feb 2017 13:09:40 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/L7kZZNq5x6x-ktgpChkk_CvZbRs>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:10:35 -0000

On 2/16/2017 11:59 AM, Brian E Carpenter wrote:
> On 17/02/2017 04:59, Stewart Bryant wrote:
>>
>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>> Unless there is operational assurance of
>>> some size X>1280, however, tunnels have to use fragmentation to
>>> guarantee that - at a minimum - packets up to 1280 will get through.
>> In that case there really needs to be a note about MPLS.
>>
>> You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
>> cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.
> I'm confused. A tunnel end point that accepts IPv6 packets MUST accept packets
> of 1280 bytes (or shorter) and MUST emit them. How it gets them through the
> tunnel is irrelevant - if it's an ATM tunnel it has to chop them into 48 byte
> fragments and re-assemble them at the other end - if it's an avian carrier tunnel
> it might have to use several pigeons per packet*. None of this matters to the IPv6
> nodes concerned; the physical MTU of the tunnel technology is irrelevant except
> to the tunnel end points.
There are too many systems that try to optimize the link MTU to
represent the size of the payload of the link source, rather than the
reassembly limit of the link receiver.

It's trying to make PMTUD work multiple layers down rather than stopping
at the IP layer (which I think is where it should stop).

Joe


From nobody Thu Feb 16 13:29:20 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5A71296E9; Thu, 16 Feb 2017 13:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCYJ35XzrAJz; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D423129541; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id r18so4991354wmd.3; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=J1iz2LwaFavlvtuubgS3GA1kYV5QHMrJzw/sHBW46M0=; b=tlgU1Q9TsgAl2F1UfRetAlDfvJ0b9eGU64N4Q3nyLRgok2qURIYFZJKPnTKcLVW2VN kJkNpMmtQzfEfkQFXmGjAFGJHBUXG7ezujTyD7/Pl3o8ilmETGeTXxyB3jQpX938RStM rJZNmYL9ajHktG4+vV9oHmbqr14CPN4EFak4hvfKH6WpC7rF5m5h3QNBykwgDKoQqGcw Gxze/5130JjjPw5QO4g68Qvem8gGAU63e6VT9n/uqRgxC4+hRf4sWsvP9KkGIvFBPgxb HCWX2tQYKQIlrWmotcTelGfAhWQlPqq+W1rO2O6qbnZmKeLpZGQFHOrwz82SA4tqEAlX ovbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=J1iz2LwaFavlvtuubgS3GA1kYV5QHMrJzw/sHBW46M0=; b=FWtB+SYXRCG/joB6R5dZv3j0B0xsb089kCYmH872Gv/1O3N+g/Qx2+IWGmpzmgV7Ld 0/iV6Ga4+3NiQ+3HCXo+6/ORgJkPdqrIiw2SSXXWFoVzsGxQx35wo9bLJNiQVHzx6j4P FsKJLNtX2+6n1AH3a3DDYlVr8dFFeddUYhhWJFVLog/HjiH3nXU4BWJV1CzDp6viZNJW G8bkfM64xRLgwo5lPoPOce3xbN/FfM76esQt21Gt7k3AnjNWuv7IYzilMUYV3lLbsqC5 SQpZFjBN4nwVSAq7F2i4/+CfD0BsZGBUqELbfGb6ndZsd7K86w+Uz7vyft0/60vCWIvT 1n6w==
X-Gm-Message-State: AMke39kdyrRU2wvcNNlH860ZKj4uZJS2gKnh0jNNwzVhE+UFSu93Pvll5aH89JPHS0Iygw==
X-Received: by 10.28.11.83 with SMTP id 80mr4280124wml.71.1487280543693; Thu, 16 Feb 2017 13:29:03 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id d29sm1702337wmi.19.2017.02.16.13.29.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 13:29:03 -0800 (PST)
To: Joe Touch <touch@isi.edu>, "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
Date: Thu, 16 Feb 2017 21:29:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/3Sm3VpK9SPboHg36gdb2N-L8c9g>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:29:08 -0000

On 16/02/2017 18:49, Joe Touch wrote:
>
> On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>>
>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>> Unless there is operational assurance of
>>> some size X>1280, however, tunnels have to use fragmentation to
>>> guarantee that - at a minimum - packets up to 1280 will get through.
>> In that case there really needs to be a note about MPLS.
> IMO, this doc shouldn't be discussing tunneling as any different from
> any other link.
>
>> You can fragment into an IP tunnel, but not an MPLS tunnel, because
>> you cannot fragment the payload as you can in IPv4 and you cannot
>> fragment MPLS.
> There's no such thing as an "MPLS tunnel";

In the MPLS world an "MPLS tunnel" is a common name for an MPLS LSP that
is used to carry some payload such as IP.

> at best, it's "MPLS over X",
> e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
> while it can't support fragmentation it would never need it either. It
> would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
> needed fragmentation.  If that can't be supported, then the addition of
> MPLS would just reduce the effective MTU of the MPLS-over-X link.

It was of course IPv6 over MPLS that concerned me.

S

>
> Joe


From nobody Thu Feb 16 13:43:16 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B418129629; Thu, 16 Feb 2017 13:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3zi_UkbCitB; Thu, 16 Feb 2017 13:43:13 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ADF512967D; Thu, 16 Feb 2017 13:43:13 -0800 (PST)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v1GLggFI007094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 13:42:42 -0800 (PST)
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu> <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <f2e2972e-04ca-ca9c-91e1-b12f816c9380@isi.edu>
Date: Thu, 16 Feb 2017 13:42:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ddwCgR2ZP-hyoumqjAHzvKmtBiw>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:43:14 -0000

On 2/16/2017 1:29 PM, Stewart Bryant wrote:
>
>
> On 16/02/2017 18:49, Joe Touch wrote:
>>
>> On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>>>
>>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>>> Unless there is operational assurance of
>>>> some size X>1280, however, tunnels have to use fragmentation to
>>>> guarantee that - at a minimum - packets up to 1280 will get through.
>>> In that case there really needs to be a note about MPLS.
>> IMO, this doc shouldn't be discussing tunneling as any different from
>> any other link.
>>
>>> You can fragment into an IP tunnel, but not an MPLS tunnel, because
>>> you cannot fragment the payload as you can in IPv4 and you cannot
>>> fragment MPLS.
>> There's no such thing as an "MPLS tunnel";
>
> In the MPLS world an "MPLS tunnel" is a common name for an MPLS LSP that
> is used to carry some payload such as IP.

MPLS just adds the label tags; there's no length field.  It's only a
tunnel when it goes over some other encapsulation layer, e.g., IP or
Ethernet.

>
>> at best, it's "MPLS over X",
>> e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
>> while it can't support fragmentation it would never need it either. It
>> would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
>> needed fragmentation.  If that can't be supported, then the addition of
>> MPLS would just reduce the effective MTU of the MPLS-over-X link.
>
> It was of course IPv6 over MPLS that concerned me.

IPv6 over MPLS isn't yet a tunnel. It would be IPv6 over MPLS over IPv6,
presumably (IPv6 over IPv4 isn't guaranteed to work because IPv4 EMTU_R
is only 576, and for an IPv6 tunnel it would be required to be at least
1280+encaps).

An IPv6 packet can traverse an IPv6 over MPLS over Ethernet tunnel (with
a 1500B payload) as long as the MPLS headers are smaller than 1500-1280
bytes.

An IPv6 packet can traverse an IPv6 over MPLS over IPv6 tunnel as long
as the MPLS + added IPv6 headers are smaller than 1500-1280 bytes.
However, if the arriving (transit) packet is larger than
1280-MPLS-IPv6ecaps, the MPLS tunnel ingress would need to do source
fragmentation inside the tunnel (with the egress doing reassembly).

Again, all these cases are discussed in draft-ietf-intarea-tunnels but
none have relevance IMO to this doc.

Joe


From nobody Thu Feb 16 18:31:17 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2C91297AA; Thu, 16 Feb 2017 18:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzeFO1MENlrK; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD65128B44; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id k4so3649026otc.0; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=el0TV7Fss4KtkJo20COfFrqTMTOg84hSyPjho2dru5U=; b=c3zFCRvjpRt5Tzx3XaGYQzlC4njOiC/2ccjbc5cGKLm0RydVod9Kr1fYqx4V1+hPXT dwwvEN7B6QLELCiFpIKJR+Xpi1pV3D7n3fJKFpRKek4cIJXi7IogRJgeN1+rs3S4C8Sh hkPwEo8IMom52W7wrkvfH6a0Pe3+IwKwZoF8paNryASY1moZKgK/svPYYtf5pFThwrDR KinFOL4W3Q+140fsD6pnDYTzht+bEvj4BRL3ZCpI1o+LaUKaKu2C0gGPgXZZja7UHv60 FjRJwt7V+8sr9slj40C91y4/8E4tduitWZsbR4jDE4+Wnpiw3VeSs9+qbZ/vym/ib6B/ LMzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=el0TV7Fss4KtkJo20COfFrqTMTOg84hSyPjho2dru5U=; b=uLf1M2aU2CJbjb99o9y1blSKLjBF1W4JRhez/0tRm2S2SXdFpTMelX2jkMIq6zZg4f Q6KT2DXIt5WHH9kAqX7x9zk3jwaIN1wVyRkDfld2l3HPTJCynTdWieUYzgO0MtjerREX 7bgoDGUhmrruKEx+6qXnol6oQVKz55cz2tbtMYEBqaXGKUe+Qd3xwLJ/k/Ra2EKNGmmD P6dAXLhEiNljVeWsm62jTtN18y7vV3/rMMS6Kb/UjS+z/0n5NyXwOLwU8TJVE8UL6PQ9 x/XMtueLSs9vh7CVfwphTOFbFVYmrE01T6RIn9drCpQbUv2yjKyxkSb8j5d53HHiyYzP /uEg==
X-Gm-Message-State: AMke39lOGkpWMLAIiyqHj/qWB3fTLLB6Pbby5uDuPDCd0Bcqsjo+8yy3AgaKvYjrAfYZsLr4nBa3i3//nQlHDA==
X-Received: by 10.157.15.154 with SMTP id d26mr402068otd.186.1487298670854; Thu, 16 Feb 2017 18:31:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Thu, 16 Feb 2017 18:30:30 -0800 (PST)
In-Reply-To: <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
From: tianxiang li <peter416733@gmail.com>
Date: Fri, 17 Feb 2017 10:30:30 +0800
Message-ID: <CAFx+hEOMFF=bU3BUQfcbCAARs_0OyR9HuoAmjs5BLh29QFpEXg@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a113cf206f386ab0548b0b439
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9ou15f4EKEZa7HgJ4pYlVUbTHfs>
Cc: dhcwg <dhcwg@ietf.org>, gen-art@ietf.org, Roni Even <roni.even@mail01.huawei.com>, ietf@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 02:31:12 -0000

--001a113cf206f386ab0548b0b439
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Jari,

Thank you for the support, and thanks to Roni as well as all the other kind
reviewers of this document.
We would update a new version of the document soon and cover the points
raised during last call.

Thanks and best regards,
Tianxiang

2017-02-16 20:04 GMT+08:00 Jari Arkko <jari.arkko@piuha.net>:

> Roni: thanks for your detailed review. I also appreciate
> the responses and changes by you Tianxiang. I have
> balloted no-objection for this document for today=E2=80=99s
> IESG telechat, and expect that the discussed changes
> will find themselves into a new document version at
> some point.
>
> Jari
>
>

--001a113cf206f386ab0548b0b439
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Jari,<div><br></div><div>Thank you for the support, and=
 thanks to Roni as well as all the other kind reviewers of this document.</=
div><div>We would update a new version of the document soon and cover the p=
oints raised during last call.=C2=A0</div><div><br></div><div>Thanks and be=
st regards,</div><div>Tianxiang</div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">2017-02-16 20:04 GMT+08:00 Jari Arkko <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari=
.arkko@piuha.net</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Roni: th=
anks for your detailed review. I also appreciate<br>
the responses and changes by you Tianxiang. I have<br>
balloted no-objection for this document for today=E2=80=99s<br>
IESG telechat, and expect that the discussed changes<br>
will find themselves into a new document version at<br>
some point.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div>

--001a113cf206f386ab0548b0b439--


From nobody Thu Feb 16 19:37:59 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 317231298C4; Thu, 16 Feb 2017 19:37:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Joel Halpern" <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 19:37:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jEq5yYDAqv7lXr0XwaYPfj-AB9M>
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 03:37:58 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-stateful-pce-??
Reviewer: Joel Halpern
Review Date: 2017-02-16
IETF LC End Date: 2017-02-28
IESG Telechat date: 2017-03-16

Summary:

Major issues:

Minor issues:
   At the end of section 5.4, the text talks about a PCE accepting
status updates even if the  stateful capability has not been
negotiated.  Which is fine.  But as written, the text seems to say
that doing so means that the PCE will be able to "build and maintain
an up to date view of the state of the PCC's LSPs".  However, if the
capability has not been negotiated, I do not see how the PCE can count
on getting full and timely state reports.  Trying to infer why a PCC
is sending such a report in the absence of the agreement seems
problematic.

    This comment may be a misunderstanding or mis-expectation on my
part.  I would have expected one of the ways o using an active PCE is
to have the PCE decide (under suitable circumstances) that an LSP is
needed between two PCCs.  As far as I can tell, the text in section
5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
Update Request (in a PCUpd message) for an LSP that has been delegated
to it.  At that point I thought that a PCC could delegate a block of
unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states
that for each delegation, the PCC must request an initial path.  That
seems to prohibit delegating a block of LSPs for future updates.  Is
the intention to prohibit the driving of LSP creation from the PCE?

    I have looked but I can not find the text explaining the
significance and use of the Symbolic path name.  It is mandated by the
draft.  There seems to be an implicit assumption taht it is needed by
the PCE.  If the explanation of how or why it is needed is not
present, it should be.

Nits/editorial comments: 
    Should the text on the S bit in section 7.3 (the LSP Object
definition) note that it should be set to 0 on all messages sent by
the PCE?  Should that also be stated for the R bit?  And the O bits?

  Section 9.2 seems very odd.  It states that the IETF "SHOULD" do
some additional work.  I understand why teh work is needed.  But this
does not seem to match the RFC 2119 meaning of SHOULD as it does not
apply to eitehr the implementor or the implementation.



From nobody Thu Feb 16 20:36:18 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67F512997D; Thu, 16 Feb 2017 20:36:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbyT7AwNwi3T; Thu, 16 Feb 2017 20:36:14 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC8BA1294A3; Thu, 16 Feb 2017 20:36:13 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGQ31933; Fri, 17 Feb 2017 04:36:11 +0000 (GMT)
Received: from BLREML702-CAH.china.huawei.com (10.20.4.171) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 17 Feb 2017 04:36:10 +0000
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml702-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Fri, 17 Feb 2017 10:05:57 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Joel Halpern <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM9gtp/PSv/bkEq3uaeNA/BLdaFsmcuQ
Date: Fri, 17 Feb 2017 04:35:56 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.40.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.58A67DBB.0124, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: bc9b1df1e95a95ef020d370418be5c18
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1ugdmxv5gNHmBpIm3_brW_WRDNg>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 04:36:17 -0000

Hi Joel,=20

Regarding your comment -=20

> Is the intention to prohibit the driving
> of LSP creation from the PCE?

This capability is described in -=20
https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07 (document e=
xpired recently, authors should refresh it)

Thanks,
Dhruv=20

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
> Sent: 17 February 2017 09:08
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
>=20
> Reviewer: Joel Halpern
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-pce-stateful-pce-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-16
> IETF LC End Date: 2017-02-28
> IESG Telechat date: 2017-03-16
>=20
> Summary:
>=20
> Major issues:
>=20
> Minor issues:
>    At the end of section 5.4, the text talks about a PCE accepting status
> updates even if the  stateful capability has not been negotiated.  Which =
is
> fine.  But as written, the text seems to say that doing so means that the
> PCE will be able to "build and maintain an up to date view of the state o=
f
> the PCC's LSPs".  However, if the capability has not been negotiated, I d=
o
> not see how the PCE can count on getting full and timely state reports.  =
Trying
> to infer why a PCC is sending such a report in the absence of the agreeme=
nt
> seems problematic.
>=20
>     This comment may be a misunderstanding or mis-expectation on my part.
> I would have expected one of the ways o using an active PCE is to have th=
e
> PCE decide (under suitable circumstances) that an LSP is needed between t=
wo
> PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Upd=
ate
> Request (in a PCUpd message) for an LSP that has been delegated to it.  A=
t
> that point I thought that a PCC could delegate a block of unsetup LSPs to
> the PCE.  But then looking at 5.8.2, the text states that for each delega=
tion,
> the PCC must request an initial path.  That seems to prohibit delegating =
a
> block of LSPs for future updates.  Is the intention to prohibit the drivi=
ng
> of LSP creation from the PCE?
>=20
>     I have looked but I can not find the text explaining the significance
> and use of the Symbolic path name.  It is mandated by the draft.  There s=
eems
> to be an implicit assumption taht it is needed by the PCE.  If the explan=
ation
> of how or why it is needed is not present, it should be.
>=20
> Nits/editorial comments:
>     Should the text on the S bit in section 7.3 (the LSP Object
> definition) note that it should be set to 0 on all messages sent by the P=
CE?
> Should that also be stated for the R bit?  And the O bits?
>=20
>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some
> additional work.  I understand why teh work is needed.  But this does not
> seem to match the RFC 2119 meaning of SHOULD as it does not apply to eite=
hr
> the implementor or the implementation.
>=20
>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


From nobody Thu Feb 16 20:42:38 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679B712956D; Thu, 16 Feb 2017 20:42:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lL-5ki5O1xCG; Thu, 16 Feb 2017 20:42:35 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F0E5129540; Thu, 16 Feb 2017 20:42:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 33E50A21ADA; Thu, 16 Feb 2017 20:42:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487306552; bh=5j6BM0KdaO7SJ1Ky9DrpJN3RMTl02OaEPIy9i8bv8ZM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=KR4Y7dyzbptUnhOwAYsI2M5G3pyPEsQIX2Okki/bzkhoPZLbMLZi2Lwj8z8+MXGvP Jl8tX65JnSxiwwUYsRU03ErDeykcaqgaJy5qOkH1r8z5JW7LABnLm5gurUlYbUOW8l lrM4vj8cNRHte7IgpwM8qy9S3z6Ul1UgGD+tI61U=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 6BA2A1C02F3; Thu, 16 Feb 2017 20:42:31 -0800 (PST)
To: Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Date: Thu, 16 Feb 2017 23:42:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8kuSWqrCY49YqwZtC-U8PEWDTiE>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 04:42:36 -0000

So it is intentional that this draft prohibits that behavior (PCE driven 
establishment)?

Yours,
Joel

On 2/16/17 11:35 PM, Dhruv Dhody wrote:
> Hi Joel,
>
> Regarding your comment -
>
>> Is the intention to prohibit the driving
>> of LSP creation from the PCE?
>
> This capability is described in -
> https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07 (document expired recently, authors should refresh it)
>
> Thanks,
> Dhruv
>
>> -----Original Message-----
>> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
>> Sent: 17 February 2017 09:08
>> To: gen-art@ietf.org
>> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
>> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
>>
>> Reviewer: Joel Halpern
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area Review
>> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
>> the IETF Chair.  Please treat these comments just like any other last call
>> comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-pce-stateful-pce-??
>> Reviewer: Joel Halpern
>> Review Date: 2017-02-16
>> IETF LC End Date: 2017-02-28
>> IESG Telechat date: 2017-03-16
>>
>> Summary:
>>
>> Major issues:
>>
>> Minor issues:
>>    At the end of section 5.4, the text talks about a PCE accepting status
>> updates even if the  stateful capability has not been negotiated.  Which is
>> fine.  But as written, the text seems to say that doing so means that the
>> PCE will be able to "build and maintain an up to date view of the state of
>> the PCC's LSPs".  However, if the capability has not been negotiated, I do
>> not see how the PCE can count on getting full and timely state reports.  Trying
>> to infer why a PCC is sending such a report in the absence of the agreement
>> seems problematic.
>>
>>     This comment may be a misunderstanding or mis-expectation on my part.
>> I would have expected one of the ways o using an active PCE is to have the
>> PCE decide (under suitable circumstances) that an LSP is needed between two
>> PCCs.  As far as I can tell, the text in section
>> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Update
>> Request (in a PCUpd message) for an LSP that has been delegated to it.  At
>> that point I thought that a PCC could delegate a block of unsetup LSPs to
>> the PCE.  But then looking at 5.8.2, the text states that for each delegation,
>> the PCC must request an initial path.  That seems to prohibit delegating a
>> block of LSPs for future updates.  Is the intention to prohibit the driving
>> of LSP creation from the PCE?
>>
>>     I have looked but I can not find the text explaining the significance
>> and use of the Symbolic path name.  It is mandated by the draft.  There seems
>> to be an implicit assumption taht it is needed by the PCE.  If the explanation
>> of how or why it is needed is not present, it should be.
>>
>> Nits/editorial comments:
>>     Should the text on the S bit in section 7.3 (the LSP Object
>> definition) note that it should be set to 0 on all messages sent by the PCE?
>> Should that also be stated for the R bit?  And the O bits?
>>
>>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some
>> additional work.  I understand why teh work is needed.  But this does not
>> seem to match the RFC 2119 meaning of SHOULD as it does not apply to eitehr
>> the implementor or the implementation.
>>
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce


From nobody Fri Feb 17 04:11:07 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899191299BD; Fri, 17 Feb 2017 04:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l908I6ahpKjU; Fri, 17 Feb 2017 04:11:03 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7C8B1299C5; Fri, 17 Feb 2017 04:11:01 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAU18360; Fri, 17 Feb 2017 12:10:59 +0000 (GMT)
Received: from BLREML701-CAH.china.huawei.com (10.20.4.170) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 17 Feb 2017 12:10:58 +0000
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml701-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Fri, 17 Feb 2017 17:40:48 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM9gtp/PSv/bkEq3uaeNA/BLdaFsmcuQ//+o4ACAAMp5QA==
Date: Fri, 17 Feb 2017 12:10:47 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.40.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58A6E853.0312, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 7a98ac300b3205c6cd833c86bba88d68
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/hwDVkh8YsuDg1Ac8KWcj67A0gzE>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:11:05 -0000

Hi Joel,=20

In my opinion the motivation behind section 5.8.2 is to make sure that, if =
a PCC needs to request a path to be computed by PCE immediately, PCC should=
 use the existing PCReq message to achieve that.=20
=20
Can the PCC delegate an unsignalled LSP to PCE via PCRpt message? In my int=
erpretation it can, in some cases[1]. I would let the authors confirm on th=
is.=20

Thanks,
Dhruv

[1] https://mailarchive.ietf.org/arch/msg/pce/bexK_Nc2wHgQzV-XUC8lqMec8zY

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: 17 February 2017 10:13
> To: Dhruv Dhody <dhruv.dhody@huawei.com>; gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
>=20
> So it is intentional that this draft prohibits that behavior (PCE driven
> establishment)?
>=20
> Yours,
> Joel
>=20
> On 2/16/17 11:35 PM, Dhruv Dhody wrote:
> > Hi Joel,
> >
> > Regarding your comment -
> >
> >> Is the intention to prohibit the driving of LSP creation from the
> >> PCE?
> >
> > This capability is described in -
> > https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07
> > (document expired recently, authors should refresh it)
> >
> > Thanks,
> > Dhruv
> >
> >> -----Original Message-----
> >> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
> >> Sent: 17 February 2017 09:08
> >> To: gen-art@ietf.org
> >> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org;
> >> ietf@ietf.org
> >> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
> >>
> >> Reviewer: Joel Halpern
> >> Review result: Ready with Issues
> >>
> >> I am the assigned Gen-ART reviewer for this draft. The General Area
> >> Review Team (Gen-ART) reviews all IETF documents being processed by
> >> the IESG for the IETF Chair.  Please treat these comments just like
> >> any other last call comments.
> >>
> >> For more information, please see the FAQ at
> >>
> >> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> >>
> >> Document: draft-ietf-pce-stateful-pce-??
> >> Reviewer: Joel Halpern
> >> Review Date: 2017-02-16
> >> IETF LC End Date: 2017-02-28
> >> IESG Telechat date: 2017-03-16
> >>
> >> Summary:
> >>
> >> Major issues:
> >>
> >> Minor issues:
> >>    At the end of section 5.4, the text talks about a PCE accepting
> >> status updates even if the  stateful capability has not been
> >> negotiated.  Which is fine.  But as written, the text seems to say
> >> that doing so means that the PCE will be able to "build and maintain
> >> an up to date view of the state of the PCC's LSPs".  However, if the
> >> capability has not been negotiated, I do not see how the PCE can
> >> count on getting full and timely state reports.  Trying to infer why
> >> a PCC is sending such a report in the absence of the agreement seems
> problematic.
> >>
> >>     This comment may be a misunderstanding or mis-expectation on my pa=
rt.
> >> I would have expected one of the ways o using an active PCE is to
> >> have the PCE decide (under suitable circumstances) that an LSP is
> >> needed between two PCCs.  As far as I can tell, the text in section
> >> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
> >> Update Request (in a PCUpd message) for an LSP that has been
> >> delegated to it.  At that point I thought that a PCC could delegate a
> >> block of unsetup LSPs to the PCE.  But then looking at 5.8.2, the
> >> text states that for each delegation, the PCC must request an initial
> >> path.  That seems to prohibit delegating a block of LSPs for future
> >> updates.  Is the intention to prohibit the driving of LSP creation fro=
m
> the PCE?
> >>
> >>     I have looked but I can not find the text explaining the
> >> significance and use of the Symbolic path name.  It is mandated by
> >> the draft.  There seems to be an implicit assumption taht it is
> >> needed by the PCE.  If the explanation of how or why it is needed is n=
ot
> present, it should be.
> >>
> >> Nits/editorial comments:
> >>     Should the text on the S bit in section 7.3 (the LSP Object
> >> definition) note that it should be set to 0 on all messages sent by th=
e
> PCE?
> >> Should that also be stated for the R bit?  And the O bits?
> >>
> >>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do
> >> some additional work.  I understand why teh work is needed.  But this
> >> does not seem to match the RFC 2119 meaning of SHOULD as it does not
> >> apply to eitehr the implementor or the implementation.
> >>
> >>
> >> _______________________________________________
> >> Pce mailing list
> >> Pce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pce


From nobody Fri Feb 17 04:16:06 2017
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D961294F7; Fri, 17 Feb 2017 04:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpA_pe1mbwQq; Fri, 17 Feb 2017 04:16:03 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43E4A1294DA; Fri, 17 Feb 2017 04:16:03 -0800 (PST)
X-AuditID: c1b4fb30-eabff70000002c77-3c-58a6e9818886
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by  (Symantec Mail Security) with SMTP id 21.40.11383.189E6A85; Fri, 17 Feb 2017 13:16:01 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.48) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 17 Feb 2017 13:16:00 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yCISXXNfeyonyD5kh2lOliucztN3IvWD+DKx/MA1H84=; b=CKkXEk+bxxAw7eCfGsstqjHAeBU2i8lcQt3+y13ZHSmptB5qetbamUUzdOS+EjsgXZ0FDglwaOThWAP3JM/ZU0MxscGN6QlfsZaPostjl8P1onYXd7xL9rF0sqj8BHG6sQUL+55caxkKFDTJR0eoSedXAKWreFSXsWsDltQOFaE=
Received: from HE1PR0701MB2539.eurprd07.prod.outlook.com (10.168.129.17) by HE1PR0701MB2540.eurprd07.prod.outlook.com (10.168.129.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Fri, 17 Feb 2017 12:15:59 +0000
Received: from HE1PR0701MB2539.eurprd07.prod.outlook.com ([10.168.129.17]) by HE1PR0701MB2539.eurprd07.prod.outlook.com ([10.168.129.17]) with mapi id 15.01.0919.013; Fri, 17 Feb 2017 12:15:59 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-kivinen-802-15-ie-04.txt
Thread-Index: AQHSh4tJhO14+8N/uEqhDEBHzIlQ8KFtHyrg
Date: Fri, 17 Feb 2017 12:15:59 +0000
Message-ID: <HE1PR0701MB253962BEBEB12586DC10F77A985D0@HE1PR0701MB2539.eurprd07.prod.outlook.com>
References: <201702151248.v1FCmL5E014275@givry.fdupont.fr>
In-Reply-To: <201702151248.v1FCmL5E014275@givry.fdupont.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=francesca.palombini@ericsson.com; 
x-originating-ip: [192.36.157.200]
x-ms-office365-filtering-correlation-id: 1d6593c7-3307-451a-ee24-08d4572ebbc2
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:HE1PR0701MB2540; 
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2540; 7:syjjWMxKkmja2PpdVfliVxd5Ee28RLP036kW7ykAx/uqhIOoKmT1csMEV9P8rL1Se1yPExaTAaJ2v0y+8QwcaFXkQ4tsyXUBu+QGjER/+gbEzq6+/CoFljLMeL0CrqIXcDgpVMojUUWt2LMyvwZ0dreKL8B5bs6ryOFO7WGz+qLJJaKqPzc4gxgrWKPqfOcwpXOXEhXkVQYH90FmnNqiYTL+0Sy5sIcfDni8yH+WSgk8zXTJER/GVwF0Xv8aUm9qU9bjCBd+/MtVhxNu5MYRmmZ1kv4dfGTiQFmHNoZE7ooWlhB1N6ojQShZ991qhbYs15HkllJive9z8VnyOkDnVg==
x-microsoft-antispam-prvs: <HE1PR0701MB25401E1457892855A5E08EA1985D0@HE1PR0701MB2540.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123560025)(20161123564025)(20161123562025)(20161123555025)(20161123558025)(6072148); SRVR:HE1PR0701MB2540; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2540; 
x-forefront-prvs: 02213C82F8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(13464003)(199003)(6306002)(66066001)(2906002)(2950100002)(3660700001)(6436002)(77096006)(229853002)(102836003)(6116002)(86362001)(2900100001)(9686003)(3846002)(101416001)(230783001)(7696004)(81166006)(53546006)(53936002)(99286003)(8676002)(4326007)(33656002)(122556002)(6246003)(55016002)(8936002)(3280700002)(38730400002)(81156014)(74316002)(7736002)(5660300001)(25786008)(76176999)(50986999)(68736007)(189998001)(54356999)(305945005)(97736004)(106356001)(105586002)(6506006)(2501003)(92566002)(106116001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2540; H:HE1PR0701MB2539.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Feb 2017 12:15:59.4267 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2540
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfyzUYRzHPd8f5+vm2uMwn3H90W00lI5yU91a+sO0hVp/MP2Ri++wcNcd FqOcdc0pZkPLJZHr/GhxE6NES9lijMRYyo/8GgqVrHamnEdb/73en/d7z+d5P3s4WnyLdecS U1J5TYoySSoQMmVRrbKDukVzlGytXhLU25FDBX2+84wNGln6wZykQ1dKN9lQk+k3dZaKFiri +KTEdF5z6ESMMGFjuhWpLcKr+htWQQ6q4/KRAwf4CFh1s3Q+EnJi3IBA9zHPnoi3CCw/X+4I BhfQsNxdwRDHSMH6whZFRC+Ckvn79rbDBFgBg9OrrI1dcCRYR1/TNqbxeSgcahfY2BkHwsb4 EiIZOaxVj9OEA6C6an5nzmBPaGlv3l7AcSIcA0VTcttYjI9B7sO5nbgDPg51oybGxgjvhXXd 491VbvBh9gFFumEwvRigCbvC4swWS/KxMDxeaE/mUmjLvbebCQP94LqAcAQM9d1kbR0BF9Lw 64+FIYYKJnsMLGEfyHtjpEiogoLyptuIGBJYWf1GE2OKhYaeLwJSgYeaJ3pEXsIdPg0bUBHy Mf53c8IHoLL9u4CwL5irlmkbi7AT9JTNMpWIqUeuWl57KTk+IMCP1yTGarWqFL8UPrUJbX+R V81WWRtaXAjuQphDUkeRuvNRlJhVpmszkrsQcLTURdQyY44Si+KUGZm8RnVRk5bEa7uQB8dI 3UTyuslIMY5XpvKXeV7Na/65FOfgnoOKE5yvdZbVy32fWs0yb4W11rFrxc6uhrHzii5Xu6Y5 B7/zyJvJej+pZEOuh8ccHcicbhxjss0qT8uFAqqv2P/rqeR+aRarzL7rZCx4rlZ4GXz8Yir2 hy+slJy+YnApDazejBDnTMydm9jT7S0LUUlGDp/Z1zBmqm3skIT1b+iljDZB6e9Da7TKv4Vd zPQeAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/jQ_ZrThVaKNIBtXoMJJZ2wWlLeo>
Cc: "draft-kivinen-802-15-ie.all@ietf.org" <draft-kivinen-802-15-ie.all@ietf.org>
Subject: Re: [Gen-art] review of draft-kivinen-802-15-ie-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:16:05 -0000

Francis, thanks a lot for your review.

Francesca

> -----Original Message-----
> From: Francis Dupont [mailto:Francis.Dupont@fdupont.fr]
> Sent: den 15 februari 2017 13:48
> To: gen-art@ietf.org
> Cc: draft-kivinen-802-15-ie.all@ietf.org
> Subject: review of draft-kivinen-802-15-ie-04.txt
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-kivinen-802-15-ie-04.txt
> Reviewer: Francis Dupont
> Review Date: 20170210
> IETF LC End Date: 20170214
> IESG Telechat date: 20170224
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
>  - ToC page 1 and 3 page 3 (title): Benefitting -> Benefiting
>=20
>  - 3 page 3 (suggest):  CoRE etc, ->  CoRE, etc,
>=20
>  - 4 page 3: reading the document I had a question about the "no need
>   ... to specify the internal structure" but the reason became clear
>   the next page. So I have no concern about this.
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From nobody Fri Feb 17 04:48:35 2017
Return-Path: <nite@hq.sk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD2FB129A14; Fri, 17 Feb 2017 04:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0XE4I5kSsI6; Fri, 17 Feb 2017 04:48:26 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB86129A12; Fri, 17 Feb 2017 04:48:25 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id 7203D240529; Fri, 17 Feb 2017 13:48:22 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487335702; bh=oX6kpQsn5dx7CI9Zbold9Pk2bux/AGqRGlPDAOP+AGA=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=V2b53Mwl9hDnAJf8flTVN8mvCTyvMfZy6+TL12Ta67OIGuN1xd1Z+Ew74o3q+d8go NAN7754+hreOOgv4t9B727fHlItKimbW3Y0eiJsGS9ZOb8R9+1mfOGyZI8Z2cdSCeK dqqdkH6UH8728K8471ixVKlsxiZ86u3/+kctqgpk=
To: Dhruv Dhody <dhruv.dhody@huawei.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com> <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
From: Robert Varga <nite@hq.sk>
Message-ID: <473033f8-4883-40e9-79e0-3bd15428655e@hq.sk>
Date: Fri, 17 Feb 2017 13:48:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SqdVNxODsMp80xP53OVVMx3OCm2MNjDps"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/GGdU4h2uAuokdfBhDPKZ4cGHuBI>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:48:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--SqdVNxODsMp80xP53OVVMx3OCm2MNjDps
Content-Type: multipart/mixed; boundary="w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: Dhruv Dhody <dhruv.dhody@huawei.com>,
 "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org"
 <gen-art@ietf.org>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org"
 <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <473033f8-4883-40e9-79e0-3bd15428655e@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
 <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
 <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
 <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>

--w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 01:10 PM, Dhruv Dhody wrote:
> Hi Joel,=20
>=20
> In my opinion the motivation behind section 5.8.2 is to make sure that,=
 if a PCC needs to request a path to be computed by PCE immediately, PCC =
should use the existing PCReq message to achieve that.=20
> =20
> Can the PCC delegate an unsignalled LSP to PCE via PCRpt message? In my=
 interpretation it can, in some cases[1]. I would let the authors confirm=
 on this.=20

Yes, it can.

The second paragraph on 5.8.2 is not intended to restrict usage of
delegation, but rather highlight the scenario where the LSP is
established without PCE's help.

Regards,
Robert


--w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF--

--SqdVNxODsMp80xP53OVVMx3OCm2MNjDps
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvEOCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDTwPwP/1NyUwji
DBvCawC7rMMlStn+vqkjO9oZ64b4SqnWu5rrfOzDZO5ilSLsu0M/ghnCQDkZws48
mV1gSxSXrP8q2bCAddwyMjaAoQUa8JkO1ID1Tmvr4j+anghZXZs4IH1ruB1JJ1w7
EcexCePLgQ/rAA7M4wq2CD0p64wr0EOUAex8tvK30H8uwyDcR0EvK+lA42IWByR+
A0/PBZwJMpatPAytt1EechnkXC9rBGCedjrFmaBHphQFe5JiVKR/9Uuk1ywmONGs
McBRyJjYwhNBkmypnCu6MftZlZhDWPy6IRHGM6Re/Tzh56SWnTglYv1R0v50IGCe
x3ydjvn51uD6C/ldbt8fYnJ6cnF9ootPs+n9j+K2/qscQ4Yy1WwPeHfqwhsuP3LN
0IFsTB7zZLN1JIyTrEW0n1E/NKOeXqSAzijY4fb5DZUZo8QcYx4CEMk+N2NE9Jrx
9GlqmRDcN52Cougs3D50RZBByyOyMorayiLPQjysZrBxOI6KcumDmlshdDlb/1p0
Il0UMwIZAIUrOwcYNfhy8REQhaIZLBVZukuJGQJ6xiKzfNtLcQfyPLX3bIEAFF44
keGbxR7iShlvNDe2IM80lPVyO0vi/78p6oncXqy0RrdtdaentnTWDD3F9YQC5fIN
gC0AmGEsVygVtaXAbD7XW+J9iFgBdoAcxFg8
=wpRh
-----END PGP SIGNATURE-----

--SqdVNxODsMp80xP53OVVMx3OCm2MNjDps--


From nobody Fri Feb 17 04:52:30 2017
Return-Path: <nite@hq.sk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D0B129735; Fri, 17 Feb 2017 04:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aru9aJgDQjMF; Fri, 17 Feb 2017 04:52:27 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85D31299D6; Fri, 17 Feb 2017 04:52:27 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id 2F2D1240529; Fri, 17 Feb 2017 13:52:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487335946; bh=nYHBf/DxSJJFBIwUat3UILzGdypD2N0/k62t6go4k2A=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=S35AkkIQQcrPYgG0w4dpbERrQDLrQ8NUfYSr0Gsnjcim5Fe+wrYcU90ss05LM/AZP z8PResfVGifIhSREV20/42ZEMQE8ThuRpxyw4S7U0bezNnK9cZxFNDEHhOJPFGQDeR ibcyiTgYJz3wyocHQ3PAGsZ0InIXcHzWwEYYZw0I=
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
From: Robert Varga <nite@hq.sk>
Message-ID: <d6cf2dbd-98d2-345e-521c-b8847fc894da@hq.sk>
Date: Fri, 17 Feb 2017 13:52:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8QHl-LUtAI4-3GMDRg87me1XDis>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:52:29 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj
Content-Type: multipart/mixed; boundary="spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: "Joel M. Halpern" <jmh@joelhalpern.com>,
 Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org"
 <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <d6cf2dbd-98d2-345e-521c-b8847fc894da@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
 <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
 <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>

--spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 05:42 AM, Joel M. Halpern wrote:
> So it is intentional that this draft prohibits that behavior (PCE drive=
n
> establishment)?

Yes, it is intentional. pce-stateful-pce is designed so that the PCC
remains the ultimate master of state, in line with RFC5440.

Regards,
Robert


--spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE--

--k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvIHCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDT4bUP/iBiP3ul
HVtc07NLW+y3g2od/95Lx7+OIToyQcv0mA45JJrI/ZPw/Iq8UQfhMQYEejy0/M0n
R3jp1bF2QHcMUqi5Zb1lhioLXDpNZ4AHHpIyjLguc0sE715YIXKTv2jjZrkxYThc
NslqIq0ejfrtB3icfTqe/me9XIH/tP2cwPkqd6jV6FbJj1PsY15IT39daU2kaM/j
hiQVOnpH6QfFx7ewpPtekS+GUR7Y4+462sr0rYhYukpuI26bcb3r88LUkfqOZtCi
HYW5er0HKEojaulZzOxrV1cxwNe+PSxhtbmTWncUALmxF9SVA52+7FIK/BjTfNpe
q4l7FCflUYUnDE057CRjZwovh/aygN4bweLUW+eWqSQpHc8mUgy/q5JLM9XIWr6g
zqw7P4tAlkwSL+fa+SG8TDEKCtLkWftxBdKNty8/LiHHJDMa3Hw4XdqQoalVdz3D
sYmLryebz7rDtNC0N209NK7vo595HOD2Gt348SnwKzGp4NcPh7qkecd47NjkoQh4
Djxn51TR973+kCJHcowNrTneQzeXFlQCS9Zog/Tz6oK0xGQaw2OFW9XyDhKKEsta
PKYrmbnED0LXcfP+QhQdzVPERPpGv8dgadLUZzKs5wQqL1KKoA15iVz8O8Zq8ESf
seEH78Ge0ikgm0QPgLd6JCFmnleKSxP4peYw
=CPFo
-----END PGP SIGNATURE-----

--k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj--


From nobody Fri Feb 17 05:12:36 2017
Return-Path: <nite@hq.sk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D7D129A4D; Fri, 17 Feb 2017 05:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8uhI40ZxM3l; Fri, 17 Feb 2017 05:12:24 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABA72129A48; Fri, 17 Feb 2017 05:12:23 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id D34BF240529; Fri, 17 Feb 2017 14:12:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487337142; bh=o5jAr1OUb7BO7sKdh69cuhwaX18XoFa8MjAZFePEx0k=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=JPs7KLiK2nEMOmGRJluDEeDgv1PuAJFfh0f0JgxsP2H50zirKXs0JAzwilDjR/w4o MLyNNfjDlANQLDP6G2M1FlOZbnJLHmC3j5PaRkLadEhvJjrowOwUx28o9k8uCeYRJT Fho8lO2KNl7XhCgNTa77BbDFisiIVtECkn63PQI8=
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
From: Robert Varga <nite@hq.sk>
Message-ID: <ff31899f-23f5-f3b2-41c8-89fc16586c38@hq.sk>
Date: Fri, 17 Feb 2017 14:12:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/NW2UliHotBy7SyWjXNoUbdE5VKU>
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] [Pce] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 13:12:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp
Content-Type: multipart/mixed; boundary="CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
Message-ID: <ff31899f-23f5-f3b2-41c8-89fc16586c38@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>

--CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 04:37 AM, Joel Halpern wrote:
>=20
>     This comment may be a misunderstanding or mis-expectation on my
> part.  I would have expected one of the ways o using an active PCE is
> to have the PCE decide (under suitable circumstances) that an LSP is
> needed between two PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
> Update Request (in a PCUpd message) for an LSP that has been delegated
> to it.  At that point I thought that a PCC could delegate a block of
> unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states
> that for each delegation, the PCC must request an initial path.  That
> seems to prohibit delegating a block of LSPs for future updates.  Is
> the intention to prohibit the driving of LSP creation from the PCE?

I think this may be a case consistency rotting over the years this draft
has been out there, which also affects my recollection of reasoning
behind the text.

Sections 5.8.1 and 5.8.2 govern how to transition from 'passive
stateful' mode of operation, where the PCC uses PCRpt to communicate
state and PCReq to solicit updates. They are not meant (or at least not
when they were originally written) to restrict the delegation procedure.

The wording of 5.8.2's first paragraph has an implicit unstated goal of
ensuring that the LSP will be set up, i.e. the PCC first makes an
explicit request to acquire the parameters needed to signal the LSP and
then delegates the LSP, thus ensuring a computation is made.

I think it is still valid for PCC to delegate an LSP without performing
5.8.1, in which case the PCE decides when (and if) to push the
parameters required to make the LSP operational.

I do see this as a problem, as the PCC is free to revoke the delegation,
based solely on its local policy, if the PCE fails to fill in the LSP
parameters in a reasonable time frame -- reverting to either local
control or to 5.8.1 mechanics.

Regards,
Robert


--CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va--

--2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvasCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDTfNQP/3zMSesO
uwaSxSg5QBneclZjThLE51SeaZRjyQ2Qm8lt+zv25WdfQB4uhRQsBl9rfCvadMBT
NMIkIpBzS+o6YePoyi/BswWaAjFeByou4EsBvTttLqvZHkqDa2kKsfNUv0i7oEZr
+x78WedrUC8wxTjHKmRin8eTCjdf/25uRvgLmQBcH7i0tuwn7UQdEj/9+hyeB++8
ZYC8tIORFeJDwB9HTsiNSi2DpBf1nO214fbC9H+8EJF8IGNDheMOwwJWjVqX19ee
U+u1GMU5GVuPeucWATOe1S6DqkQs6zRLuCJShO7WMmn/EKiRq7hVmyzJs1xV+MvB
Og/EASSIyp+5QS/Wp6jHK9dQ3MQ1Dzda2cd/Rud0d6NNE4b5w8haiS8ikRgit0Qn
nlhQlymTjH01b+phjkIJ/AQ5dB3DS1UfKHt3/I5TZ2cr+DZJ58tuLIaFJc2qJQkj
AL9hsYUo62rIn7EeSh/6blv/rmuaWenZDC/BSf18u8q0cKjXy25Q66I2DvbCYwHm
x2/aQF+K3xc5z6NHJEg9mCYlpcHvK0s5+6pe+xV0EBtzGybydPOU0guYf0qCOZRV
P4ZkuWik2GjALYp7AD3zr0wf8VPe1os/3sb5JWJBzHk3bIXu47xiq2qSTaOZ5en5
ITCiVqsWDPJoazom+vIH5VkCyAZmP6mC0J9D
=wNuR
-----END PGP SIGNATURE-----

--2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp--


From nobody Fri Feb 17 13:01:57 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 130D2129BE5 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2017 13:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbMR1cNNu4Mw for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2017 13:01:54 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE88E129BE1 for <gen-art@ietf.org>; Fri, 17 Feb 2017 13:01:54 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-01-58a71e6b69fb
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by  (Symantec Mail Security) with SMTP id 04.DF.02566.B6E17A85; Fri, 17 Feb 2017 17:01:50 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0319.002; Fri, 17 Feb 2017 16:01:51 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-dmm-hnprenum-06
Thread-Index: AdKJYQRXWYpygA5VTea6kv2slPldgg==
Date: Fri, 17 Feb 2017 21:01:50 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E88DDFA@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E88DDFAeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXRPiG6e3PIIgw9zJCzOn+9ltrj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXx9+QhloJzShVtL9QbGE/JdTFyckgImEg8 2f+ftYuRi0NIYD2jxKw7u9ggnOWMEqennWYGqWITsJDY/vs5WJWIQAejRO+33ewgCWEBZ4me uauZQGwRAQ+Ju9s/snQxcgDZehLXF4iDhFkEVCWe7LwHVsIr4CvxZvYtMJtRQEzi+6k1YDaz gLjErSfzmSAuEpBYsuc8M4QtKvHy8T9WCFtRYl//dHaI+nyJltUn2CBmCkqcnPmEZQKj4Cwk o2YhKZuFpAwiriOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYuQoLS7IyU03MtzECAz6YxJs jjsY9/Z6HmIU4GBU4uHdcH1ZhBBrYllxZe4hRgkOZiUR3qlJyyOEeFMSK6tSi/Lji0pzUosP MUpzsCiJ814PuR8uJJCeWJKanZpakFoEk2Xi4JRqYEyw27TzWuTCmn3K64J9Z/jIHC2uZnod ZdHjPveyQHjd9vrLzvHsBbZ57b+mMl5JOfKBbe3cs5PO7m9la09TajrnV/v8Jad0/6qrqr/3 T1/7p1Hx6vY7L/snzbOfPyfrsVlHSKBpJu+5nwdTH7icfsCQrm/oq2zsJhzSwSBx5Jzsa613 52/+uKLEUpyRaKjFXFScCACQdY6WdgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/iIrWSxCXbfC1PLOn0crTkVzfT5o>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-dmm-hnprenum-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 21:01:56 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E88DDFAeusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair. Please wait for direction from your document shepherd or AD =
before posting a new version of the draft.

For more information, please see the FAQ at <http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-dmm-hnprenum-06
Reviewer: Meral Shirazipour
Review Date: 2017-02-17
IETF LC End Date: 2017-02-10
IESG Telechat date: 2017-03-02

Summary: This draft is ready to be published as Standards RFC.

Major issues:
Minor issues:
Nits/editorial comments:

Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E88DDFAeusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair. Please wait for direction from your d=
ocument shepherd or AD before posting
 a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-dmm-hnprenum-06<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-02-17<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2017-02-10&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2017-03-02<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E88DDFAeusaamb107erics_--


From nobody Fri Feb 17 18:32:30 2017
Return-Path: <worley@ariadne.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B19E129449; Fri, 17 Feb 2017 18:32:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Dale Worley" <worley@ariadne.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
Date: Fri, 17 Feb 2017 18:32:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/g4zNLVZwm2OErwb5bXCUDsd0Lqk>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
Subject: [Gen-art] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 02:32:25 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-slim-negotiating-human-language-06
Reviewer:  Dale R. Worley
Review Date:  2017-02-17
IETF LC End Date:  2017-02-20
IESG Telechat date:  [unknown]

Summary:
       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

* Technical comments

A. Call failure

If a call fails due to no available language match, in what way(s)
does it fail?  Section 5.3 says

   If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent

But I suspect it's also allowed for the UAS to fail the call at the
SIP level.  Whether or not that is allowed (or at least envisioned)
should be described.  And what response code(s)/warn-code(s) should
be
used for that?

B. Audio/Video coordination

   5.2.  New 'humintlang-send' and 'humintlang-recv' attributes

   Note that while signed language tags are used with a video stream
to
   indicate sign language, a spoken language tag for a video stream
in
   parallel with an audio stream with the same spoken language tag
   indicates a request for a supplemental video stream to see the
   speaker.

And there's a similar paragraph in 5.4:

>    A spoken language tag for a video stream in conjunction with an
audio
>    stream with the same language might indicate a request for
>    supplemental video to see the speaker.

I think this mechanism needs to be described more exactly, and in
particular, it should not depend on the UA understanding which
language tags are spoken language tags.  It seems to me that a
workable rule is that there is an audio stream and a video stream and
they specify exactly the same language tag in their respective
humintlang attributes.  In that case, it is a request for a spoken
language with simultaneous video of the speaker, and those requests
should be considered satisfied only if both streams can be
established.

* The following three items are adjustments to the design which I'd
like to know have been considered.

C. "humintlang" seems long to me

Given the excessive length of SDP in practice, it seems to me that a
shorter attribute name would be desirable.  E.g., "humlang" as was
used in some previous versions.  Or is there a coordinated usage with
other names in the "hum*lang" pattern?

D. Use the Accept-Language syntax

It seems to me that it would better to use the Accept-Language syntax
for the attribute values.  This allows (1) specifiying the quality of
language experience, allowing clear description of bilingualism, (2)
a
unified method of specifying whether or not arbitrary languages are
acceptable, and (3) abbreviating SDP descriptions.

In a way, the fact that the current proposal seems to require (but
does not directly specify) the coordinated absence/presence of an
asterisk on all of the repetitions of humintlang-send or
humintlang-recv is a warning that the syntax doesn't represent the
semantics as well as it might.

E. Have an attribute to abbreviate the bidirectionally-symmetric case

Note that all examples are bidirectionally symmetric, and the text
says that requests and responses SHOULD be bidirectionally symmetric.
So it would be a very useful abbreviation to define
"humintlang=<value>" to be equivalent to the combination of
"humintlang-send=<value>" and "humintlang-recv=<value>".

Combining proposals C, D, and E, the examples become

      m=audio 49170 RTP/AVP 0
      a=humlang:en

      m=video 51372 RTP/AVP 31 32
      a=humlang:ase,*;q=0.1

      m=audio 49250 RTP/AVP 20
      a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1

      m=text 45020 RTP/AVP 103 104
      a=humlang:gr

which requires about half as many characters as they have now.

* Editorial comments and nits

Abstract

   This document describes the need and a solution using new SDP
stream
   attributes.

I don't think the term "stream attribute" is used in RFC 4566.
Instead, it uses "media attribute".

1.  Introduction

   caller and callee know each other or there is contextual or out of
   band information from which the language(s) and media modalities
can

I think this context, it's preferred to hyphenate "out-of-band" to
make it clearly be an adjective.

   This approach has a number of benefits, including that it is
generic
   (applies to all interactive communications negotiated using SDP)
and
   not limited to emergency calls.

I think s/and not limited to/and is not limited to/ reads more
smoothly.

   But it is clearly useful in many other cases.  For
   example, someone calling a company call center or a Public Safety
   Answering Point (PSAP) should be able to indicate if one or more
   specific signed, written, and/or spoken languages are preferred,
the
   callee should be able to indicate its capabilities in this area,
and
   the call proceed using in-common language(s) and media forms.

I think s/preferred, the callee/preferred; the callee/ because the
sentence is the concatenation of two sentences.

Perhaps s/in-common/shared/.

   Including the user's human (natural) language preferences in the
   session establishment negotiation is independent of the use of a
   relay service and is transparent to a voice service provider. 

I think it's even broader than "transparent to a voice service
provider" -- it's transparent to any serivice provider, assuming that
the media are language-neutral.

   In the case of a call to e.g., an airline, the call could be
   automatically handled by a Spanish-speaking agent.

I think s/handled by/routed to/ is the usual usage.

3.  Desired Semantics

   The desired solution is a media attribute (preferably per
direction)
   that may be used within an offer to indicate the preferred
language
   of each (direction of a) media stream, and within an answer to
   indicate the accepted language.

In this one instance, I think you want to use "language(s)" to drive
home that that multiple languages can be specified:  "within an offer
to indicate the preferred language(s)".

   (Negotiating multiple simultaneous languages within a media stream
is
   out of scope, as the complexity of doing so outweighs the
   usefulness.)

You might want to say instead "(Negotiating multiple simultaneous
languages within a media stream is out of scope for this document.)"
to ensure that nobody decides to argue whether "the complexity of
doing so outweighs the usefulness".

4.  The existing 'lang' attribute

   RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
   similar to what is needed here, but is not sufficiently detailed
for
   use here.

"for use here" isn't quite right.  Maybe "is not sufficiently
specific
or flexible to satisfy the requirements".

   In addition, it is not mentioned in [RFC3264]

"it" is somewhat ambiguous here, perhaps change to "the 'lang'
attribute".

5.  Proposed Solution

Perhaps /Proposed Solution/Solution/, since once this draft is
approved, it becomes the solution.

5.2.  New 'humintlang-send' and 'humintlang-recv' attributes

      a=humintlang-send:<language tag>
      a=humintlang-recv:<language tag>

This is presented as the generic form of the attributes, but there is
no indication of the posible asterisk.

   The values constitute a list of languages
   in preference order (first is most preferred).

"The values" isn't very clear, because the values are in successive
attributes.  You want to say something like "The sequence of values
in
the occurrences of one of these attributes constitutes ...". 
However,
see the technical comments above.

   When placing an emergency call, and in any other case where the
   language cannot be assumed from context, each media stream in an
   offer primarily intended for human language communication SHOULD
   specify both (or in some cases, one of) the 'humintlang-send' and
   'humintlang-recv' attributes.

Probably s/assumed/inferred/.

Could you be more accurate by
s/or in some cases/or for unidirectional streams/?

5.3.  Advisory vs Required

   The mechanism for indicating this preference is that, in an offer,
if
   the last character of any of the 'humintlang-recv' or 'humintlang-
   send' values is an asterisk, this indicates a request to not fail
the
   call (similar to SIP Accept-Language syntax).  Either way, the
called
   party MAY ignore this, e.g., for the emergency services use case,
a
   PSAP will likely not fail the call.

The construction of this paragraph isn't quite complete.  It says
that
if an asterisk is present, a request shouldn't fail, but it doesn't
say that if no asterisk is present, a request should fail if there is
no language match.  And it's the latter condition that makes the
second sentence meaningful.  So I think you want to insert between
the
two sentences one regarding the absence of an asterisk.

5.5.  Examples

Given that the combined audio/video mechanism is the only
irregularity
in this system, there ought to be an example of it.  E.g.,

   An example of a supplemental video stream with a spoken language
   audio stream:

      m=video 51372 RTP/AVP 31 32
      a=humintlang-send:en
      a=humintlang-recv:en

      m=audio 49250 RTP/AVP 20
      a=humintlang-send:en
      a=humintlang-recv:en

6.  IANA Considerations

      humintlang-value =  Language-Tag [ asterisk ]
                          ; Language-Tag defined in RFC 5646
      asterisk         =  "*"

s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
5646/

But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
tracks the current version of language tags.

Appendix A.  Historic Alternative Proposal: Caller-prefs

   This
   results in a more fragile solution since the media modality and
   language would be negotiated using SIP, and then the specific
media
   formats (which inherently include the modality) would be
negotiated
   at a different level (typically SDP, especially in the emergency
   calling cases), making it easier to have mismatches (such as where
   the media modality negotiated in SIP don't match what was
negotiated
   using SDP).

"the media modality and language would be negotiated using SIP" isn't
quite the right way to say it because SIP isn't explicitly
negotiating
the modality.  Better would be

   ... the language (and by implication the media modality) would be
   negotiated using SIP, and then the specific media (which
inherently
   include the modalities and formats) would be negotiated at a
   different level ...

[END]



From nobody Sun Feb 19 06:27:14 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFE01296C2 for <gen-art@ietfa.amsl.com>; Sun, 19 Feb 2017 06:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.485
X-Spam-Level: 
X-Spam-Status: No, score=-4.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P_HnlkZH5a5M for <gen-art@ietfa.amsl.com>; Sun, 19 Feb 2017 06:27:09 -0800 (PST)
Received: from nm17-vm3.bullet.mail.gq1.yahoo.com (nm17-vm3.bullet.mail.gq1.yahoo.com [98.137.177.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D9C81296C0 for <gen-art@ietf.org>; Sun, 19 Feb 2017 06:27:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487514429; bh=orIPtZjq+vT+eCeyHpz3K9/Z8fWjTmViJ61d6KUg4KE=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=ZLfMJlMJzvArv+87Kz/3HgWgeo23hY+D+i/cdDqkIpxhem9LFTPvtl02SSReLJDkOuAlBb9f3CQatZCqUW0jFupJVHhX8uqU+d6D/k7Hp4ZQcCJnbZ9d6HhviQ3UV2jM6nOi2LMwXyRMe5iAvix7J764P6ykicW95dHNwB2LAOZETsrQceht5acRLIl4cAmXcG3Bllo5ayQ6vUX1Nf0IKp6NQJA5stU9SrvjQxfjM4rUtUfF+m7qmYhPXLT2izgQkkeDtLrzUWkbd4aifKq5MoXdcpdiXy/HasMCA4mJXR2IN35pHFlM6Scwtry6miV2pmlJCJdcl8MgV5SVsQDVgQ==
Received: from [98.137.12.189] by nm17.bullet.mail.gq1.yahoo.com with NNFMP; 19 Feb 2017 14:27:09 -0000
Received: from [98.137.12.203] by tm10.bullet.mail.gq1.yahoo.com with NNFMP; 19 Feb 2017 14:27:09 -0000
Received: from [127.0.0.1] by omp1011.mail.gq1.yahoo.com with NNFMP; 19 Feb 2017 14:27:09 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 153635.426.bm@omp1011.mail.gq1.yahoo.com
X-YMail-OSG: xIBi3zIVM1mSKmcTbuEFc5I_uA3EpaLV0QsQ0hQf0WVv..yjo0N168YlB.UHxFb XokMMis7Umf2T9vzsel92nlK7d9asVUeNQD0dnHciDrbhnTxSxd.72pLHOr7S7eoJvrIIq29EGek OTsrkTq6xWY2ycWzxjnGqijKlnLCezPROKnlObAWLjJzHGFrHy6f_SAtvikZLLn55YBfKJjSe8Xa slkNs6zpxtC3asQtxUYhNic6E0UYfNCq2_YqzThZRcZBpf088_ct1cnQqfrzpcE6CmpB1IwZ40mZ loET0nHeO8vdv2d5Ir.IFfDQrRIVGGu6c2XAU7Zj11MjXg6QeBWQDPIwe6WzobwKO.de2rbKJ29W r_5_IDJG0QAHReLmhqw1mC2DucGW1Ag6Y89EPyyurAh1dtLVCiiiWpCY_Ho4i2LO8RTeOzFmRFMV 5CsIWVVyPoTm8NbAIZ6ZdpvY0Tf8qHJGGVEG17085spjctLlob5B8kZQGM1XmgnkYZSHh2r1qEVV MCNlu0dQyhZSlTO_fQg0JRnIMFVQ4mIxjVwlx35Qarn_zzzNxyQA-
Received: from jws300034.mail.gq1.yahoo.com by sendmailws129.mail.gq1.yahoo.com; Sun, 19 Feb 2017 14:27:08 +0000; 1487514428.719
Date: Sun, 19 Feb 2017 14:26:54 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: jouni korhonen <jouni.nospam@gmail.com>,  General Area Review Team <gen-art@ietf.org>,  "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>
Message-ID: <1332138488.632081.1487514414996@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_632080_2137494313.1487514414993"
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/IQsrAo6iV9YBEBWL-6-AyNXF57k>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Time Reference Plane
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 14:27:12 -0000

------=_Part_632080_2137494313.1487514414993
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Jouni,

We have finished with the comments from the Security Area (I believe!) and =
are now starting on the comments from you.

There is a new draft which has the latest changes incorporated.

https://datatracker.ietf.org/doc/draft-ietf-ippm-6man-pdm-option/

I wanted to start a thread for each of your major comments so that we could=
 concentrate on each and resolve them.

So, major comment #1 from you:

>1) There is no mention of what is the time reference plane for internal ti=
me stamping. All other timing and synchronization related documents I am aw=
are of (at least >outside IETF) describe it very clearly where in the proce=
ssing/packet handling the time stamp is to be taken. Now the document gives=
 me no idea as an implementer >where that should take place. At least it ma=
kes it hard to calculate the *network* RTT precisely.

I believe you are asking where the timestamp should be taken in the impleme=
ntation. =C2=A0 Please let me know if I am misunderstanding your question.
In rough terms,=C2=A0we want to capture the current time as soon as a packe=
t arrives and <quickly> perform any required calculations. Similarly, we wa=
nt to capture the time and <again, quickly> perform delta-time-sent as late=
 as possible before the packet is sent.
We can put something like that into the document somewhere. =C2=A0Of course=
, if the PDM header is encrypted, the encryption/decryption time becomes pa=
rt of the transport time.
In talking this over with the developer working on the prototype implementa=
tion and design of this code for us, =C2=A0he tells me that he has=C2=A0mul=
tiple available sources for the receive and transmit timestamps, each with =
a different=C2=A0associated resolution, precision, and run-time cost. =C2=
=A0 We are thinking that a sysctl will be provided to select the desired=C2=
=A0timestamp source.=C2=A0

=C2=A0
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360



________________________________
From: jouni korhonen <jouni.nospam@gmail.com>
To: General Area Review Team <gen-art@ietf.org>; draft-ietf-ippm-6man-pdm-o=
ption.all@ietf.org=20
Sent: Friday, September 23, 2016 11:14 AM
Subject: Gen-ART review of



I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-ippm-6man-pdm-option-05
Reviewer: Jouni Korhonen
Review Date: 9/23/2016
IETF LC End Date: 2016-09-28
IESG Telechat date: (if known)

Summary: The draft needs some work.

Major issues:


I have two technical issues here:


1) There is no mention of what is the time reference plane for internal tim=
e stamping. All other timing and synchronization related documents I am awa=
re of (at least outside IETF) describe it very clearly where in the process=
ing/packet handling the time stamp is to be taken. Now the document gives m=
e no idea as an implementer where that should take place. At least it makes=
 it hard to calculate the *network* RTT precisely.


2) The PDM option relation to actual "server" time is somewhat confusing an=
d the 5-tuple does not allow me to detect the real relationship between the=
 server/application action that caused the generation of the packet and the=
 PDM within the packet. This is specifically an issue with transport/applic=
ation protocols that multiplex/interleave multiple application streams into=
 one transport. I have no idea of the actual individual application time si=
nce the packets get generated independent of the processing of a single thr=
ead. I would welcome some discussion around here. Section 1.4 last paragrap=
h is going to this direction but is not sufficient IMHO.


Minor issues:


1) This is a larger editorial issue. The document is far too long with a lo=
t of repetition considering it describes only one IPv6 destination option. =
It is a writing style issue and I am fully aware of that. I have proposals =
how to cut text in the editorial comments section.


2) Section 1.2 3rd paragraph talks about IoT and that speed matters there. =
I find this too generalized statement. There are many other things that mat=
ter in this application domain and speed might not be that important as bei=
ng able to send/receive that one to two bytes of data in a given time windo=
w. I suggest removing this paragraph.


Nits/editorial comments:


1) Section 1.4 numbered list: add missing full stops.


2) Section 3.2: remove
=C2=A0 "The 5-tuple consists of
=C2=A0=C2=A0 the source and destination IP addresses, the source and destin=
ation
=C2=A0=C2=A0 ports, and the upper layer protocol (ex. TCP, ICMP, etc)."

since this is unnecessary repetition.

3) Section 3.2: remove
=C2=A0 "Operating systems MUST NOT implement a single
=C2=A0=C2=A0 counter for all connections."

Seems again like unnecessary repetition to previous sentence.


4) Section 3.2 again unnecessary repetition of IPv6 basics that can be read=
 from RFC2460. Suggest strongly to remove:
=C2=A0 "This indicates the
=C2=A0=C2=A0 following processing requirements:

=C2=A0=C2=A0 00 - skip over this option and continue processing the header.

=C2=A0=C2=A0 RFC2460 [RFC2460] defines other values for the Option Type fie=
ld.
=C2=A0=C2=A0 These MUST NOT be used in the PDM."


and

=C2=A0 "The
=C2=A0=C2=A0 possible values are as follows:

=C2=A0=C2=A0 0 - Option Data does not change en-route

=C2=A0=C2=A0 1 - Option Data may change en-route

=C2=A0=C2=A0 The three high-order bits described above are to be treated as=
 part
=C2=A0=C2=A0 of the Option Type, not independent of the Option Type.=C2=A0 =
That is, a
=C2=A0=C2=A0 particular option is identified by a full 8-bit Option Type, n=
ot just
=C2=A0=C2=A0 the low-order 5 bits of an Option Type."


5) Section 3.3 same as in comment 4). Suggest strongly removing:
=C2=A0 "This follows the order defined in RFC2460 [RFC2460]
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 IPv6 header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Hop-by-Hop Options header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header=C2=A0 <--------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Routing header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Fragment header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Authentication header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Encapsulating Security Payload header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header <------------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 upper-layer header"


6) Suggest removing entire Section 3.4 and moving the following text to Sec=
tion 3.3:
=C2=A0 "PDM MUST be placed before the ESP header in
=C2=A0=C2=A0 order to work.=C2=A0 If placed before the ESP header, the PDM =
header will
=C2=A0=C2=A0 flow in the clear over the network thus allowing gathering of
=C2=A0=C2=A0 performance and diagnostic data without sacrificing security."


7) Section 3.6 suggest removing the following text. I see no value it would=
 add to what has already been said:
=C2=A0 "As with all other destination options extension headers, the PDM is
=C2=A0=C2=A0 for destination nodes only. As specified above, intermediate d=
evices
=C2=A0=C2=A0 MUST neither set nor modify this field."


8) Section 3.6 suggest removing the following 5-tuple text as it has alread=
y been described earlier in Section 2:
=C2=A0 "The 5-tuple is:

=C2=A0=C2=A0 SADDR : IP address of the sender SPORT : Port for sender DADDR=
 : IP
=C2=A0=C2=A0 address of the destination DPORT : Port for destination PROTC =
:
=C2=A0=C2=A0 Protocol for upper layer (ex. TCP, UDP, ICMP)"


9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value th=
ese sections add. I acknowledge they are good to know information of timer =
hardware implementation difference but do not really add value on the on-wi=
re encoding of the PDM option.


10) Section 4.4 suggest removing the entire section. Time Base was already =
described in detail enough in Section 3.2.


11) Section 4.5 time base for picoseconds is 11 not 00.


12) Section 4.5 suggest removing the following text, since it does not add =
any more clarity to what has already been said in my opinion. This is becau=
se all the examples follow nice nybble increment in scaling:
=C2=A0 "Sample binary values (high order 16 bits taken)

=C2=A0=C2=A0 1 psec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0001
=C2=A0=C2=A0 1 nsec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3=
E8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1110 1=
000
=C2=A0=C2=A0 1 usec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 F4240=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1111 =
0100 0010 0100 0000
=C2=A0=C2=A0 1 msec=C2=A0=C2=A0=C2=A0=C2=A0 3B9ACA00=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1011 1001 1010 1100 1010 0000 =
0000
=C2=A0=C2=A0 1 sec=C2=A0=C2=A0=C2=A0 E8D4A51000 1110 1000 1101 0100 1010 01=
01 0001 0000 0000 0000"


12) Section 4.6 I do not understand why this section is here. I strongly su=
ggest removing it. Sections 4.5 and 3.2 already describe how I would encode=
 the delta time using scaling as a separate fields not embedded (option fie=
lds ScaleDTLR and ScaleDTLS). Did I misunderstand something here?


13) Section 5 suggest removing the following text because of it repeating w=
hat has already been said earlier:
=C2=A0 "Each packet, in addition to the PDM contains information on the
=C2=A0=C2=A0 sender and receiver. As discussed before, a 5-tuple consists o=
f:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SADDR : IP address of the sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SPORT : Port for sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DADDR : IP address of the destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DPORT : Port for destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PROTC : Protocol for upper layer (ex. TCP, U=
DP, ICMP)

=C2=A0=C2=A0 It should be understood that the packet identification informa=
tion is
=C2=A0=C2=A0 in each packet. We will not repeat that in each of the followi=
ng
=C2=A0=C2=A0 steps."


14) Section 5.3 suggest merging the following text into one example and do =
necessary rewording. There is no need to do the same calculation twice on a=
lmost adjacent lines:

=C2=A0 "Sending time : packet 2 - receive time : packet 1

=C2=A0=C2=A0 We will call the result of this calculation: Delta Time Last R=
eceived
=C2=A0=C2=A0 (DELTATLR)

=C2=A0=C2=A0 That is:

=C2=A0=C2=A0 Delta Time Last Received =3D (Sending time: packet 2 - receive=
 time:
=C2=A0=C2=A0 packet 1)"


15) Expand RTT and PSN on their first use.


Phew.. after all this I found the document good reading and most likely a u=
seful tool to be used.


Regards,

=C2=A0=C2=A0 Jouni
------=_Part_632080_2137494313.1487514414993
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px">Jouni,<br><br>We hav=
e finished with the comments from the Security Area (I believe!) and are no=
w starting on the comments from you.<br><br>There is a new draft which has =
the latest changes incorporated.<br><br>https://datatracker.ietf.org/doc/dr=
aft-ietf-ippm-6man-pdm-option/<br><br>I wanted to start a thread for each o=
f your major comments so that we could concentrate on each and resolve them=
.<br><br>So, major comment #1 from you:<br><br>&gt;1) There is no mention o=
f what is the time reference plane for internal time stamping. All other ti=
ming and synchronization related documents I am aware of (at least &gt;outs=
ide IETF) describe it very clearly where in the processing/packet handling =
the time stamp is to be taken. Now the document gives me no idea as an impl=
ementer &gt;where that should take place. At least it makes it hard to calc=
ulate the *network* RTT precisely.<br><br><div id=3D"yui_3_16_0_ym19_1_1487=
513138294_17731">I believe you are asking where the timestamp should be tak=
en in the implementation. &nbsp; Please let me know if I am misunderstandin=
g your question.</div><div id=3D"yui_3_16_0_ym19_1_1487513138294_17730"><br=
></div><div id=3D"yui_3_16_0_ym19_1_1487513138294_17359">In rough terms,&nb=
sp;<span style=3D"font-family: HelveticaNeue-Light, &quot;Helvetica Neue Li=
ght&quot;, &quot;Helvetica Neue&quot;, Helvetica, Arial, &quot;Lucida Grand=
e&quot;, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_148751313829=
4_17358">we want to capture the current time as soon as a packet arrives an=
d &lt;quickly&gt; perform any required calculations. Similarly, we want to =
capture the time and &lt;again, quickly&gt; perform delta-time-sent as late=
 as possible before the packet is sent.</span></div><div id=3D"yui_3_16_0_y=
m19_1_1487513138294_17359"><span style=3D"font-family: HelveticaNeue-Light,=
 &quot;Helvetica Neue Light&quot;, &quot;Helvetica Neue&quot;, Helvetica, A=
rial, &quot;Lucida Grande&quot;, sans-serif; font-size: 16px;"><br></span><=
/div><div id=3D"yui_3_16_0_ym19_1_1487513138294_17359"><span style=3D"font-=
family: HelveticaNeue-Light, &quot;Helvetica Neue Light&quot;, &quot;Helvet=
ica Neue&quot;, Helvetica, Arial, &quot;Lucida Grande&quot;, sans-serif; fo=
nt-size: 16px;" id=3D"yui_3_16_0_ym19_1_1487513138294_17733">We can put som=
ething like that into the document somewhere. &nbsp;Of course, if the PDM h=
eader is encrypted, the encryption/decryption time becomes part of the tran=
sport time.</span></div><br>In talking this over with the developer working=
 on the prototype implementation and design of this code for us, &nbsp;he t=
ells me that he has&nbsp;multiple available sources for the receive and tra=
nsmit timestamps, each with a different&nbsp;associated resolution, precisi=
on, and run-time cost. &nbsp; We are thinking that a sysctl will be provide=
d to select the desired&nbsp;timestamp source.&nbsp;<br><br>&nbsp;<br>Thank=
s,<br><br>Nalini Elkins<br>Inside Products, Inc.<br>www.insidethestack.com<=
br>(831) 659-8360<br><br><br><br>________________________________<br>From: =
jouni korhonen &lt;jouni.nospam@gmail.com&gt;<br>To: General Area Review Te=
am &lt;gen-art@ietf.org&gt;; draft-ietf-ippm-6man-pdm-option.all@ietf.org <=
br>Sent: Friday, September 23, 2016 11:14 AM<br>Subject: Gen-ART review of<=
br><br><br><br>I am the assigned Gen-ART reviewer for this draft. The Gener=
al Area<br>Review Team (Gen-ART) reviews all IETF documents being processed=
<br>by the IESG for the IETF Chair. Please wait for direction from your<br>=
document shepherd or AD before posting a new version of the draft.<br><br>F=
or more information, please see the FAQ at<br><br>&lt;http://wiki.tools.iet=
f.org/ar ea/gen/trac/wiki/GenArtfaq&gt;.<br><br>Document: draft-ietf-ippm-6=
man-pdm-option-05<br>Reviewer: Jouni Korhonen<br>Review Date: 9/23/2016<br>=
IETF LC End Date: 2016-09-28<br>IESG Telechat date: (if known)<br><br>Summa=
ry: The draft needs some work.<br><br>Major issues:<br><br><br>I have two t=
echnical issues here:<br><br><br>1) There is no mention of what is the time=
 reference plane for internal time stamping. All other timing and synchroni=
zation related documents I am aware of (at least outside IETF) describe it =
very clearly where in the processing/packet handling the time stamp is to b=
e taken. Now the document gives me no idea as an implementer where that sho=
uld take place. At least it makes it hard to calculate the *network* RTT pr=
ecisely.<br><br><br>2) The PDM option relation to actual "server" time is s=
omewhat confusing and the 5-tuple does not allow me to detect the real rela=
tionship between the server/application action that caused the generation o=
f the packet and the PDM within the packet. This is specifically an issue w=
ith transport/application protocols that multiplex/interleave multiple appl=
ication streams into one transport. I have no idea of the actual individual=
 application time since the packets get generated independent of the proces=
sing of a single thread. I would welcome some discussion around here. Secti=
on 1.4 last paragraph is going to this direction but is not sufficient IMHO=
.<br><br><br>Minor issues:<br><br><br>1) This is a larger editorial issue. =
The document is far too long with a lot of repetition considering it descri=
bes only one IPv6 destination option. It is a writing style issue and I am =
fully aware of that. I have proposals how to cut text in the editorial comm=
ents section.<br><br><br>2) Section 1.2 3rd paragraph talks about IoT and t=
hat speed matters there. I find this too generalized statement. There are m=
any other things that matter in this application domain and speed might not=
 be that important as being able to send/receive that one to two bytes of d=
ata in a given time window. I suggest removing this paragraph.<br><br><br>N=
its/editorial comments:<br><br><br>1) Section 1.4 numbered list: add missin=
g full stops.<br><br><br>2) Section 3.2: remove<br>&nbsp; "The 5-tuple cons=
ists of<br>&nbsp;&nbsp; the source and destination IP addresses, the source=
 and destination<br>&nbsp;&nbsp; ports, and the upper layer protocol (ex. T=
CP, ICMP, etc)."<br><br>since this is unnecessary repetition.<br><br>3) Sec=
tion 3.2: remove<br>&nbsp; "Operating systems MUST NOT implement a single<b=
r>&nbsp;&nbsp; counter for all connections."<br><br>Seems again like unnece=
ssary repetition to previous sentence.<br><br><br>4) Section 3.2 again unne=
cessary repetition of IPv6 basics that can be read from RFC2460. Suggest st=
rongly to remove:<br>&nbsp; "This indicates the<br>&nbsp;&nbsp; following p=
rocessing requirements:<br><br>&nbsp;&nbsp; 00 - skip over this option and =
continue processing the header.<br><br>&nbsp;&nbsp; RFC2460 [RFC2460] defin=
es other values for the Option Type field.<br>&nbsp;&nbsp; These MUST NOT b=
e used in the PDM."<br><br><br>and<br><br>&nbsp; "The<br>&nbsp;&nbsp; possi=
ble values are as follows:<br><br>&nbsp;&nbsp; 0 - Option Data does not cha=
nge en-route<br><br>&nbsp;&nbsp; 1 - Option Data may change en-route<br><br=
>&nbsp;&nbsp; The three high-order bits described above are to be treated a=
s part<br>&nbsp;&nbsp; of the Option Type, not independent of the Option Ty=
pe.&nbsp; That is, a<br>&nbsp;&nbsp; particular option is identified by a f=
ull 8-bit Option Type, not just<br>&nbsp;&nbsp; the low-order 5 bits of an =
Option Type."<br><br><br>5) Section 3.3 same as in comment 4). Suggest stro=
ngly removing:<br>&nbsp; "This follows the order defined in RFC2460 [RFC246=
0]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hop-by=
-Hop Options header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Options header=
&nbsp; &lt;--------<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Routing header<br><br>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; Fragment header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authenticati=
on header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Encapsulating Security Payload heade=
r<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Options header &lt;------------<=
br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; upper-layer header"<br><br><br>6) Suggest remo=
ving entire Section 3.4 and moving the following text to Section 3.3:<br>&n=
bsp; "PDM MUST be placed before the ESP header in<br>&nbsp;&nbsp; order to =
work.&nbsp; If placed before the ESP header, the PDM header will<br>&nbsp;&=
nbsp; flow in the clear over the network thus allowing gathering of<br>&nbs=
p;&nbsp; performance and diagnostic data without sacrificing security."<br>=
<br><br>7) Section 3.6 suggest removing the following text. I see no value =
it would add to what has already been said:<br>&nbsp; "As with all other de=
stination options extension headers, the PDM is<br>&nbsp;&nbsp; for destina=
tion nodes only. As specified above, intermediate devices<br>&nbsp;&nbsp; M=
UST neither set nor modify this field."<br><br><br>8) Section 3.6 suggest r=
emoving the following 5-tuple text as it has already been described earlier=
 in Section 2:<br>&nbsp; "The 5-tuple is:<br><br>&nbsp;&nbsp; SADDR : IP ad=
dress of the sender SPORT : Port for sender DADDR : IP<br>&nbsp;&nbsp; addr=
ess of the destination DPORT : Port for destination PROTC :<br>&nbsp;&nbsp;=
 Protocol for upper layer (ex. TCP, UDP, ICMP)"<br><br><br>9) Sections 4.2 =
and 4.3 suggest removing them entirely. I see what value these sections add=
. I acknowledge they are good to know information of timer hardware impleme=
ntation difference but do not really add value on the on-wire encoding of t=
he PDM option.<br><br><br>10) Section 4.4 suggest removing the entire secti=
on. Time Base was already described in detail enough in Section 3.2.<br><br=
><br>11) Section 4.5 time base for picoseconds is 11 not 00.<br><br><br>12)=
 Section 4.5 suggest removing the following text, since it does not add any=
 more clarity to what has already been said in my opinion. This is because =
all the examples follow nice nybble increment in scaling:<br>&nbsp; "Sample=
 binary values (high order 16 bits taken)<br><br>&nbsp;&nbsp; 1 psec&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0001<br>&nbsp;&nbsp; 1 nsec&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3E8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1110 1000<br>&nbsp;&nbsp; 1 usec&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F4240&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1111 0100 0010 0100 0000<br>&nbsp;&n=
bsp; 1 msec&nbsp;&nbsp;&nbsp;&nbsp; 3B9ACA00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1011 1001 1010 1100 1010 0000 0000<br>&n=
bsp;&nbsp; 1 sec&nbsp;&nbsp;&nbsp; E8D4A51000 1110 1000 1101 0100 1010 0101=
 0001 0000 0000 0000"<br><br><br>12) Section 4.6 I do not understand why th=
is section is here. I strongly suggest removing it. Sections 4.5 and 3.2 al=
ready describe how I would encode the delta time using scaling as a separat=
e fields not embedded (option fields ScaleDTLR and ScaleDTLS). Did I misund=
erstand something here?<br><br><br>13) Section 5 suggest removing the follo=
wing text because of it repeating what has already been said earlier:<br>&n=
bsp; "Each packet, in addition to the PDM contains information on the<br>&n=
bsp;&nbsp; sender and receiver. As discussed before, a 5-tuple consists of:=
<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SADDR : IP address of the sender<br>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SPORT : Port for sender<br>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; DADDR : IP address of the destination<br>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; DPORT : Port for destination<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; P=
ROTC : Protocol for upper layer (ex. TCP, UDP, ICMP)<br><br>&nbsp;&nbsp; It=
 should be understood that the packet identification information is<br>&nbs=
p;&nbsp; in each packet. We will not repeat that in each of the following<b=
r>&nbsp;&nbsp; steps."<br><br><br>14) Section 5.3 suggest merging the follo=
wing text into one example and do necessary rewording. There is no need to =
do the same calculation twice on almost adjacent lines:<br><br>&nbsp; "Send=
ing time : packet 2 - receive time : packet 1<br><br>&nbsp;&nbsp; We will c=
all the result of this calculation: Delta Time Last Received<br>&nbsp;&nbsp=
; (DELTATLR)<br><br>&nbsp;&nbsp; That is:<br><br>&nbsp;&nbsp; Delta Time La=
st Received =3D (Sending time: packet 2 - receive time:<br>&nbsp;&nbsp; pac=
ket 1)"<br><br><br>15) Expand RTT and PSN on their first use.<br><br><br>Ph=
ew.. after all this I found the document good reading and most likely a use=
ful tool to be used.<br><br><br>Regards,<br><br>&nbsp;&nbsp; Jouni</div></b=
ody></html>
------=_Part_632080_2137494313.1487514414993--


From nobody Tue Feb 21 08:25:42 2017
Return-Path: <rbonica@juniper.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EEF1294C4; Tue, 21 Feb 2017 08:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHisB9ELCEfu; Tue, 21 Feb 2017 08:25:38 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0103.outbound.protection.outlook.com [104.47.42.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F364129512; Tue, 21 Feb 2017 08:25:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=I8+a3V/mNysIqnGxkoCfLwQFpUiVCGfkybFnnuB318E=; b=jX0CVC0ELW/ouH6UNp0ZuitBksO7nIPXwnKQC2eGLmJcXc6aUt/pwmBGnNqkbngSv5PhNg0GrkreL9wHaiw2TpsZnlDil2RQjplq00vP665kuTuaj2IKTKV2Y9+kbUayr54luOso9r0/1inapOcHOK+RGJUWxKAyou/OgbkqOro=
Received: from SN1PR0501MB2062.namprd05.prod.outlook.com (10.163.227.23) by SN1PR0501MB2064.namprd05.prod.outlook.com (10.163.227.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.7; Tue, 21 Feb 2017 16:25:37 +0000
Received: from SN1PR0501MB2062.namprd05.prod.outlook.com ([10.163.227.23]) by SN1PR0501MB2062.namprd05.prod.outlook.com ([10.163.227.23]) with mapi id 15.01.0933.011; Tue, 21 Feb 2017 16:25:37 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "Cerveny, Bill" <wcerveny@arbor.net>, Jari Arkko <jari.arkko@piuha.net>, Francis Dupont <Francis.Dupont@fdupont.fr>
Thread-Topic: [Gen-art] review of draft-ietf-bmwg-ipv6-nd-04.txt
Thread-Index: AQHSdmDkXttwFCNmI0WbP+T5kfo6IaFruMgAgAAoi4CAB+/VUA==
Date: Tue, 21 Feb 2017 16:25:37 +0000
Message-ID: <SN1PR0501MB2062B441CCE5AE24D389E4ACAE510@SN1PR0501MB2062.namprd05.prod.outlook.com>
References: <201701241633.v0OGXSBE087413@givry.fdupont.fr> <6D68BE00-1E51-44C4-BDC1-B2EDD7CA8AE3@piuha.net> <D2074128-83C3-4193-AF36-C524A348E232@arbor.net>
In-Reply-To: <D2074128-83C3-4193-AF36-C524A348E232@arbor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rbonica@juniper.net; 
x-originating-ip: [66.129.241.10]
x-ms-office365-filtering-correlation-id: 977d8cff-0e30-4f4e-9705-08d45a7644b8
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:SN1PR0501MB2064; 
x-microsoft-exchange-diagnostics: 1; SN1PR0501MB2064; 7:UVhSQnUlxrUu94GU+OArumwxa9sCpP8TZR2L8JxP/FWfuREE6oGGsyal0vLbDNlnVlg+mLeZGuNkqmmpWEMZq6HzP9VdExDnMYSkC8Q4JtRJdW2OaYRLxWFDxdg9T+vZ3ey2MoXq2Sz3DeWnqjy/lLIYh0ByvmZ3EgqzUnLcP7x4sGyK5XRCr5TO/n6/LKLH3lXMqpkFoQq8sq3VmWFdI1f5lY10TL5x/czPLeNYA14A8GwnuUxdlk/8DS9cKoJEWByiTSalK8xy9HRt3KQVIc2pdFKnx90TNwccoL1M2T5SqLsfLipds9lJ/MogSV/PMsUsEbWNn6W+BNn0y54Rwg==
x-microsoft-antispam-prvs: <SN1PR0501MB2064D0E7DCCCAB0DDAB4C7A8AE510@SN1PR0501MB2064.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:SN1PR0501MB2064; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB2064; 
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39850400002)(39860400002)(39450400003)(39840400002)(39410400002)(377454003)(189002)(199003)(24454002)(51914003)(13464003)(54356999)(6116002)(54906002)(122556002)(7736002)(189998001)(66066001)(102836003)(50986999)(76176999)(74316002)(53936002)(3846002)(305945005)(38730400002)(6306002)(6246003)(9686003)(53546006)(2906002)(86362001)(3280700002)(3660700001)(92566002)(2900100001)(105586002)(4326007)(106356001)(8676002)(68736007)(81166006)(81156014)(2950100002)(230783001)(8936002)(33656002)(5660300001)(6506006)(101416001)(25786008)(6436002)(77096006)(99286003)(229853002)(7696004)(97736004)(55016002)(106116001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0501MB2064; H:SN1PR0501MB2062.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Feb 2017 16:25:37.0265 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB2064
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/DolQgQHoFMsn0u5edDUIzfbRQOE>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-bmwg-ipv6-nd.all@ietf.org" <draft-ietf-bmwg-ipv6-nd.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-bmwg-ipv6-nd-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 16:25:40 -0000

RnJhbmNpcywNCg0KVGhhbmtzIGZvciB0aGUgY2FyZWZ1bCByZXZpZXcuIENhbiB5b3Ugc3VnZ2Vz
dCBhIGJldHRlciB0aXRsZT8NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IFJvbg0KDQpQLlMuIEkgaGF2ZSB3b3JrZWQgdGhlIG90aGVyIGNvbW1lbnRzIGludG8gdGhlIG5l
eHQgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPiBGcm9tOiBHZW4tYXJ0IFttYWlsdG86Z2VuLWFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBC
ZWhhbGYgT2YgQ2VydmVueSwgQmlsbA0KPiBTZW50OiBUaHVyc2RheSwgRmVicnVhcnkgMTYsIDIw
MTcgMTA6MTIgQU0NCj4gVG86IEphcmkgQXJra28gPGphcmkuYXJra29AcGl1aGEubmV0PjsgRnJh
bmNpcyBEdXBvbnQNCj4gPEZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnI+DQo+IENjOiBnZW4tYXJ0
QGlldGYub3JnOyBkcmFmdC1pZXRmLWJtd2ctaXB2Ni1uZC5hbGxAaWV0Zi5vcmcNCj4gU3ViamVj
dDogUmU6IFtHZW4tYXJ0XSByZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibXdnLWlwdjYtbmQtMDQudHh0
DQo+IA0KPiBIaSBKYXJpDQo+IA0KPiBJ4oCZbGwgcmV2aWV3IHRoZSBjb21tZW50cyBhbmQgcmVz
cG9uZCB0byB0aGVtLg0KPiANCj4gVGhhbmtzLA0KPiANCj4gQmlsbCBDZXJ2ZW55DQo+IA0KPiBP
biAyLzE2LzE3LCA3OjQ3IEFNLCAiSmFyaSBBcmtrbyIgPGphcmkuYXJra29AcGl1aGEubmV0PiB3
cm90ZToNCj4gDQo+ICAgICBUaGFua3MgZm9yIHRoZSBkZXRhaWxlZCByZXZpZXcsIEZyYW5jaXMh
DQo+IA0KPiAgICAgQXV0aG9ycyDigJQgZGlkIHlvdSBtYWtlIGEgbm90ZSBvZiB0aGUgY29tbWVu
dHM/IERpZCBub3Qgc2VlIGENCj4gcmVzcG9uc2XigKYNCj4gDQo+ICAgICBKYXJpDQo+IA0KPiAg
ICAgT24gMjQgSmFuIDIwMTcsIGF0IDE4OjMzLCBGcmFuY2lzIER1cG9udCA8RnJhbmNpcy5EdXBv
bnRAZmR1cG9udC5mcj4NCj4gd3JvdGU6DQo+IA0KPiAgICAgPiBJIGFtIHRoZSBhc3NpZ25lZCBH
ZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhDQo+ICAgICA+
IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBw
cm9jZXNzZWQNCj4gICAgID4gYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNl
IHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QNCj4gICAgID4gbGlrZSBhbnkgb3RoZXIgbGFzdCBj
YWxsIGNvbW1lbnRzLg0KPiAgICAgPg0KPiAgICAgPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxl
YXNlIHNlZSB0aGUgRkFRIGF0DQo+ICAgICA+DQo+ICAgICA+IDxodHRwczovL3RyYWMuaWV0Zi5v
cmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiAgICAgPg0KPiAgICAgPiBEb2N1bWVudDog
ZHJhZnQtaWV0Zi1ibXdnLWlwdjYtbmQtMDQudHh0DQo+ICAgICA+IFJldmlld2VyOiBGcmFuY2lz
IER1cG9udA0KPiAgICAgPiBSZXZpZXcgRGF0ZTogMjAxNzAxMTYNCj4gICAgID4gSUVURiBMQyBF
bmQgRGF0ZTogMjAxNzAxMjMNCj4gICAgID4gSUVTRyBUZWxlY2hhdCBkYXRlOiB1bmtub3duDQo+
ICAgICA+DQo+ICAgICA+IFN1bW1hcnk6IFJlYWR5IHdpdGggbml0cw0KPiAgICAgPg0KPiAgICAg
PiBNYWpvciBpc3N1ZXM6IG5vbmUNCj4gICAgID4NCj4gICAgID4gTWlub3IgaXNzdWVzOiB0aGUg
dGl0bGUgKGFuZCB0aGUgQWJzdHJhY3QpIGlzIGEgYml0IG1pc2xlYWRpbmc6IGl0IGlzDQo+ICAg
ICA+IG5vdCB0aGUgYmVuY2htYXJraW5nIG9mIHRoZSBORCBwcm90b2NvbCB3aGljaCBoYXMgfjEy
IGRpZmZlcmVudA0KPiAgICAgPiBmdW5jdGlvbnMgYnV0IHRoZSBiZW5jaG1hcmtpbmcgb2YgYSBw
YXJ0aWN1bGFyIGZ1bmN0aW9uIG9uIGEgcm91dGVyLg0KPiAgICAgPiBOb3cgaXQgaXMgdGhlIGNy
aXRpY2FsIG9uZSBzbyBteSBjb25jZXJuIGlzIG1vcmUgdGhlIGRvY3VtZW50IGlzDQo+ICAgICA+
IGxpbWl0ZWQgdG8gb25seSB0aGlzIG9uZS4uLg0KPiAgICAgPg0KPiAgICAgPiBOaXRzL2VkaXRv
cmlhbCBjb21tZW50czoNCj4gICAgID4gLSBUb0MgcGFnZSAyIGFuZCA3IHBhZ2UgMTI6IEFja25v
d2xlZGdlbWVudHMgLT4gQWNrbm93bGVkZ21lbnRzDQo+ICAgICA+DQo+ICAgICA+IC0gMSBwYWdl
IDI6IHRoZSBsaW1pdCB0byBhIHJvdXRlciBleHBsYWlucyB3aHkgdGhlIHZlcmIgc2VuZCBpcw0K
PiAgICAgPiAgcmVwbGFjZWQgYnkgZm9yd2FyZC4uLiBhbmQgd2h5IHRoZXJlIGlzIG5vdGhpbmcg
YWJvdXQgcmVkaXJlY3Rpb24NCj4gICAgID4NCj4gICAgID4gLSAxIHBhZ2UgMjogZGV0ZXJtaW5l
IHRoZSBJUHY2IG5leHQtaG9wJ3MgbGluay1sYXllciBhZGRyZXNzDQo+ICAgICA+ICAtPiBkZXRl
cm1pbmUgdGhlIG91dGdvaW5nIGludGVyZmFjZSBhbmQgdGhlIElQdjYgbmV4dC1ob3Ancw0KPiAg
ICAgPiAgIGxpbmstbGF5ZXIgYWRkcmVzcw0KPiAgICAgPg0KPiAgICAgPiAtIDIuMi4xIHBhZ2Ug
NTogZXQgY2V0ZXJhIC0+IGV0Yw0KPiAgICAgPg0KPiAgICAgPiAtIDMuMS4yIHBhZ2UgOSAodHdp
Y2UpIGFuZCAzLjIuMiBwYWdlIDEwOyByZWNpZXZlZCAtPiByZWNlaXZlZA0KPiAgICAgPg0KPiAg
ICAgPiAtIDMuMS4yIHBhZ2UgOTogSU1ITyB5b3Ugc2hvdWxkIGRlZmluZSB0aGUgImluaXRpYWwi
IHRlcm0gKGZvciBmaW5hbA0KPiAgICAgPiAgdGhlIG1lYW5pbmcgaXMgb2J2aW91cykNCj4gICAg
ID4NCj4gICAgID4gLSAzLjIuMSBwYWdlIDEwOiAoaS5lLixJUHY2IC0+IChpLmUuLCBJUHY2DQo+
ICAgICA+DQo+ICAgICA+IC0gMy4yLjIgcGFnZSAxMDogaW4gInBhY2tldHMtcmVjZWl2ZWQgd2ls
bCBlaXRoZXIgYmUNCj4gICAgID4gICBlcXVhbCB0byB6ZXJvIG9yIHBhY2tldHMtcmVjZWl2ZWQu
IiB0aGUgbGFzdCByZWNlaXZlZCAtPiBzZW50Lg0KPiAgICAgPg0KPiAgICAgPiBSZWdhcmRzDQo+
ICAgICA+DQo+ICAgICA+IEZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnINCj4gICAgID4NCj4gICAg
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gICAg
ID4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4gICAgID4gR2VuLWFydEBpZXRmLm9yZw0KPiAgICAg
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCj4gDQo+IA0K
PiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
R2VuLWFydCBtYWlsaW5nIGxpc3QNCj4gR2VuLWFydEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCg==


From nobody Tue Feb 21 09:59:49 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B4AD1294D7 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 09:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.785
X-Spam-Level: 
X-Spam-Status: No, score=-3.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTR6RyhqiGqz for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 09:59:45 -0800 (PST)
Received: from nm21-vm4.bullet.mail.gq1.yahoo.com (nm21-vm4.bullet.mail.gq1.yahoo.com [98.136.217.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B64B129465 for <gen-art@ietf.org>; Tue, 21 Feb 2017 09:59:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487699985; bh=Ria5aF+7vU6R9VaMl6d07nHKAZwrjYnuv+uuydQh3Ps=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=DB44xf9vH43kHrVN0bIbq96megmv7U8RRxcBxTSkXzWDGz2K6tpMZGATQp2s481jwrgxh9OdGfjd0QQZfNod69sNExnmrnvucqoOut727PHWD0rvSRemofb6piOLeadGZEh9uXxdco+VyQ4V+8bhEqHn2pzcg3aaHOvLZWUMm+f+Bw/bEdWimyqqSpYusp2oIO0qTRn+C86xoCsBCghpTlDDsK00S77lfxy0p0mJPx7D6NJPZZ3wzsDMaYLpwtXcYUq29pAn2nHlxn4YSkgoU3ez51vbsbem49dLpPKn296SRbMC4SuCNthc7OQHWwRp2DmREhK0xUeC2+vUsqkYfQ==
Received: from [98.137.12.60] by nm21.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 17:59:45 -0000
Received: from [98.137.12.229] by tm5.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 17:59:44 -0000
Received: from [127.0.0.1] by omp1037.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 17:59:44 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 890063.15142.bm@omp1037.mail.gq1.yahoo.com
X-YMail-OSG: xYutkpYVM1mlFK3mpOnJG9I8iQYfzdwEZCS_ZJphMR_RdoxOr9P.qxH7XljO1wJ d8RixJaaDKf38DAOg5QpmaRmMTG9MWBKF.sYHy1jV0XHANs5TM1GZ_xn91KGDZLutliPUMTBmXk. tU1wkBJbPbGgfhWYL03ZIwxIWRfQK6ayUWuUMNBpmvcktdCxkXhlxJQ0QEEQ9fOrIIVa5bIjNQmc INrYt6wM5WYbxInkMldsurPZ7MyHe.rWbnqDquyNZeSRIebBRT6rAK9z80LamYkuUpSaoZ1YTXg2 PmqkE0zIVmbUAC7CqgWQ5XXHZcSJlQpCGk8NTzcQr.9.QjliZ9jsofy.331bWCiSUwxXFzSxoiLG ssIRaUgVXuMwZTPTwmdcCvKP5tKWiN7OaCIIatAFpJf4KZcAHio4lez5ggTsYJHunjzMkm1pu917 9k6gi4Rj3UfCsyJZNox1fI_3RjhBFRriJNcVCMKv0QBV_.7tdA7zAHmI5gl_7mxo2y8qnKAnv0iV AdEHQSzASKM2kVlb68b7C4j1Nt2H0w.Iw.9mGf7dH9wtggA5jv9tmTYWITi6RUW8Pa8X1Wg--
Received: from jws300002.mail.gq1.yahoo.com by sendmailws130.mail.gq1.yahoo.com; Tue, 21 Feb 2017 17:59:44 +0000; 1487699984.153
Date: Tue, 21 Feb 2017 17:59:43 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: jouni korhonen <jouni.nospam@gmail.com>,  General Area Review Team <gen-art@ietf.org>,  "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>
Message-ID: <100465536.2630141.1487699983875@mail.yahoo.com>
In-Reply-To: <1332138488.632081.1487514414996@mail.yahoo.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2630139_637711418.1487699983871"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dSCWkJJRnrr0vEtafljsroZbIic>
Cc: Robert Hamilton <rhamilton@cas.org>, "MORTON ALFRED C \(AL\)" <acmorton@att.com>, Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 17:59:48 -0000

------=_Part_2630139_637711418.1487699983871
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Jouni,

Here is the thread for your second major comment:

Major comment #2 from you:

>2) The PDM option relation to actual "server" time is somewhat confusing a=
nd the 5-tuple does not allow me to detect the real relationship between th=
e >server/application action that caused the generation of the packet and t=
he PDM within the packet. This is specifically an issue with transport/appl=
ication protocols >that multiplex/interleave multiple application streams i=
nto one transport. I have no idea of the actual individual application time=
 since the packets get generated >independent of the processing of a single=
 thread. I would welcome some discussion around here. Section 1.4 last para=
graph is going to this direction but is not >sufficient IMHO.

Yes, you are, of course, correct that=C2=A0all traffic will flow between th=
e matching ports at the two endpoints. The 5-tuples will match regardless o=
f the application.

The thing is that we never intended that PDM would distinguish between appl=
ications using the same 5-tuple. =C2=A0That is, it is a feature, not a bug.

What PDM WILL tell you is whether the problem is in the network or the host=
. =C2=A0 =C2=A0In our experience, which is primarily on networks for large =
data centers, there is a different group which is involved to troubleshoot =
the problem depending on the nature of the problem. =C2=A0That is, do I get=
 the application developers on the line or the team that deals with the rou=
ters & infrastructure.

One of the important functions of=C2=A0PDM is to allow you to do quick tria=
ge so that you can get the right SWAT team going. =C2=A0 PDM does not tell =
you if the problem is in the IP stack or the application or buffer allocati=
on. =C2=A0 PDM also does not tell you which of the network segments or midd=
le boxes is at fault. =C2=A0The reason for PDM is to get the right speciali=
sts in place who can then be dispatched to investigate their area.

In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0 Both the network group and the application group have quite a few=
 specialized tools at their disposal to further investigate their own areas=
.

I am adding some of this verbiage to section 1.4. =C2=A0 Please see below:

CURRENT
-----------

1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). More=20
intermediate measurements may be needed if the host or network=20
discrimination is not sufficient. At the client, TCP/IP stack time=20
vs. application time may still need to be broken out by client=20
software.=20


NEW----
1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). =C2=A0That is,it =
is a fast way to do triage.
One of the important functions of PDM is to allow you to do quickly dispatc=
hthe right set of diagnosticians. =C2=A0Within network or server latency,th=
ere may be many components. =C2=A0The job of the diagnostician is to ruleea=
ch one out until the culprit is found.
How PDM fits into this diagnostic picture is that PDM will quickly tell=C2=
=A0you how to escalate. =C2=A0PDM will point to either the network area or =
theserver area. =C2=A0 Within the server latency,=C2=A0PDM does not tell yo=
u if the bottleneckis in the IP stack or the application or buffer allocati=
on.=C2=A0Within the network latency,=C2=A0PDM does not tell you which of th=
e network segments or middle boxes is at fault.=C2=A0
What PDM will tell you is whether the problem is in the network or the serv=
er. In our experience,=C2=A0there is often a different group which is invol=
ved to troubleshoot the problem depending on the=C2=A0nature of the problem=
. =C2=A0 That is, the problem may be escalated to the application developer=
sor the team that deals with the routers and infrastructure. =C2=A0Both the=
 network group and the=C2=A0application group have quite a few specialized =
tools at their disposal to further investigate theirown areas. =C2=A0 What =
is missing is the first step, which PDM provides.
In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0PDM is expected toreduce this time substantially.=C2=A0=C2=A0
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

________________________________

From: jouni korhonen <jouni.nospam@gmail.com>
To: General Area Review Team <gen-art@ietf.org>; draft-ietf-ippm-6man-pdm-o=
ption.all@ietf.org=20
Sent: Friday, September 23, 2016 11:14 AM
Subject: Gen-ART review of



I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-ippm-6man-pdm-option-05
Reviewer: Jouni Korhonen
Review Date: 9/23/2016
IETF LC End Date: 2016-09-28
IESG Telechat date: (if known)

Summary: The draft needs some work.

Major issues:


I have two technical issues here:


1) There is no mention of what is the time reference plane for internal tim=
e stamping. All other timing and synchronization related documents I am awa=
re of (at least outside IETF) describe it very clearly where in the process=
ing/packet handling the time stamp is to be taken. Now the document gives m=
e no idea as an implementer where that should take place. At least it makes=
 it hard to calculate the *network* RTT precisely.


2) The PDM option relation to actual "server" time is somewhat confusing an=
d the 5-tuple does not allow me to detect the real relationship between the=
 server/application action that caused the generation of the packet and the=
 PDM within the packet. This is specifically an issue with transport/applic=
ation protocols that multiplex/interleave multiple application streams into=
 one transport. I have no idea of the actual individual application time si=
nce the packets get generated independent of the processing of a single thr=
ead. I would welcome some discussion around here. Section 1.4 last paragrap=
h is going to this direction but is not sufficient IMHO.


Minor issues:


1) This is a larger editorial issue. The document is far too long with a lo=
t of repetition considering it describes only one IPv6 destination option. =
It is a writing style issue and I am fully aware of that. I have proposals =
how to cut text in the editorial comments section.


2) Section 1.2 3rd paragraph talks about IoT and that speed matters there. =
I find this too generalized statement. There are many other things that mat=
ter in this application domain and speed might not be that important as bei=
ng able to send/receive that one to two bytes of data in a given time windo=
w. I suggest removing this paragraph.


Nits/editorial comments:


1) Section 1.4 numbered list: add missing full stops.


2) Section 3.2: remove
=C2=A0 "The 5-tuple consists of
=C2=A0=C2=A0 the source and destination IP addresses, the source and destin=
ation
=C2=A0=C2=A0 ports, and the upper layer protocol (ex. TCP, ICMP, etc)."

since this is unnecessary repetition.

3) Section 3.2: remove
=C2=A0 "Operating systems MUST NOT implement a single
=C2=A0=C2=A0 counter for all connections."

Seems again like unnecessary repetition to previous sentence.


4) Section 3.2 again unnecessary repetition of IPv6 basics that can be read=
 from RFC2460. Suggest strongly to remove:
=C2=A0 "This indicates the
=C2=A0=C2=A0 following processing requirements:

=C2=A0=C2=A0 00 - skip over this option and continue processing the header.

=C2=A0=C2=A0 RFC2460 [RFC2460] defines other values for the Option Type fie=
ld.
=C2=A0=C2=A0 These MUST NOT be used in the PDM."


and

=C2=A0 "The
=C2=A0=C2=A0 possible values are as follows:

=C2=A0=C2=A0 0 - Option Data does not change en-route

=C2=A0=C2=A0 1 - Option Data may change en-route

=C2=A0=C2=A0 The three high-order bits described above are to be treated as=
 part
=C2=A0=C2=A0 of the Option Type, not independent of the Option Type.=C2=A0 =
That is, a
=C2=A0=C2=A0 particular option is identified by a full 8-bit Option Type, n=
ot just
=C2=A0=C2=A0 the low-order 5 bits of an Option Type."


5) Section 3.3 same as in comment 4). Suggest strongly removing:
=C2=A0 "This follows the order defined in RFC2460 [RFC2460]
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 IPv6 header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Hop-by-Hop Options header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header=C2=A0 <--------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Routing header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Fragment header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Authentication header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Encapsulating Security Payload header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header <------------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 upper-layer header"


6) Suggest removing entire Section 3.4 and moving the following text to Sec=
tion 3.3:
=C2=A0 "PDM MUST be placed before the ESP header in
=C2=A0=C2=A0 order to work.=C2=A0 If placed before the ESP header, the PDM =
header will
=C2=A0=C2=A0 flow in the clear over the network thus allowing gathering of
=C2=A0=C2=A0 performance and diagnostic data without sacrificing security."


7) Section 3.6 suggest removing the following text. I see no value it would=
 add to what has already been said:
=C2=A0 "As with all other destination options extension headers, the PDM is
=C2=A0=C2=A0 for destination nodes only. As specified above, intermediate d=
evices
=C2=A0=C2=A0 MUST neither set nor modify this field."


8) Section 3.6 suggest removing the following 5-tuple text as it has alread=
y been described earlier in Section 2:
=C2=A0 "The 5-tuple is:

=C2=A0=C2=A0 SADDR : IP address of the sender SPORT : Port for sender DADDR=
 : IP
=C2=A0=C2=A0 address of the destination DPORT : Port for destination PROTC =
:
=C2=A0=C2=A0 Protocol for upper layer (ex. TCP, UDP, ICMP)"


9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value th=
ese sections add. I acknowledge they are good to know information of timer =
hardware implementation difference but do not really add value on the on-wi=
re encoding of the PDM option.


10) Section 4.4 suggest removing the entire section. Time Base was already =
described in detail enough in Section 3.2.


11) Section 4.5 time base for picoseconds is 11 not 00.


12) Section 4.5 suggest removing the following text, since it does not add =
any more clarity to what has already been said in my opinion. This is becau=
se all the examples follow nice nybble increment in scaling:
=C2=A0 "Sample binary values (high order 16 bits taken)

=C2=A0=C2=A0 1 psec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0001
=C2=A0=C2=A0 1 nsec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3=
E8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1110 1=
000
=C2=A0=C2=A0 1 usec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 F4240=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1111 =
0100 0010 0100 0000
=C2=A0=C2=A0 1 msec=C2=A0=C2=A0=C2=A0=C2=A0 3B9ACA00=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1011 1001 1010 1100 1010 0000 =
0000
=C2=A0=C2=A0 1 sec=C2=A0=C2=A0=C2=A0 E8D4A51000 1110 1000 1101 0100 1010 01=
01 0001 0000 0000 0000"


12) Section 4.6 I do not understand why this section is here. I strongly su=
ggest removing it. Sections 4.5 and 3.2 already describe how I would encode=
 the delta time using scaling as a separate fields not embedded (option fie=
lds ScaleDTLR and ScaleDTLS). Did I misunderstand something here?


13) Section 5 suggest removing the following text because of it repeating w=
hat has already been said earlier:
=C2=A0 "Each packet, in addition to the PDM contains information on the
=C2=A0=C2=A0 sender and receiver. As discussed before, a 5-tuple consists o=
f:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SADDR : IP address of the sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SPORT : Port for sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DADDR : IP address of the destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DPORT : Port for destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PROTC : Protocol for upper layer (ex. TCP, U=
DP, ICMP)

=C2=A0=C2=A0 It should be understood that the packet identification informa=
tion is
=C2=A0=C2=A0 in each packet. We will not repeat that in each of the followi=
ng
=C2=A0=C2=A0 steps."


14) Section 5.3 suggest merging the following text into one example and do =
necessary rewording. There is no need to do the same calculation twice on a=
lmost adjacent lines:

=C2=A0 "Sending time : packet 2 - receive time : packet 1

=C2=A0=C2=A0 We will call the result of this calculation: Delta Time Last R=
eceived
=C2=A0=C2=A0 (DELTATLR)

=C2=A0=C2=A0 That is:

=C2=A0=C2=A0 Delta Time Last Received =3D (Sending time: packet 2 - receive=
 time:
=C2=A0=C2=A0 packet 1)"


15) Expand RTT and PSN on their first use.


Phew.. after all this I found the document good reading and most likely a u=
seful tool to be used.


Regards,

=C2=A0=C2=A0 Jouni
------=_Part_2630139_637711418.1487699983871
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px">Jouni,<br><br>Here i=
s the thread for your second major comment:<br><br>Major comment #2 from yo=
u:<br><br>&gt;2) The PDM option relation to actual "server" time is somewha=
t confusing and the 5-tuple does not allow me to detect the real relationsh=
ip between the &gt;server/application action that caused the generation of =
the packet and the PDM within the packet. This is specifically an issue wit=
h transport/application protocols &gt;that multiplex/interleave multiple ap=
plication streams into one transport. I have no idea of the actual individu=
al application time since the packets get generated &gt;independent of the =
processing of a single thread. I would welcome some discussion around here.=
 Section 1.4 last paragraph is going to this direction but is not &gt;suffi=
cient IMHO.<br><br>Yes, you are, of course, correct that&nbsp;all traffic w=
ill flow between the matching ports at the two endpoints. The 5-tuples will=
 match regardless of the application.<br><br>The thing is that we never int=
ended that PDM would distinguish between applications using the same 5-tupl=
e. &nbsp;That is, it is a feature, not a bug.<br><br>What PDM WILL tell you=
 is whether the problem is in the network or the host. &nbsp; &nbsp;In our =
experience, which is primarily on networks for large data centers, there is=
 a different group which is involved to troubleshoot the problem depending =
on the nature of the problem. &nbsp;That is, do I get the application devel=
opers on the line or the team that deals with the routers &amp; infrastruct=
ure.<br><br>One of the important functions of&nbsp;PDM is to allow you to d=
o quick triage so that you can get the right SWAT team going. &nbsp; PDM do=
es not tell you if the problem is in the IP stack or the application or buf=
fer allocation. &nbsp; PDM also does not tell you which of the network segm=
ents or middle boxes is at fault. &nbsp;The reason for PDM is to get the ri=
ght specialists in place who can then be dispatched to investigate their ar=
ea.<br><br>In our experience, valuable time is often lost at this first sta=
ge of triage. &nbsp; Both the network group and the application group have =
quite a few specialized tools at their disposal to further investigate thei=
r own areas.<br><br>I am adding some of this verbiage to section 1.4. &nbsp=
; Please see below:<br><br>CURRENT<br>-----------<br><br>1.4 Rationale for =
defined solution <br><br>The current IPv6 specification does not provide ti=
ming nor a similar <br>field in the IPv6 main header or in any extension he=
ader. So, we <br>define the IPv6 Performance and Diagnostic Metrics destina=
tion option <br>(PDM). <br><br>Advantages include: <br><br>1.  Real measure=
 of actual transactions. <br>2.  Independence from transport layer protocol=
s. <br>3.  Ability to span organizational boundaries with consistent <br>in=
strumentation <br>4.  No time synchronization needed between session partne=
rs <br>5.  Ability to handle all transport protocols (TCP, UDP, SCTP, etc) =
<br>in a uniform way <br><br>The PDM provides the ability to determine quic=
kly if the (latency) <br>problem is in the network or in the server (applic=
ation).  More <br>intermediate measurements may be needed if the host or ne=
twork <br>discrimination is not sufficient.  At the client, TCP/IP stack ti=
me <br>vs. application time may still need to be broken out by client <br>s=
oftware. <br><div id=3D"yui_3_16_0_ym19_1_1487697725733_31288"><br></div><d=
iv><br></div><div id=3D"yui_3_16_0_ym19_1_1487697725733_31289">NEW</div><di=
v id=3D"yui_3_16_0_ym19_1_1487697725733_31290">----</div><div id=3D"yui_3_1=
6_0_ym19_1_1487697725733_31293"><br></div><div id=3D"yui_3_16_0_ym19_1_1487=
697725733_37838"><div id=3D"yui_3_16_0_ym19_1_1487697725733_31291">1.4 Rati=
onale for defined solution=20
<br>
<br>The current IPv6 specification does not provide timing nor a similar=20
<br>field in the IPv6 main header or in any extension header. So, we=20
<br>define the IPv6 Performance and Diagnostic Metrics destination option=
=20
<br>(PDM).=20
<br>
<br>Advantages include:=20
<br>
<br>1. Real measure of actual transactions.=20
<br>2. Independence from transport layer protocols.=20
<br>3. Ability to span organizational boundaries with consistent=20
<br>instrumentation=20
<br>4. No time synchronization needed between session partners=20
<br>5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
<br>in a uniform way=20
<br>
<br>The PDM provides the ability to determine quickly if the (latency)=20
<br>problem is in the network or in the server (application). &nbsp;That is=
,</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_31291">it is a fast way t=
o do triage.</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_31291"><br></d=
iv><div id=3D"yui_3_16_0_ym19_1_1487697725733_37839"><div id=3D"yui_3_16_0_=
ym19_1_1487697725733_33204">One of the important functions of PDM is to all=
ow you to do quickly dispatch</div><div id=3D"yui_3_16_0_ym19_1_14876977257=
33_33204">the right set of diagnosticians. &nbsp;Within network or server l=
atency,</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_33204">there may be=
 many components. &nbsp;The job of the diagnostician is to rule</div><div i=
d=3D"yui_3_16_0_ym19_1_1487697725733_33204">each one out until the culprit =
is found.</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_33204"><br></div>=
<div id=3D"yui_3_16_0_ym19_1_1487697725733_33204">How PDM fits into this di=
agnostic picture is that PDM will quickly tell&nbsp;</div><div id=3D"yui_3_=
16_0_ym19_1_1487697725733_33204">you how to escalate. &nbsp;PDM will point =
to either the network area or the</div><div id=3D"yui_3_16_0_ym19_1_1487697=
725733_33204">server area. &nbsp; Within the server latency,&nbsp;<span sty=
le=3D"font-family: HelveticaNeue-Light, &quot;Helvetica Neue Light&quot;, &=
quot;Helvetica Neue&quot;, Helvetica, Arial, &quot;Lucida Grande&quot;, san=
s-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1487697725733_37177">PDM=
 does not tell you if the bottleneck</span></div><div id=3D"yui_3_16_0_ym19=
_1_1487697725733_33204"><span style=3D"font-family: HelveticaNeue-Light, &q=
uot;Helvetica Neue Light&quot;, &quot;Helvetica Neue&quot;, Helvetica, Aria=
l, &quot;Lucida Grande&quot;, sans-serif; font-size: 16px;" id=3D"yui_3_16_=
0_ym19_1_1487697725733_37689">is in the IP stack or the application or buff=
er allocation.&nbsp;</span>Within the network latency,&nbsp;</div><div id=
=3D"yui_3_16_0_ym19_1_1487697725733_33204">PDM does not tell you which of t=
he network segments or middle boxes is at fault.&nbsp;</div><div id=3D"yui_=
3_16_0_ym19_1_1487697725733_33204"><br></div><div id=3D"yui_3_16_0_ym19_1_1=
487697725733_33204" dir=3D"ltr">What PDM will tell you is whether the probl=
em is in the network or the server. In our experience,&nbsp;</div><div id=
=3D"yui_3_16_0_ym19_1_1487697725733_33204" dir=3D"ltr">there is often a dif=
ferent group which is involved to troubleshoot the problem depending on the=
&nbsp;</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_33204" dir=3D"ltr">n=
ature of the problem. &nbsp; That is, the problem may be escalated to the a=
pplication developers</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_33204=
" dir=3D"ltr">or the team that deals with the routers and infrastructure. &=
nbsp;Both the network group and the&nbsp;</div><div id=3D"yui_3_16_0_ym19_1=
_1487697725733_33204" dir=3D"ltr">application group have quite a few specia=
lized tools at their disposal to further investigate their</div><div id=3D"=
yui_3_16_0_ym19_1_1487697725733_33204" dir=3D"ltr">own areas. &nbsp; What i=
s missing is the first step, which PDM provides.</div></div></div><div id=
=3D"yui_3_16_0_ym19_1_1487697725733_37854"><div id=3D"yui_3_16_0_ym19_1_148=
7697725733_33204" dir=3D"ltr"><br></div></div><div id=3D"yui_3_16_0_ym19_1_=
1487697725733_37863"><div id=3D"yui_3_16_0_ym19_1_1487697725733_31291" dir=
=3D"ltr"><div id=3D"yui_3_16_0_ym19_1_1487697725733_32708">In our experienc=
e, valuable time is often lost at this first stage of triage. &nbsp;PDM is =
expected to</div><div id=3D"yui_3_16_0_ym19_1_1487697725733_32708">reduce t=
his time substantially.&nbsp;</div><div id=3D"yui_3_16_0_ym19_1_14876977257=
33_32708">&nbsp;<br></div></div></div>Thanks,<br><br>Nalini Elkins<br>Insid=
e Products, Inc.<br>www.insidethestack.com<br>(831) 659-8360<br><br>_______=
_________________________<br><br>From: jouni korhonen &lt;jouni.nospam@gmai=
l.com&gt;<br>To: General Area Review Team &lt;gen-art@ietf.org&gt;; draft-i=
etf-ippm-6man-pdm-option.all@ietf.org <br>Sent: Friday, September 23, 2016 =
11:14 AM<br>Subject: Gen-ART review of<br><br><br><br>I am the assigned Gen=
-ART reviewer for this draft. The General Area<br>Review Team (Gen-ART) rev=
iews all IETF documents being processed<br>by the IESG for the IETF Chair. =
Please wait for direction from your<br>document shepherd or AD before posti=
ng a new version of the draft.<br><br>For more information, please see the =
FAQ at<br><br>&lt;http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq&=
gt;.<br><br>Document: draft-ietf-ippm-6man-pdm-option-05<br>Reviewer: Jouni=
 Korhonen<br>Review Date: 9/23/2016<br>IETF LC End Date: 2016-09-28<br>IESG=
 Telechat date: (if known)<br><br>Summary: The draft needs some work.<br><b=
r>Major issues:<br><br><br>I have two technical issues here:<br><br><br>1) =
There is no mention of what is the time reference plane for internal time s=
tamping. All other timing and synchronization related documents I am aware =
of (at least outside IETF) describe it very clearly where in the processing=
/packet handling the time stamp is to be taken. Now the document gives me n=
o idea as an implementer where that should take place. At least it makes it=
 hard to calculate the *network* RTT precisely.<br><br><br>2) The PDM optio=
n relation to actual "server" time is somewhat confusing and the 5-tuple do=
es not allow me to detect the real relationship between the server/applicat=
ion action that caused the generation of the packet and the PDM within the =
packet. This is specifically an issue with transport/application protocols =
that multiplex/interleave multiple application streams into one transport. =
I have no idea of the actual individual application time since the packets =
get generated independent of the processing of a single thread. I would wel=
come some discussion around here. Section 1.4 last paragraph is going to th=
is direction but is not sufficient IMHO.<br><br><br>Minor issues:<br><br><b=
r>1) This is a larger editorial issue. The document is far too long with a =
lot of repetition considering it describes only one IPv6 destination option=
. It is a writing style issue and I am fully aware of that. I have proposal=
s how to cut text in the editorial comments section.<br><br><br>2) Section =
1.2 3rd paragraph talks about IoT and that speed matters there. I find this=
 too generalized statement. There are many other things that matter in this=
 application domain and speed might not be that important as being able to =
send/receive that one to two bytes of data in a given time window. I sugges=
t removing this paragraph.<br><br><br>Nits/editorial comments:<br><br><br>1=
) Section 1.4 numbered list: add missing full stops.<br><br><br>2) Section =
3.2: remove<br>&nbsp; "The 5-tuple consists of<br>&nbsp;&nbsp; the source a=
nd destination IP addresses, the source and destination<br>&nbsp;&nbsp; por=
ts, and the upper layer protocol (ex. TCP, ICMP, etc)."<br><br>since this i=
s unnecessary repetition.<br><br>3) Section 3.2: remove<br>&nbsp; "Operatin=
g systems MUST NOT implement a single<br>&nbsp;&nbsp; counter for all conne=
ctions."<br><br>Seems again like unnecessary repetition to previous sentenc=
e.<br><br><br>4) Section 3.2 again unnecessary repetition of IPv6 basics th=
at can be read from RFC2460. Suggest strongly to remove:<br>&nbsp; "This in=
dicates the<br>&nbsp;&nbsp; following processing requirements:<br><br>&nbsp=
;&nbsp; 00 - skip over this option and continue processing the header.<br><=
br>&nbsp;&nbsp; RFC2460 [RFC2460] defines other values for the Option Type =
field.<br>&nbsp;&nbsp; These MUST NOT be used in the PDM."<br><br><br>and<b=
r><br>&nbsp; "The<br>&nbsp;&nbsp; possible values are as follows:<br><br>&n=
bsp;&nbsp; 0 - Option Data does not change en-route<br><br>&nbsp;&nbsp; 1 -=
 Option Data may change en-route<br><br>&nbsp;&nbsp; The three high-order b=
its described above are to be treated as part<br>&nbsp;&nbsp; of the Option=
 Type, not independent of the Option Type.&nbsp; That is, a<br>&nbsp;&nbsp;=
 particular option is identified by a full 8-bit Option Type, not just<br>&=
nbsp;&nbsp; the low-order 5 bits of an Option Type."<br><br><br>5) Section =
3.3 same as in comment 4). Suggest strongly removing:<br>&nbsp; "This follo=
ws the order defined in RFC2460 [RFC2460]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 hea=
der<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hop-by-Hop Options header<br><br>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; Destination Options header&nbsp; &lt;--------<br><br>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; Routing header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fragment header<br=
><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Authentication header<br><br>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Encapsulating Security Payload header<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Desti=
nation Options header &lt;------------<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upper-l=
ayer header"<br><br><br>6) Suggest removing entire Section 3.4 and moving t=
he following text to Section 3.3:<br>&nbsp; "PDM MUST be placed before the =
ESP header in<br>&nbsp;&nbsp; order to work.&nbsp; If placed before the ESP=
 header, the PDM header will<br>&nbsp;&nbsp; flow in the clear over the net=
work thus allowing gathering of<br>&nbsp;&nbsp; performance and diagnostic =
data without sacrificing security."<br><br><br>7) Section 3.6 suggest remov=
ing the following text. I see no value it would add to what has already bee=
n said:<br>&nbsp; "As with all other destination options extension headers,=
 the PDM is<br>&nbsp;&nbsp; for destination nodes only. As specified above,=
 intermediate devices<br>&nbsp;&nbsp; MUST neither set nor modify this fiel=
d."<br><br><br>8) Section 3.6 suggest removing the following 5-tuple text a=
s it has already been described earlier in Section 2:<br>&nbsp; "The 5-tupl=
e is:<br><br>&nbsp;&nbsp; SADDR : IP address of the sender SPORT : Port for=
 sender DADDR : IP<br>&nbsp;&nbsp; address of the destination DPORT : Port =
for destination PROTC :<br>&nbsp;&nbsp; Protocol for upper layer (ex. TCP, =
UDP, ICMP)"<br><br><br>9) Sections 4.2 and 4.3 suggest removing them entire=
ly. I see what value these sections add. I acknowledge they are good to kno=
w information of timer hardware implementation difference but do not really=
 add value on the on-wire encoding of the PDM option.<br><br><br>10) Sectio=
n 4.4 suggest removing the entire section. Time Base was already described =
in detail enough in Section 3.2.<br><br><br>11) Section 4.5 time base for p=
icoseconds is 11 not 00.<br><br><br>12) Section 4.5 suggest removing the fo=
llowing text, since it does not add any more clarity to what has already be=
en said in my opinion. This is because all the examples follow nice nybble =
increment in scaling:<br>&nbsp; "Sample binary values (high order 16 bits t=
aken)<br><br>&nbsp;&nbsp; 1 psec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0001=
<br>&nbsp;&nbsp; 1 nsec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 3E8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 111=
0 1000<br>&nbsp;&nbsp; 1 usec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F42=
40&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 1111 0100 0010 0100 0000<br>&nbsp;&nbsp; 1 msec&nbsp;&nbsp;&nbsp;&nbsp; =
3B9ACA00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1=
011 1001 1010 1100 1010 0000 0000<br>&nbsp;&nbsp; 1 sec&nbsp;&nbsp;&nbsp; E=
8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000"<br><br><br>12)=
 Section 4.6 I do not understand why this section is here. I strongly sugge=
st removing it. Sections 4.5 and 3.2 already describe how I would encode th=
e delta time using scaling as a separate fields not embedded (option fields=
 ScaleDTLR and ScaleDTLS). Did I misunderstand something here?<br><br><br>1=
3) Section 5 suggest removing the following text because of it repeating wh=
at has already been said earlier:<br>&nbsp; "Each packet, in addition to th=
e PDM contains information on the<br>&nbsp;&nbsp; sender and receiver. As d=
iscussed before, a 5-tuple consists of:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; SADDR : IP address of the sender<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SPORT=
 : Port for sender<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DADDR : IP address of =
the destination<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DPORT : Port for destinat=
ion<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PROTC : Protocol for upper layer (ex.=
 TCP, UDP, ICMP)<br><br>&nbsp;&nbsp; It should be understood that the packe=
t identification information is<br>&nbsp;&nbsp; in each packet. We will not=
 repeat that in each of the following<br>&nbsp;&nbsp; steps."<br><br><br>14=
) Section 5.3 suggest merging the following text into one example and do ne=
cessary rewording. There is no need to do the same calculation twice on alm=
ost adjacent lines:<br><br>&nbsp; "Sending time : packet 2 - receive time :=
 packet 1<br><br>&nbsp;&nbsp; We will call the result of this calculation: =
Delta Time Last Received<br>&nbsp;&nbsp; (DELTATLR)<br><br>&nbsp;&nbsp; Tha=
t is:<br><br>&nbsp;&nbsp; Delta Time Last Received =3D (Sending time: packe=
t 2 - receive time:<br>&nbsp;&nbsp; packet 1)"<br><br><br>15) Expand RTT an=
d PSN on their first use.<br><br><br>Phew.. after all this I found the docu=
ment good reading and most likely a useful tool to be used.<br><br><br>Rega=
rds,<br><br>&nbsp;&nbsp; Jouni</div></body></html>
------=_Part_2630139_637711418.1487699983871--


From nobody Tue Feb 21 10:06:22 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B151294D7 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 10:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.785
X-Spam-Level: 
X-Spam-Status: No, score=-1.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_PSBL=2.7, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0cP3FptzGVT for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 10:06:19 -0800 (PST)
Received: from nm48-vm10.bullet.mail.gq1.yahoo.com (nm48-vm10.bullet.mail.gq1.yahoo.com [67.195.87.230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7DE5129465 for <gen-art@ietf.org>; Tue, 21 Feb 2017 10:06:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487700377; bh=03kdsLN9eoPVePwRuKpp/PA7NjX3PjuF/RcYG8Mbx2g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=BH6QQiX8hgHcifmvNIb4Q6qM/IDJtZeYDE+CTn6lDho9HDxvDzmVAquwYqeMvQ4VPlK0/4U70Zf/DHcKhPrNJdEgacl+Al19rWNp22tmP6f1scrTv6xhjiXTmiWdRqG0tUIku3U7YWimsZB0m/tUSc7GjGmUdrt9Gt+FeLEHJ/LDYcgNDepVV91dAudGm2EeSGVOd0HkArcg9/eRyIzEokU/IEUucm0O2FdFYP9+vrlixAYgSuIyduF6fSqt+1rI2VIBHDZOF3ZjlQChu2MvjIWVGgsvgbIC8tJdzk+TNFFpKivv+Aaw0FUTECu7YkAMe4Ao6fTSc2YaoMpKwPEt4g==
Received: from [127.0.0.1] by nm48.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:06:17 -0000
Received: from [98.137.12.59] by nm48.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:03:35 -0000
Received: from [98.137.12.226] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:03:34 -0000
Received: from [127.0.0.1] by omp1034.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:03:34 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 905033.10287.bm@omp1034.mail.gq1.yahoo.com
X-YMail-OSG: eK82bHYVRDtgfAoCqOIpFuQf7CXNzbPmvwqKAF0E6WpCYH8GW8U-
Received: from jws300026.mail.gq1.yahoo.com by sendmailws777.mail.gq1.yahoo.com; Tue, 21 Feb 2017 18:03:34 +0000; 1487700214.454
Date: Tue, 21 Feb 2017 18:03:33 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: jouni korhonen <jouni.nospam@gmail.com>,  General Area Review Team <gen-art@ietf.org>,  "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>
Message-ID: <685542803.2622890.1487700213971@mail.yahoo.com>
In-Reply-To: <100465536.2630141.1487699983875@mail.yahoo.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com> <100465536.2630141.1487699983875@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2622889_1903105876.1487700213967"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/85b5FfbyxVBP5LEJJk_7UY_uxqA>
Cc: Robert Hamilton <rhamilton@cas.org>, "MORTON ALFRED C \(AL\)" <acmorton@att.com>, Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 18:06:20 -0000

------=_Part_2622889_1903105876.1487700213967
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Resending. =C2=A0Somehow the last email was cut off.=C2=A0Nalini=C2=A0
      From: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestac=
k.com>
 To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team <gen=
-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-=
ippm-6man-pdm-option.all@ietf.org>=20
Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@ca=
s.org>; MORTON ALFRED C (AL) <acmorton@att.com>
 Sent: Tuesday, February 21, 2017 9:59 AM
 Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Tim=
e
  =20
Jouni,

Here is the thread for your second major comment:

Major comment #2 from you:

>2) The PDM option relation to actual "server" time is somewhat confusing a=
nd the 5-tuple does not allow me to detect the real relationship between th=
e >server/application action that caused the generation of the packet and t=
he PDM within the packet. This is specifically an issue with transport/appl=
ication protocols >that multiplex/interleave multiple application streams i=
nto one transport. I have no idea of the actual individual application time=
 since the packets get generated >independent of the processing of a single=
 thread. I would welcome some discussion around here. Section 1.4 last para=
graph is going to this direction but is not >sufficient IMHO.

Yes, you are, of course, correct that=C2=A0all traffic will flow between th=
e matching ports at the two endpoints. The 5-tuples will match regardless o=
f the application.

The thing is that we never intended that PDM would distinguish between appl=
ications using the same 5-tuple. =C2=A0That is, it is a feature, not a bug.

What PDM WILL tell you is whether the problem is in the network or the host=
. =C2=A0 =C2=A0In our experience, which is primarily on networks for large =
data centers, there is a different group which is involved to troubleshoot =
the problem depending on the nature of the problem. =C2=A0That is, do I get=
 the application developers on the line or the team that deals with the rou=
ters & infrastructure.

One of the important functions of=C2=A0PDM is to allow you to do quick tria=
ge so that you can get the right SWAT team going. =C2=A0 PDM does not tell =
you if the problem is in the IP stack or the application or buffer allocati=
on. =C2=A0 PDM also does not tell you which of the network segments or midd=
le boxes is at fault. =C2=A0The reason for PDM is to get the right speciali=
sts in place who can then be dispatched to investigate their area.

In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0 Both the network group and the application group have quite a few=
 specialized tools at their disposal to further investigate their own areas=
.

I am adding some of this verbiage to section 1.4. =C2=A0 Please see below:

CURRENT
-----------

1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). More=20
intermediate measurements may be needed if the host or network=20
discrimination is not sufficient. At the client, TCP/IP stack time=20
vs. application time may still need to be broken out by client=20
software.=20


NEW----
1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). =C2=A0That is,it =
is a fast way to do triage.
One of the important functions of PDM is to allow you to do quickly dispatc=
hthe right set of diagnosticians. =C2=A0Within network or server latency,th=
ere may be many components. =C2=A0The job of the diagnostician is to ruleea=
ch one out until the culprit is found.
How PDM fits into this diagnostic picture is that PDM will quickly tell=C2=
=A0you how to escalate. =C2=A0PDM will point to either the network area or =
theserver area. =C2=A0 Within the server latency,=C2=A0PDM does not tell yo=
u if the bottleneckis in the IP stack or the application or buffer allocati=
on.=C2=A0Within the network latency,=C2=A0PDM does not tell you which of th=
e network segments or middle boxes is at fault.=C2=A0
What PDM will tell you is whether the problem is in the network or the serv=
er. In our experience,=C2=A0there is often a different group which is invol=
ved to troubleshoot the problem depending on the=C2=A0nature of the problem=
. =C2=A0 That is, the problem may be escalated to the application developer=
sor the team that deals with the routers and infrastructure. =C2=A0Both the=
 network group and the=C2=A0application group have quite a few specialized =
tools at their disposal to further investigate theirown areas. =C2=A0 What =
is missing is the first step, which PDM provides.
In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0PDM is expected toreduce this time substantially.=C2=A0=C2=A0
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

________________________________

From: jouni korhonen <jouni.nospam@gmail.com>
To: General Area Review Team <gen-art@ietf.org>; draft-ietf-ippm-6man-pdm-o=
ption.all@ietf.org=20
Sent: Friday, September 23, 2016 11:14 AM
Subject: Gen-ART review of



I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-ippm-6man-pdm-option-05
Reviewer: Jouni Korhonen
Review Date: 9/23/2016
IETF LC End Date: 2016-09-28
IESG Telechat date: (if known)

Summary: The draft needs some work.

Major issues:


I have two technical issues here:


1) There is no mention of what is the time reference plane for internal tim=
e stamping. All other timing and synchronization related documents I am awa=
re of (at least outside IETF) describe it very clearly where in the process=
ing/packet handling the time stamp is to be taken. Now the document gives m=
e no idea as an implementer where that should take place. At least it makes=
 it hard to calculate the *network* RTT precisely.


2) The PDM option relation to actual "server" time is somewhat confusing an=
d the 5-tuple does not allow me to detect the real relationship between the=
 server/application action that caused the generation of the packet and the=
 PDM within the packet. This is specifically an issue with transport/applic=
ation protocols that multiplex/interleave multiple application streams into=
 one transport. I have no idea of the actual individual application time si=
nce the packets get generated independent of the processing of a single thr=
ead. I would welcome some discussion around here. Section 1.4 last paragrap=
h is going to this direction but is not sufficient IMHO.


Minor issues:


1) This is a larger editorial issue. The document is far too long with a lo=
t of repetition considering it describes only one IPv6 destination option. =
It is a writing style issue and I am fully aware of that. I have proposals =
how to cut text in the editorial comments section.


2) Section 1.2 3rd paragraph talks about IoT and that speed matters there. =
I find this too generalized statement. There are many other things that mat=
ter in this application domain and speed might not be that important as bei=
ng able to send/receive that one to two bytes of data in a given time windo=
w. I suggest removing this paragraph.


Nits/editorial comments:


1) Section 1.4 numbered list: add missing full stops.


2) Section 3.2: remove
=C2=A0 "The 5-tuple consists of
=C2=A0=C2=A0 the source and destination IP addresses, the source and destin=
ation
=C2=A0=C2=A0 ports, and the upper layer protocol (ex. TCP, ICMP, etc)."

since this is unnecessary repetition.

3) Section 3.2: remove
=C2=A0 "Operating systems MUST NOT implement a single
=C2=A0=C2=A0 counter for all connections."

Seems again like unnecessary repetition to previous sentence.


4) Section 3.2 again unnecessary repetition of IPv6 basics that can be read=
 from RFC2460. Suggest strongly to remove:
=C2=A0 "This indicates the
=C2=A0=C2=A0 following processing requirements:

=C2=A0=C2=A0 00 - skip over this option and continue processing the header.

=C2=A0=C2=A0 RFC2460 [RFC2460] defines other values for the Option Type fie=
ld.
=C2=A0=C2=A0 These MUST NOT be used in the PDM."


and

=C2=A0 "The
=C2=A0=C2=A0 possible values are as follows:

=C2=A0=C2=A0 0 - Option Data does not change en-route

=C2=A0=C2=A0 1 - Option Data may change en-route

=C2=A0=C2=A0 The three high-order bits described above are to be treated as=
 part
=C2=A0=C2=A0 of the Option Type, not independent of the Option Type.=C2=A0 =
That is, a
=C2=A0=C2=A0 particular option is identified by a full 8-bit Option Type, n=
ot just
=C2=A0=C2=A0 the low-order 5 bits of an Option Type."


5) Section 3.3 same as in comment 4). Suggest strongly removing:
=C2=A0 "This follows the order defined in RFC2460 [RFC2460]
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 IPv6 header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Hop-by-Hop Options header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header=C2=A0 <--------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Routing header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Fragment header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Authentication header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Encapsulating Security Payload header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header <------------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 upper-layer header"


6) Suggest removing entire Section 3.4 and moving the following text to Sec=
tion 3.3:
=C2=A0 "PDM MUST be placed before the ESP header in
=C2=A0=C2=A0 order to work.=C2=A0 If placed before the ESP header, the PDM =
header will
=C2=A0=C2=A0 flow in the clear over the network thus allowing gathering of
=C2=A0=C2=A0 performance and diagnostic data without sacrificing security."


7) Section 3.6 suggest removing the following text. I see no value it would=
 add to what has already been said:
=C2=A0 "As with all other destination options extension headers, the PDM is
=C2=A0=C2=A0 for destination nodes only. As specified above, intermediate d=
evices
=C2=A0=C2=A0 MUST neither set nor modify this field."


8) Section 3.6 suggest removing the following 5-tuple text as it has alread=
y been described earlier in Section 2:
=C2=A0 "The 5-tuple is:

=C2=A0=C2=A0 SADDR : IP address of the sender SPORT : Port for sender DADDR=
 : IP
=C2=A0=C2=A0 address of the destination DPORT : Port for destination PROTC =
:
=C2=A0=C2=A0 Protocol for upper layer (ex. TCP, UDP, ICMP)"


9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value th=
ese sections add. I acknowledge they are good to know information of timer =
hardware implementation difference but do not really add value on the on-wi=
re encoding of the PDM option.


10) Section 4.4 suggest removing the entire section. Time Base was already =
described in detail enough in Section 3.2.


11) Section 4.5 time base for picoseconds is 11 not 00.


12) Section 4.5 suggest removing the following text, since it does not add =
any more clarity to what has already been said in my opinion. This is becau=
se all the examples follow nice nybble increment in scaling:
=C2=A0 "Sample binary values (high order 16 bits taken)

=C2=A0=C2=A0 1 psec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0001
=C2=A0=C2=A0 1 nsec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3=
E8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1110 1=
000
=C2=A0=C2=A0 1 usec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 F4240=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1111 =
0100 0010 0100 0000
=C2=A0=C2=A0 1 msec=C2=A0=C2=A0=C2=A0=C2=A0 3B9ACA00=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1011 1001 1010 1100 1010 0000 =
0000
=C2=A0=C2=A0 1 sec=C2=A0=C2=A0=C2=A0 E8D4A51000 1110 1000 1101 0100 1010 01=
01 0001 0000 0000 0000"


12) Section 4.6 I do not understand why this section is here. I strongly su=
ggest removing it. Sections 4.5 and 3.2 already describe how I would encode=
 the delta time using scaling as a separate fields not embedded (option fie=
lds ScaleDTLR and ScaleDTLS). Did I misunderstand something here?


13) Section 5 suggest removing the following text because of it repeating w=
hat has already been said earlier:
=C2=A0 "Each packet, in addition to the PDM contains information on the
=C2=A0=C2=A0 sender and receiver. As discussed before, a 5-tuple consists o=
f:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SADDR : IP address of the sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SPORT : Port for sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DADDR : IP address of the destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DPORT : Port for destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PROTC : Protocol for upper layer (ex. TCP, U=
DP, ICMP)

=C2=A0=C2=A0 It should be understood that the packet identification informa=
tion is
=C2=A0=C2=A0 in each packet. We will not repeat that in each of the followi=
ng
=C2=A0=C2=A0 steps."


14) Section 5.3 suggest merging the following text into one example and do =
necessary rewording. There is no need to do the same calculation twice on a=
lmost adjacent lines:

=C2=A0 "Sending time : packet 2 - receive time : packet 1

=C2=A0=C2=A0 We will call the result of this calculation: Delta Time Last R=
eceived
=C2=A0=C2=A0 (DELTATLR)

=C2=A0=C2=A0 That is:

=C2=A0=C2=A0 Delta Time Last Received =3D (Sending time: packet 2 - receive=
 time:
=C2=A0=C2=A0 packet 1)"


15) Expand RTT and PSN on their first use.


Phew.. after all this I found the document good reading and most likely a u=
seful tool to be used.


Regards,

=C2=A0=C2=A0 Jouni

  =20
------=_Part_2622889_1903105876.1487700213967
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1487699989064_29721">Resending. &nbsp;Somehow the last email was c=
ut off.</div><div></div><div id=3D"yui_3_16_0_ym19_1_1487699989064_29711">&=
nbsp;</div><div class=3D"signature" id=3D"yui_3_16_0_ym19_1_1487699989064_2=
9690">Nalini&nbsp;</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_=
1_1487699989064_29714"><br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16=
_0_ym19_1_1487699989064_29718" style=3D"display: block;">  <div style=3D"fo=
nt-family: HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_=
ym19_1_1487699989064_29717"> <div style=3D"font-family: HelveticaNeue, Helv=
etica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" =
id=3D"yui_3_16_0_ym19_1_1487699989064_29716"> <div dir=3D"ltr" id=3D"yui_3_=
16_0_ym19_1_1487699989064_29715"> <font size=3D"2" face=3D"Arial" id=3D"yui=
_3_16_0_ym19_1_1487699989064_29719"> <hr size=3D"1" id=3D"yui_3_16_0_ym19_1=
_1487699989064_29720"> <b><span style=3D"font-weight:bold;">From:</span></b=
> "nalini.elkins@insidethestack.com" &lt;nalini.elkins@insidethestack.com&g=
t;<br> <b><span style=3D"font-weight: bold;">To:</span></b> jouni korhonen =
&lt;jouni.nospam@gmail.com&gt;; General Area Review Team &lt;gen-art@ietf.o=
rg&gt;; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" &lt;draft-ietf-ippm-=
6man-pdm-option.all@ietf.org&gt; <br><b><span style=3D"font-weight: bold;">=
Cc:</span></b> Michael Ackermann &lt;mackermann@bcbsm.com&gt;; Robert Hamil=
ton &lt;rhamilton@cas.org&gt;; MORTON ALFRED C (AL) &lt;acmorton@att.com&gt=
;<br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Tuesday, Febru=
ary 21, 2017 9:59 AM<br> <b><span style=3D"font-weight: bold;">Subject:</sp=
an></b> Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option:  Server Time=
<br> </font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_=
1487699989064_29730"><br><div id=3D"yiv6333607819"><div id=3D"yui_3_16_0_ym=
19_1_1487699989064_29732"><div style=3D"color:#000;background-color:#fff;fo=
nt-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvet=
ica, Arial, Lucida Grande, sans-serif;font-size:16px;" id=3D"yui_3_16_0_ym1=
9_1_1487699989064_29731">Jouni,<br clear=3D"none"><br clear=3D"none">Here i=
s the thread for your second major comment:<br clear=3D"none"><br clear=3D"=
none">Major comment #2 from you:<br clear=3D"none"><br clear=3D"none">&gt;2=
) The PDM option relation to actual "server" time is somewhat confusing and=
 the 5-tuple does not allow me to detect the real relationship between the =
&gt;server/application action that caused the generation of the packet and =
the PDM within the packet. This is specifically an issue with transport/app=
lication protocols &gt;that multiplex/interleave multiple application strea=
ms into one transport. I have no idea of the actual individual application =
time since the packets get generated &gt;independent of the processing of a=
 single thread. I would welcome some discussion around here. Section 1.4 la=
st paragraph is going to this direction but is not &gt;sufficient IMHO.<br =
clear=3D"none"><br clear=3D"none">Yes, you are, of course, correct that&nbs=
p;all traffic will flow between the matching ports at the two endpoints. Th=
e 5-tuples will match regardless of the application.<br clear=3D"none"><br =
clear=3D"none">The thing is that we never intended that PDM would distingui=
sh between applications using the same 5-tuple. &nbsp;That is, it is a feat=
ure, not a bug.<br clear=3D"none"><br clear=3D"none">What PDM WILL tell you=
 is whether the problem is in the network or the host. &nbsp; &nbsp;In our =
experience, which is primarily on networks for large data centers, there is=
 a different group which is involved to troubleshoot the problem depending =
on the nature of the problem. &nbsp;That is, do I get the application devel=
opers on the line or the team that deals with the routers &amp; infrastruct=
ure.<br clear=3D"none"><br clear=3D"none">One of the important functions of=
&nbsp;PDM is to allow you to do quick triage so that you can get the right =
SWAT team going. &nbsp; PDM does not tell you if the problem is in the IP s=
tack or the application or buffer allocation. &nbsp; PDM also does not tell=
 you which of the network segments or middle boxes is at fault. &nbsp;The r=
eason for PDM is to get the right specialists in place who can then be disp=
atched to investigate their area.<br clear=3D"none"><br clear=3D"none">In o=
ur experience, valuable time is often lost at this first stage of triage. &=
nbsp; Both the network group and the application group have quite a few spe=
cialized tools at their disposal to further investigate their own areas.<br=
 clear=3D"none"><br clear=3D"none">I am adding some of this verbiage to sec=
tion 1.4. &nbsp; Please see below:<br clear=3D"none"><br clear=3D"none">CUR=
RENT<br clear=3D"none">-----------<br clear=3D"none"><br clear=3D"none">1.4=
 Rationale for defined solution <br clear=3D"none"><br clear=3D"none">The c=
urrent IPv6 specification does not provide timing nor a similar <br clear=
=3D"none">field in the IPv6 main header or in any extension header. So, we =
<br clear=3D"none">define the IPv6 Performance and Diagnostic Metrics desti=
nation option <br clear=3D"none">(PDM). <br clear=3D"none"><br clear=3D"non=
e">Advantages include: <br clear=3D"none"><br clear=3D"none">1.  Real measu=
re of actual transactions. <br clear=3D"none">2.  Independence from transpo=
rt layer protocols. <br clear=3D"none">3.  Ability to span organizational b=
oundaries with consistent <br clear=3D"none">instrumentation <br clear=3D"n=
one">4.  No time synchronization needed between session partners <br clear=
=3D"none">5.  Ability to handle all transport protocols (TCP, UDP, SCTP, et=
c) <br clear=3D"none">in a uniform way <br clear=3D"none"><br clear=3D"none=
">The PDM provides the ability to determine quickly if the (latency) <br cl=
ear=3D"none">problem is in the network or in the server (application).  Mor=
e <br clear=3D"none">intermediate measurements may be needed if the host or=
 network <br clear=3D"none">discrimination is not sufficient.  At the clien=
t, TCP/IP stack time <br clear=3D"none">vs. application time may still need=
 to be broken out by client <br clear=3D"none">software. <br clear=3D"none"=
><div id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_31288"><br clear=
=3D"none"></div><div><br clear=3D"none"></div><div id=3D"yiv6333607819yui_3=
_16_0_ym19_1_1487697725733_31289">NEW</div><div id=3D"yiv6333607819yui_3_16=
_0_ym19_1_1487697725733_31290">----</div><div id=3D"yiv6333607819yui_3_16_0=
_ym19_1_1487697725733_31293"><br clear=3D"none"></div><div id=3D"yiv6333607=
819yui_3_16_0_ym19_1_1487697725733_37838"><div id=3D"yiv6333607819yui_3_16_=
0_ym19_1_1487697725733_31291">1.4 Rationale for defined solution=20
<br clear=3D"none">
<br clear=3D"none">The current IPv6 specification does not provide timing n=
or a similar=20
<br clear=3D"none">field in the IPv6 main header or in any extension header=
. So, we=20
<br clear=3D"none">define the IPv6 Performance and Diagnostic Metrics desti=
nation option=20
<br clear=3D"none">(PDM).=20
<br clear=3D"none">
<br clear=3D"none">Advantages include:=20
<br clear=3D"none">
<br clear=3D"none">1. Real measure of actual transactions.=20
<br clear=3D"none">2. Independence from transport layer protocols.=20
<br clear=3D"none">3. Ability to span organizational boundaries with consis=
tent=20
<br clear=3D"none">instrumentation=20
<br clear=3D"none">4. No time synchronization needed between session partne=
rs=20
<br clear=3D"none">5. Ability to handle all transport protocols (TCP, UDP, =
SCTP, etc)=20
<br clear=3D"none">in a uniform way=20
<br clear=3D"none">
<br clear=3D"none">The PDM provides the ability to determine quickly if the=
 (latency)=20
<br clear=3D"none">problem is in the network or in the server (application)=
. &nbsp;That is,</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_14876977257=
33_31291">it is a fast way to do triage.</div><div id=3D"yiv6333607819yui_3=
_16_0_ym19_1_1487697725733_31291"><br clear=3D"none"></div><div id=3D"yiv63=
33607819yui_3_16_0_ym19_1_1487697725733_37839"><div id=3D"yiv6333607819yui_=
3_16_0_ym19_1_1487697725733_33204">One of the important functions of PDM is=
 to allow you to do quickly dispatch</div><div id=3D"yiv6333607819yui_3_16_=
0_ym19_1_1487697725733_33204">the right set of diagnosticians. &nbsp;Within=
 network or server latency,</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_=
1487697725733_33204">there may be many components. &nbsp;The job of the dia=
gnostician is to rule</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_148769=
7725733_33204">each one out until the culprit is found.</div><div id=3D"yiv=
6333607819yui_3_16_0_ym19_1_1487697725733_33204"><br clear=3D"none"></div><=
div id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_33204">How PDM fits =
into this diagnostic picture is that PDM will quickly tell&nbsp;</div><div =
id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_33204">you how to escala=
te. &nbsp;PDM will point to either the network area or the</div><div id=3D"=
yiv6333607819yui_3_16_0_ym19_1_1487697725733_33204">server area. &nbsp; Wit=
hin the server latency,&nbsp;<span id=3D"yiv6333607819yui_3_16_0_ym19_1_148=
7697725733_37177" style=3D"font-family:HelveticaNeue-Light,;">PDM does not =
tell you if the bottleneck</span></div><div id=3D"yiv6333607819yui_3_16_0_y=
m19_1_1487697725733_33204"><span id=3D"yiv6333607819yui_3_16_0_ym19_1_14876=
97725733_37689" style=3D"font-family:HelveticaNeue-Light,;">is in the IP st=
ack or the application or buffer allocation.&nbsp;</span>Within the network=
 latency,&nbsp;</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_148769772573=
3_33204">PDM does not tell you which of the network segments or middle boxe=
s is at fault.&nbsp;</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697=
725733_33204"><br clear=3D"none"></div><div dir=3D"ltr" id=3D"yiv6333607819=
yui_3_16_0_ym19_1_1487697725733_33204">What PDM will tell you is whether th=
e problem is in the network or the server. In our experience,&nbsp;</div><d=
iv dir=3D"ltr" id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_33204">th=
ere is often a different group which is involved to troubleshoot the proble=
m depending on the&nbsp;</div><div dir=3D"ltr" id=3D"yiv6333607819yui_3_16_=
0_ym19_1_1487697725733_33204">nature of the problem. &nbsp; That is, the pr=
oblem may be escalated to the application developers</div><div dir=3D"ltr" =
id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_33204">or the team that =
deals with the routers and infrastructure. &nbsp;Both the network group and=
 the&nbsp;</div><div dir=3D"ltr" id=3D"yiv6333607819yui_3_16_0_ym19_1_14876=
97725733_33204">application group have quite a few specialized tools at the=
ir disposal to further investigate their</div><div dir=3D"ltr" id=3D"yiv633=
3607819yui_3_16_0_ym19_1_1487697725733_33204">own areas. &nbsp; What is mis=
sing is the first step, which PDM provides.</div></div></div><div id=3D"yiv=
6333607819yui_3_16_0_ym19_1_1487697725733_37854"><div dir=3D"ltr" id=3D"yiv=
6333607819yui_3_16_0_ym19_1_1487697725733_33204"><br clear=3D"none"></div><=
/div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_37863"><div di=
r=3D"ltr" id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_31291"><div id=
=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_32708">In our experience, =
valuable time is often lost at this first stage of triage. &nbsp;PDM is exp=
ected to</div><div id=3D"yiv6333607819yui_3_16_0_ym19_1_1487697725733_32708=
">reduce this time substantially.&nbsp;</div><div class=3D"yiv6333607819yqt=
9051455253" id=3D"yiv6333607819yqtfd89895"><div id=3D"yiv6333607819yui_3_16=
_0_ym19_1_1487697725733_32708">&nbsp;<br clear=3D"none"></div></div></div><=
/div><div class=3D"yiv6333607819yqt9051455253" id=3D"yiv6333607819yqtfd5402=
4">Thanks,<br clear=3D"none"><br clear=3D"none">Nalini Elkins<br clear=3D"n=
one">Inside Products, Inc.<br clear=3D"none">www.insidethestack.com<br clea=
r=3D"none">(831) 659-8360<br clear=3D"none"><br clear=3D"none">____________=
____________________<br clear=3D"none"><br clear=3D"none">From: jouni korho=
nen &lt;jouni.nospam@gmail.com&gt;<br clear=3D"none">To: General Area Revie=
w Team &lt;gen-art@ietf.org&gt;; draft-ietf-ippm-6man-pdm-option.all@ietf.o=
rg <br clear=3D"none">Sent: Friday, September 23, 2016 11:14 AM<br clear=3D=
"none">Subject: Gen-ART review of<br clear=3D"none"><br clear=3D"none"><br =
clear=3D"none"><br clear=3D"none">I am the assigned Gen-ART reviewer for th=
is draft. The General Area<br clear=3D"none">Review Team (Gen-ART) reviews =
all IETF documents being processed<br clear=3D"none">by the IESG for the IE=
TF Chair. Please wait for direction from your<br clear=3D"none">document sh=
epherd or AD before posting a new version of the draft.<br clear=3D"none"><=
br clear=3D"none">For more information, please see the FAQ at<br clear=3D"n=
one"><br clear=3D"none">&lt;http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/=
GenArtfaq&gt;.<br clear=3D"none"><br clear=3D"none">Document: draft-ietf-ip=
pm-6man-pdm-option-05<br clear=3D"none">Reviewer: Jouni Korhonen<br clear=
=3D"none">Review Date: 9/23/2016<br clear=3D"none">IETF LC End Date: 2016-0=
9-28<br clear=3D"none">IESG Telechat date: (if known)<br clear=3D"none"><br=
 clear=3D"none">Summary: The draft needs some work.<br clear=3D"none"><br c=
lear=3D"none">Major issues:<br clear=3D"none"><br clear=3D"none"><br clear=
=3D"none">I have two technical issues here:<br clear=3D"none"><br clear=3D"=
none"><br clear=3D"none">1) There is no mention of what is the time referen=
ce plane for internal time stamping. All other timing and synchronization r=
elated documents I am aware of (at least outside IETF) describe it very cle=
arly where in the processing/packet handling the time stamp is to be taken.=
 Now the document gives me no idea as an implementer where that should take=
 place. At least it makes it hard to calculate the *network* RTT precisely.=
<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">2) The PDM option =
relation to actual "server" time is somewhat confusing and the 5-tuple does=
 not allow me to detect the real relationship between the server/applicatio=
n action that caused the generation of the packet and the PDM within the pa=
cket. This is specifically an issue with transport/application protocols th=
at multiplex/interleave multiple application streams into one transport. I =
have no idea of the actual individual application time since the packets ge=
t generated independent of the processing of a single thread. I would welco=
me some discussion around here. Section 1.4 last paragraph is going to this=
 direction but is not sufficient IMHO.<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">Minor issues:<br clear=3D"none"><br clear=3D"none"><br =
clear=3D"none">1) This is a larger editorial issue. The document is far too=
 long with a lot of repetition considering it describes only one IPv6 desti=
nation option. It is a writing style issue and I am fully aware of that. I =
have proposals how to cut text in the editorial comments section.<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">2) Section 1.2 3rd paragrap=
h talks about IoT and that speed matters there. I find this too generalized=
 statement. There are many other things that matter in this application dom=
ain and speed might not be that important as being able to send/receive tha=
t one to two bytes of data in a given time window. I suggest removing this =
paragraph.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">Nits/edi=
torial comments:<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">1)=
 Section 1.4 numbered list: add missing full stops.<br clear=3D"none"><br c=
lear=3D"none"><br clear=3D"none">2) Section 3.2: remove<br clear=3D"none">&=
nbsp; "The 5-tuple consists of<br clear=3D"none">&nbsp;&nbsp; the source an=
d destination IP addresses, the source and destination<br clear=3D"none">&n=
bsp;&nbsp; ports, and the upper layer protocol (ex. TCP, ICMP, etc)."<br cl=
ear=3D"none"><br clear=3D"none">since this is unnecessary repetition.<br cl=
ear=3D"none"><br clear=3D"none">3) Section 3.2: remove<br clear=3D"none">&n=
bsp; "Operating systems MUST NOT implement a single<br clear=3D"none">&nbsp=
;&nbsp; counter for all connections."<br clear=3D"none"><br clear=3D"none">=
Seems again like unnecessary repetition to previous sentence.<br clear=3D"n=
one"><br clear=3D"none"><br clear=3D"none">4) Section 3.2 again unnecessary=
 repetition of IPv6 basics that can be read from RFC2460. Suggest strongly =
to remove:<br clear=3D"none">&nbsp; "This indicates the<br clear=3D"none">&=
nbsp;&nbsp; following processing requirements:<br clear=3D"none"><br clear=
=3D"none">&nbsp;&nbsp; 00 - skip over this option and continue processing t=
he header.<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; RFC2460 [RFC24=
60] defines other values for the Option Type field.<br clear=3D"none">&nbsp=
;&nbsp; These MUST NOT be used in the PDM."<br clear=3D"none"><br clear=3D"=
none"><br clear=3D"none">and<br clear=3D"none"><br clear=3D"none">&nbsp; "T=
he<br clear=3D"none">&nbsp;&nbsp; possible values are as follows:<br clear=
=3D"none"><br clear=3D"none">&nbsp;&nbsp; 0 - Option Data does not change e=
n-route<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; 1 - Option Data m=
ay change en-route<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; The th=
ree high-order bits described above are to be treated as part<br clear=3D"n=
one">&nbsp;&nbsp; of the Option Type, not independent of the Option Type.&n=
bsp; That is, a<br clear=3D"none">&nbsp;&nbsp; particular option is identif=
ied by a full 8-bit Option Type, not just<br clear=3D"none">&nbsp;&nbsp; th=
e low-order 5 bits of an Option Type."<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">5) Section 3.3 same as in comment 4). Suggest strongly =
removing:<br clear=3D"none">&nbsp; "This follows the order defined in RFC24=
60 [RFC2460]<br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 header<br clear=
=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hop-by-Hop Options heade=
r<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Op=
tions header&nbsp; &lt;--------<br clear=3D"none"><br clear=3D"none">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Routing header<br clear=3D"none"><br clear=3D"none">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Fragment header<br clear=3D"none"><br clear=3D"none">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Authentication header<br clear=3D"none"><br clear=3D"none">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Encapsulating Security Payload header<br clear=3D"none=
"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Options header &lt;-=
-----------<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; uppe=
r-layer header"<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">6) =
Suggest removing entire Section 3.4 and moving the following text to Sectio=
n 3.3:<br clear=3D"none">&nbsp; "PDM MUST be placed before the ESP header i=
n<br clear=3D"none">&nbsp;&nbsp; order to work.&nbsp; If placed before the =
ESP header, the PDM header will<br clear=3D"none">&nbsp;&nbsp; flow in the =
clear over the network thus allowing gathering of<br clear=3D"none">&nbsp;&=
nbsp; performance and diagnostic data without sacrificing security."<br cle=
ar=3D"none"><br clear=3D"none"><br clear=3D"none">7) Section 3.6 suggest re=
moving the following text. I see no value it would add to what has already =
been said:<br clear=3D"none">&nbsp; "As with all other destination options =
extension headers, the PDM is<br clear=3D"none">&nbsp;&nbsp; for destinatio=
n nodes only. As specified above, intermediate devices<br clear=3D"none">&n=
bsp;&nbsp; MUST neither set nor modify this field."<br clear=3D"none"><br c=
lear=3D"none"><br clear=3D"none">8) Section 3.6 suggest removing the follow=
ing 5-tuple text as it has already been described earlier in Section 2:<br =
clear=3D"none">&nbsp; "The 5-tuple is:<br clear=3D"none"><br clear=3D"none"=
>&nbsp;&nbsp; SADDR : IP address of the sender SPORT : Port for sender DADD=
R : IP<br clear=3D"none">&nbsp;&nbsp; address of the destination DPORT : Po=
rt for destination PROTC :<br clear=3D"none">&nbsp;&nbsp; Protocol for uppe=
r layer (ex. TCP, UDP, ICMP)"<br clear=3D"none"><br clear=3D"none"><br clea=
r=3D"none">9) Sections 4.2 and 4.3 suggest removing them entirely. I see wh=
at value these sections add. I acknowledge they are good to know informatio=
n of timer hardware implementation difference but do not really add value o=
n the on-wire encoding of the PDM option.<br clear=3D"none"><br clear=3D"no=
ne"><br clear=3D"none">10) Section 4.4 suggest removing the entire section.=
 Time Base was already described in detail enough in Section 3.2.<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">11) Section 4.5 time base f=
or picoseconds is 11 not 00.<br clear=3D"none"><br clear=3D"none"><br clear=
=3D"none">12) Section 4.5 suggest removing the following text, since it doe=
s not add any more clarity to what has already been said in my opinion. Thi=
s is because all the examples follow nice nybble increment in scaling:<br c=
lear=3D"none">&nbsp; "Sample binary values (high order 16 bits taken)<br cl=
ear=3D"none"><br clear=3D"none">&nbsp;&nbsp; 1 psec&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; 0001<br clear=3D"none">&nbsp;&nbsp; 1 nsec&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3E8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1110 1000<br clear=3D"none">&nbsp;&nbsp; 1 u=
sec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F4240&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1111 0100 0010 0100 000=
0<br clear=3D"none">&nbsp;&nbsp; 1 msec&nbsp;&nbsp;&nbsp;&nbsp; 3B9ACA00&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1011 1001 10=
10 1100 1010 0000 0000<br clear=3D"none">&nbsp;&nbsp; 1 sec&nbsp;&nbsp;&nbs=
p; E8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000"<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">12) Section 4.6 I do not un=
derstand why this section is here. I strongly suggest removing it. Sections=
 4.5 and 3.2 already describe how I would encode the delta time using scali=
ng as a separate fields not embedded (option fields ScaleDTLR and ScaleDTLS=
). Did I misunderstand something here?<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">13) Section 5 suggest removing the following text becau=
se of it repeating what has already been said earlier:<br clear=3D"none">&n=
bsp; "Each packet, in addition to the PDM contains information on the<br cl=
ear=3D"none">&nbsp;&nbsp; sender and receiver. As discussed before, a 5-tup=
le consists of:<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; SADDR : IP address of the sender<br clear=3D"none">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; SPORT : Port for sender<br clear=3D"none">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; DADDR : IP address of the destination<br clear=3D"none">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; DPORT : Port for destination<br clear=3D"none">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; PROTC : Protocol for upper layer (ex. TCP, UDP=
, ICMP)<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; It should be unde=
rstood that the packet identification information is<br clear=3D"none">&nbs=
p;&nbsp; in each packet. We will not repeat that in each of the following<b=
r clear=3D"none">&nbsp;&nbsp; steps."<br clear=3D"none"><br clear=3D"none">=
<br clear=3D"none">14) Section 5.3 suggest merging the following text into =
one example and do necessary rewording. There is no need to do the same cal=
culation twice on almost adjacent lines:<br clear=3D"none"><br clear=3D"non=
e">&nbsp; "Sending time : packet 2 - receive time : packet 1<br clear=3D"no=
ne"><br clear=3D"none">&nbsp;&nbsp; We will call the result of this calcula=
tion: Delta Time Last Received<br clear=3D"none">&nbsp;&nbsp; (DELTATLR)<br=
 clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; That is:<br clear=3D"none">=
<br clear=3D"none">&nbsp;&nbsp; Delta Time Last Received =3D (Sending time:=
 packet 2 - receive time:<br clear=3D"none">&nbsp;&nbsp; packet 1)"<br clea=
r=3D"none"><br clear=3D"none"><br clear=3D"none">15) Expand RTT and PSN on =
their first use.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">Ph=
ew.. after all this I found the document good reading and most likely a use=
ful tool to be used.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none=
">Regards,<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; Jouni</div></d=
iv></div></div><br><br></div> </div> </div>  </div></div></body></html>
------=_Part_2622889_1903105876.1487700213967--


From nobody Tue Feb 21 10:12:57 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8AA129477 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 10:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.785
X-Spam-Level: 
X-Spam-Status: No, score=-3.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id abjuJHH3Bqko for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 10:12:53 -0800 (PST)
Received: from nm22-vm7.bullet.mail.gq1.yahoo.com (nm22-vm7.bullet.mail.gq1.yahoo.com [98.136.217.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD850129465 for <gen-art@ietf.org>; Tue, 21 Feb 2017 10:12:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487700772; bh=6BR3U8WH0jN1w2+mvSgyzxIWoHRDJQza7gHKqnJjHM8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=HXYeMxxKG/OFGoc2E0O/JK945c6wejtJHxonAX/aNIgm24ieiDXf61xULUR3/jB3lImQlnVg9A+z92uFNz9BE81g1F40XaGdqfzG5LMkfQ30sxIgFLc4hbZdSBl9I2LlDvghZyKhC0H+FA84Em/KjkFDHc9y/Mzin81oMW+FYEvUWrK2JYN56eBhjfRRe/9MeH43/NViRSxGYuDSOiLaPVLeyKDZtTqCMpPf0bwZVSED8b4BTq34Cg0G/imW9MrnzcGL+Q5y12UuHOrkSctlWlmBQqfHrmoEnE3bUvtlvqhMJZnmIuCgoYFJDd8UTs8/4Ej2EvJrM3SuIZfzPnonKw==
Received: from [98.137.12.191] by nm22.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:12:52 -0000
Received: from [98.137.12.229] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:12:52 -0000
Received: from [127.0.0.1] by omp1037.mail.gq1.yahoo.com with NNFMP; 21 Feb 2017 18:12:52 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 174874.44924.bm@omp1037.mail.gq1.yahoo.com
X-YMail-OSG: 8ZLdwxMVM1nJlEn7AZqMmbv5AcGEEqtj4XWa4cXqtt7kyXNK.EjciWJz0wGOn4P lkO.NYXcQksO55.Vq8xudx0OOCikWzLBeoPtePEbXp.uS_Z4n0sxkdq3EzJN6I_05.ZZIyi33niv 4wLpKdMkms53R358pkXkA0PsYTyV3Fvbo8336Ft5qbgULiZ3.Oviy8gVOOFV8iPugYj4Z3S3PvKd mLI3dZCse.q9keMuqwHWtD4eUoBsFUSgVth5.gcwvwU4Ek6sKksEZ_fyo5NXPWYGuK8abetx5gcq kWMMidoOo0e8F3pCcNCfw9oMiFkvJVSveDA0O9y1.F.dCFeGOle_DLh0wVYezaA3B7wzn7Wd0xyK nd83Zp0dihhE9ue9IUCN.2L8TTq5lrKNWkoFrOV04Bwy1rUuW1emAxLPe5wreiQ5FeVaH2N2CX2m Nu9_bod9RrA9e2M7X_7s_.DlNuaU1H_F9E70EM5dAdrjOmwWbtPF.vSOKZifttTT42fR2jdTA6CO zB6ztOx7KqY4Vzw6yKl12QXvCV.tqOhkdbfza9xxjeH8ESasvKs6BCvFIzg--
Received: from jws300055.mail.gq1.yahoo.com by sendmailws144.mail.gq1.yahoo.com; Tue, 21 Feb 2017 18:12:51 +0000; 1487700771.074
Date: Tue, 21 Feb 2017 18:12:50 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: jouni korhonen <jouni.nospam@gmail.com>,  General Area Review Team <gen-art@ietf.org>,  "\"draft-ietf-ippm-6man-pdm-option.all@ietf.org\"" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>
Message-ID: <1540716911.2617277.1487700770759@mail.yahoo.com>
In-Reply-To: <685542803.2622890.1487700213971@mail.yahoo.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com> <100465536.2630141.1487699983875@mail.yahoo.com> <685542803.2622890.1487700213971@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_2617276_118908285.1487700770758"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/xddTlLhyCe5DNTQpadbl1JLrdYI>
Cc: Robert Hamilton <rhamilton@cas.org>, "MORTON ALFRED C \(AL\)" <acmorton@att.com>, Michael Ackermann <mackermann@bcbsm.com>
Subject: [Gen-art] Fw: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 18:12:55 -0000

------=_Part_2617276_118908285.1487700770758
Content-Type: multipart/alternative; 
	boundary="----=_Part_2617275_1323557547.1487700770753"

------=_Part_2617275_1323557547.1487700770753
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I don't know why this email keeps getting cut off!
I am attaching my response in a text file.
Sigh.=C2=A0Thanks,
Nalini ElkinsInside Products, Inc.www.insidethestack.com(831) 659-8360

    =20
----- Forwarded Message -----
 From: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com=
>
 To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team <gen=
-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-=
ippm-6man-pdm-option.all@ietf.org>=20
Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@ca=
s.org>; MORTON ALFRED C (AL) <acmorton@att.com>
 Sent: Tuesday, February 21, 2017 10:03 AM
 Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Tim=
e
  =20
Resending. =C2=A0Somehow the last email was cut off.=C2=A0Nalini=C2=A0
      From: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestac=
k.com>
 To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team <gen=
-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-=
ippm-6man-pdm-option.all@ietf.org>=20
Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@ca=
s.org>; MORTON ALFRED C (AL) <acmorton@att.com>
 Sent: Tuesday, February 21, 2017 9:59 AM
 Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Tim=
e
 =20
Jouni,

Here is the thread for your second major comment:

Major comment #2 from you:

>2) The PDM option relation to actual "server" time is somewhat confusing a=
nd the 5-tuple does not allow me to detect the real relationship between th=
e >server/application action that caused the generation of the packet and t=
he PDM within the packet. This is specifically an issue with transport/appl=
ication protocols >that multiplex/interleave multiple application streams i=
nto one transport. I have no idea of the actual individual application time=
 since the packets get generated >independent of the processing of a single=
 thread. I would welcome some discussion around here. Section 1.4 last para=
graph is going to this direction but is not >sufficient IMHO.

Yes, you are, of course, correct that=C2=A0all traffic will flow between th=
e matching ports at the two endpoints. The 5-tuples will match regardless o=
f the application.

The thing is that we never intended that PDM would distinguish between appl=
ications using the same 5-tuple. =C2=A0That is, it is a feature, not a bug.

What PDM WILL tell you is whether the problem is in the network or the host=
. =C2=A0 =C2=A0In our experience, which is primarily on networks for large =
data centers, there is a different group which is involved to troubleshoot =
the problem depending on the nature of the problem. =C2=A0That is, do I get=
 the application developers on the line or the team that deals with the rou=
ters & infrastructure.

One of the important functions of=C2=A0PDM is to allow you to do quick tria=
ge so that you can get the right SWAT team going. =C2=A0 PDM does not tell =
you if the problem is in the IP stack or the application or buffer allocati=
on. =C2=A0 PDM also does not tell you which of the network segments or midd=
le boxes is at fault. =C2=A0The reason for PDM is to get the right speciali=
sts in place who can then be dispatched to investigate their area.

In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0 Both the network group and the application group have quite a few=
 specialized tools at their disposal to further investigate their own areas=
.

I am adding some of this verbiage to section 1.4. =C2=A0 Please see below:

CURRENT
-----------

1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). More=20
intermediate measurements may be needed if the host or network=20
discrimination is not sufficient. At the client, TCP/IP stack time=20
vs. application time may still need to be broken out by client=20
software.=20


NEW----
1.4 Rationale for defined solution=20

The current IPv6 specification does not provide timing nor a similar=20
field in the IPv6 main header or in any extension header. So, we=20
define the IPv6 Performance and Diagnostic Metrics destination option=20
(PDM).=20

Advantages include:=20

1. Real measure of actual transactions.=20
2. Independence from transport layer protocols.=20
3. Ability to span organizational boundaries with consistent=20
instrumentation=20
4. No time synchronization needed between session partners=20
5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
in a uniform way=20

The PDM provides the ability to determine quickly if the (latency)=20
problem is in the network or in the server (application). =C2=A0That is,it =
is a fast way to do triage.
One of the important functions of PDM is to allow you to do quickly dispatc=
hthe right set of diagnosticians. =C2=A0Within network or server latency,th=
ere may be many components. =C2=A0The job of the diagnostician is to ruleea=
ch one out until the culprit is found.
How PDM fits into this diagnostic picture is that PDM will quickly tell=C2=
=A0you how to escalate. =C2=A0PDM will point to either the network area or =
theserver area. =C2=A0 Within the server latency,=C2=A0PDM does not tell yo=
u if the bottleneckis in the IP stack or the application or buffer allocati=
on.=C2=A0Within the network latency,=C2=A0PDM does not tell you which of th=
e network segments or middle boxes is at fault.=C2=A0
What PDM will tell you is whether the problem is in the network or the serv=
er. In our experience,=C2=A0there is often a different group which is invol=
ved to troubleshoot the problem depending on the=C2=A0nature of the problem=
. =C2=A0 That is, the problem may be escalated to the application developer=
sor the team that deals with the routers and infrastructure. =C2=A0Both the=
 network group and the=C2=A0application group have quite a few specialized =
tools at their disposal to further investigate theirown areas. =C2=A0 What =
is missing is the first step, which PDM provides.
In our experience, valuable time is often lost at this first stage of triag=
e. =C2=A0PDM is expected toreduce this time substantially.=C2=A0=C2=A0
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

________________________________

From: jouni korhonen <jouni.nospam@gmail.com>
To: General Area Review Team <gen-art@ietf.org>; draft-ietf-ippm-6man-pdm-o=
ption.all@ietf.org=20
Sent: Friday, September 23, 2016 11:14 AM
Subject: Gen-ART review of



I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-ippm-6man-pdm-option-05
Reviewer: Jouni Korhonen
Review Date: 9/23/2016
IETF LC End Date: 2016-09-28
IESG Telechat date: (if known)

Summary: The draft needs some work.

Major issues:


I have two technical issues here:


1) There is no mention of what is the time reference plane for internal tim=
e stamping. All other timing and synchronization related documents I am awa=
re of (at least outside IETF) describe it very clearly where in the process=
ing/packet handling the time stamp is to be taken. Now the document gives m=
e no idea as an implementer where that should take place. At least it makes=
 it hard to calculate the *network* RTT precisely.


2) The PDM option relation to actual "server" time is somewhat confusing an=
d the 5-tuple does not allow me to detect the real relationship between the=
 server/application action that caused the generation of the packet and the=
 PDM within the packet. This is specifically an issue with transport/applic=
ation protocols that multiplex/interleave multiple application streams into=
 one transport. I have no idea of the actual individual application time si=
nce the packets get generated independent of the processing of a single thr=
ead. I would welcome some discussion around here. Section 1.4 last paragrap=
h is going to this direction but is not sufficient IMHO.


Minor issues:


1) This is a larger editorial issue. The document is far too long with a lo=
t of repetition considering it describes only one IPv6 destination option. =
It is a writing style issue and I am fully aware of that. I have proposals =
how to cut text in the editorial comments section.


2) Section 1.2 3rd paragraph talks about IoT and that speed matters there. =
I find this too generalized statement. There are many other things that mat=
ter in this application domain and speed might not be that important as bei=
ng able to send/receive that one to two bytes of data in a given time windo=
w. I suggest removing this paragraph.


Nits/editorial comments:


1) Section 1.4 numbered list: add missing full stops.


2) Section 3.2: remove
=C2=A0 "The 5-tuple consists of
=C2=A0=C2=A0 the source and destination IP addresses, the source and destin=
ation
=C2=A0=C2=A0 ports, and the upper layer protocol (ex. TCP, ICMP, etc)."

since this is unnecessary repetition.

3) Section 3.2: remove
=C2=A0 "Operating systems MUST NOT implement a single
=C2=A0=C2=A0 counter for all connections."

Seems again like unnecessary repetition to previous sentence.


4) Section 3.2 again unnecessary repetition of IPv6 basics that can be read=
 from RFC2460. Suggest strongly to remove:
=C2=A0 "This indicates the
=C2=A0=C2=A0 following processing requirements:

=C2=A0=C2=A0 00 - skip over this option and continue processing the header.

=C2=A0=C2=A0 RFC2460 [RFC2460] defines other values for the Option Type fie=
ld.
=C2=A0=C2=A0 These MUST NOT be used in the PDM."


and

=C2=A0 "The
=C2=A0=C2=A0 possible values are as follows:

=C2=A0=C2=A0 0 - Option Data does not change en-route

=C2=A0=C2=A0 1 - Option Data may change en-route

=C2=A0=C2=A0 The three high-order bits described above are to be treated as=
 part
=C2=A0=C2=A0 of the Option Type, not independent of the Option Type.=C2=A0 =
That is, a
=C2=A0=C2=A0 particular option is identified by a full 8-bit Option Type, n=
ot just
=C2=A0=C2=A0 the low-order 5 bits of an Option Type."


5) Section 3.3 same as in comment 4). Suggest strongly removing:
=C2=A0 "This follows the order defined in RFC2460 [RFC2460]
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 IPv6 header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Hop-by-Hop Options header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header=C2=A0 <--------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Routing header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Fragment header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Authentication header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Encapsulating Security Payload header

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Destination Options header <------------

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 upper-layer header"


6) Suggest removing entire Section 3.4 and moving the following text to Sec=
tion 3.3:
=C2=A0 "PDM MUST be placed before the ESP header in
=C2=A0=C2=A0 order to work.=C2=A0 If placed before the ESP header, the PDM =
header will
=C2=A0=C2=A0 flow in the clear over the network thus allowing gathering of
=C2=A0=C2=A0 performance and diagnostic data without sacrificing security."


7) Section 3.6 suggest removing the following text. I see no value it would=
 add to what has already been said:
=C2=A0 "As with all other destination options extension headers, the PDM is
=C2=A0=C2=A0 for destination nodes only. As specified above, intermediate d=
evices
=C2=A0=C2=A0 MUST neither set nor modify this field."


8) Section 3.6 suggest removing the following 5-tuple text as it has alread=
y been described earlier in Section 2:
=C2=A0 "The 5-tuple is:

=C2=A0=C2=A0 SADDR : IP address of the sender SPORT : Port for sender DADDR=
 : IP
=C2=A0=C2=A0 address of the destination DPORT : Port for destination PROTC =
:
=C2=A0=C2=A0 Protocol for upper layer (ex. TCP, UDP, ICMP)"


9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value th=
ese sections add. I acknowledge they are good to know information of timer =
hardware implementation difference but do not really add value on the on-wi=
re encoding of the PDM option.


10) Section 4.4 suggest removing the entire section. Time Base was already =
described in detail enough in Section 3.2.


11) Section 4.5 time base for picoseconds is 11 not 00.


12) Section 4.5 suggest removing the following text, since it does not add =
any more clarity to what has already been said in my opinion. This is becau=
se all the examples follow nice nybble increment in scaling:
=C2=A0 "Sample binary values (high order 16 bits taken)

=C2=A0=C2=A0 1 psec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0001
=C2=A0=C2=A0 1 nsec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3=
E8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1110 1=
000
=C2=A0=C2=A0 1 usec=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 F4240=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1111 =
0100 0010 0100 0000
=C2=A0=C2=A0 1 msec=C2=A0=C2=A0=C2=A0=C2=A0 3B9ACA00=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0011 1011 1001 1010 1100 1010 0000 =
0000
=C2=A0=C2=A0 1 sec=C2=A0=C2=A0=C2=A0 E8D4A51000 1110 1000 1101 0100 1010 01=
01 0001 0000 0000 0000"


12) Section 4.6 I do not understand why this section is here. I strongly su=
ggest removing it. Sections 4.5 and 3.2 already describe how I would encode=
 the delta time using scaling as a separate fields not embedded (option fie=
lds ScaleDTLR and ScaleDTLS). Did I misunderstand something here?


13) Section 5 suggest removing the following text because of it repeating w=
hat has already been said earlier:
=C2=A0 "Each packet, in addition to the PDM contains information on the
=C2=A0=C2=A0 sender and receiver. As discussed before, a 5-tuple consists o=
f:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SADDR : IP address of the sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SPORT : Port for sender
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DADDR : IP address of the destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 DPORT : Port for destination
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PROTC : Protocol for upper layer (ex. TCP, U=
DP, ICMP)

=C2=A0=C2=A0 It should be understood that the packet identification informa=
tion is
=C2=A0=C2=A0 in each packet. We will not repeat that in each of the followi=
ng
=C2=A0=C2=A0 steps."


14) Section 5.3 suggest merging the following text into one example and do =
necessary rewording. There is no need to do the same calculation twice on a=
lmost adjacent lines:

=C2=A0 "Sending time : packet 2 - receive time : packet 1

=C2=A0=C2=A0 We will call the result of this calculation: Delta Time Last R=
eceived
=C2=A0=C2=A0 (DELTATLR)

=C2=A0=C2=A0 That is:

=C2=A0=C2=A0 Delta Time Last Received =3D (Sending time: packet 2 - receive=
 time:
=C2=A0=C2=A0 packet 1)"


15) Expand RTT and PSN on their first use.


Phew.. after all this I found the document good reading and most likely a u=
seful tool to be used.


Regards,

=C2=A0=C2=A0 Jouni

  =20

  =20
------=_Part_2617275_1323557547.1487700770753
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1487700549457_6191"><span id=3D"yui_3_16_0_ym19_1_1487700549457_65=
88">I don't know why this email keeps getting cut off!</span></div><div id=
=3D"yui_3_16_0_ym19_1_1487700549457_6191"><span><br></span></div><div id=3D=
"yui_3_16_0_ym19_1_1487700549457_6191"><span id=3D"yui_3_16_0_ym19_1_148770=
0549457_6593">I am attaching my response in a text file.</span></div><div i=
d=3D"yui_3_16_0_ym19_1_1487700549457_6191"><span><br></span></div><div id=
=3D"yui_3_16_0_ym19_1_1487700549457_6191"><span>Sigh.</span></div><div></di=
v><div id=3D"yui_3_16_0_ym19_1_1487700549457_6178">&nbsp;</div><div class=
=3D"signature" id=3D"yui_3_16_0_ym19_1_1487700549457_6081">Thanks,<div id=
=3D"yui_3_16_0_ym19_1_1487700549457_6080"><br></div><div id=3D"yui_3_16_0_y=
m19_1_1487700549457_6179">Nalini Elkins</div><div id=3D"yui_3_16_0_ym19_1_1=
487700549457_6180">Inside Products, Inc.</div><div id=3D"yui_3_16_0_ym19_1_=
1487700549457_6181">www.insidethestack.com</div><div id=3D"yui_3_16_0_ym19_=
1_1487700549457_6182">(831) 659-8360</div></div><div class=3D"qtdSeparateBR=
"><br><br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1487700=
549457_6149" style=3D"display: block;">  <div style=3D"font-family: Helveti=
caNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucid=
a Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_14877005494=
57_6148"> <div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helveti=
ca, Arial, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym=
19_1_1487700549457_6147"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_14877005=
49457_6183"> <font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_148770=
0549457_6184"> <br>----- Forwarded Message -----<br> <b><span style=3D"font=
-weight:bold;">From:</span></b> "nalini.elkins@insidethestack.com" &lt;nali=
ni.elkins@insidethestack.com&gt;<br> <b id=3D"yui_3_16_0_ym19_1_14877005494=
57_6186"><span style=3D"font-weight: bold;" id=3D"yui_3_16_0_ym19_1_1487700=
549457_6185">To:</span></b> jouni korhonen &lt;jouni.nospam@gmail.com&gt;; =
General Area Review Team &lt;gen-art@ietf.org&gt;; "draft-ietf-ippm-6man-pd=
m-option.all@ietf.org" &lt;draft-ietf-ippm-6man-pdm-option.all@ietf.org&gt;=
 <br><b><span style=3D"font-weight: bold;">Cc:</span></b> Michael Ackermann=
 &lt;mackermann@bcbsm.com&gt;; Robert Hamilton &lt;rhamilton@cas.org&gt;; M=
ORTON ALFRED C (AL) &lt;acmorton@att.com&gt;<br> <b><span style=3D"font-wei=
ght: bold;">Sent:</span></b> Tuesday, February 21, 2017 10:03 AM<br> <b id=
=3D"yui_3_16_0_ym19_1_1487700549457_6435"><span style=3D"font-weight: bold;=
" id=3D"yui_3_16_0_ym19_1_1487700549457_6434">Subject:</span></b> Re: Gen-A=
RT review of draft-ietf-ippm-6man-pdm-option:  Server Time<br> </font> </di=
v> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1487700549457_614=
6"><br><div id=3D"yiv0086422205"><div id=3D"yui_3_16_0_ym19_1_1487700549457=
_6145"><div style=3D"color:#000;background-color:#fff;font-family:Helvetica=
Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida =
Grande, sans-serif;font-size:16px;" id=3D"yui_3_16_0_ym19_1_1487700549457_6=
144"><div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487699989064_29721">Resendi=
ng. &nbsp;Somehow the last email was cut off.</div><div></div><div id=3D"yi=
v0086422205yui_3_16_0_ym19_1_1487699989064_29711">&nbsp;</div><div class=3D=
"yiv0086422205signature" id=3D"yiv0086422205yui_3_16_0_ym19_1_1487699989064=
_29690">Nalini&nbsp;</div><div class=3D"yiv0086422205qtdSeparateBR" id=3D"y=
iv0086422205yui_3_16_0_ym19_1_1487699989064_29714"><br clear=3D"none"></div=
><div class=3D"yiv0086422205yqt2896375754" id=3D"yiv0086422205yqt35259"><di=
v class=3D"yiv0086422205yahoo_quoted" id=3D"yiv0086422205yui_3_16_0_ym19_1_=
1487699989064_29718" style=3D"display:block;">  <div id=3D"yiv0086422205yui=
_3_16_0_ym19_1_1487699989064_29717" style=3D"font-family:HelveticaNeue-Ligh=
t, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, s=
ans-serif;font-size:16px;"> <div id=3D"yiv0086422205yui_3_16_0_ym19_1_14876=
99989064_29716" style=3D"font-family:HelveticaNeue, Helvetica Neue, Helveti=
ca, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir=3D"ltr" id=
=3D"yiv0086422205yui_3_16_0_ym19_1_1487699989064_29715"> <font id=3D"yiv008=
6422205yui_3_16_0_ym19_1_1487699989064_29719" size=3D"2" face=3D"Arial"> </=
font><hr id=3D"yiv0086422205yui_3_16_0_ym19_1_1487699989064_29720" size=3D"=
1"> <b id=3D"yui_3_16_0_ym19_1_1487700549457_6437"><span style=3D"font-weig=
ht:bold;" id=3D"yui_3_16_0_ym19_1_1487700549457_6436">From:</span></b> "nal=
ini.elkins@insidethestack.com" &lt;nalini.elkins@insidethestack.com&gt;<br =
clear=3D"none"> <b id=3D"yui_3_16_0_ym19_1_1487700549457_6151"><span style=
=3D"font-weight:bold;" id=3D"yui_3_16_0_ym19_1_1487700549457_6150">To:</spa=
n></b> jouni korhonen &lt;jouni.nospam@gmail.com&gt;; General Area Review T=
eam &lt;gen-art@ietf.org&gt;; "draft-ietf-ippm-6man-pdm-option.all@ietf.org=
" &lt;draft-ietf-ippm-6man-pdm-option.all@ietf.org&gt; <br clear=3D"none"><=
b id=3D"yui_3_16_0_ym19_1_1487700549457_6439"><span style=3D"font-weight:bo=
ld;" id=3D"yui_3_16_0_ym19_1_1487700549457_6438">Cc:</span></b> Michael Ack=
ermann &lt;mackermann@bcbsm.com&gt;; Robert Hamilton &lt;rhamilton@cas.org&=
gt;; MORTON ALFRED C (AL) &lt;acmorton@att.com&gt;<br clear=3D"none"> <b id=
=3D"yui_3_16_0_ym19_1_1487700549457_6359"><span style=3D"font-weight:bold;"=
 id=3D"yui_3_16_0_ym19_1_1487700549457_6358">Sent:</span></b> Tuesday, Febr=
uary 21, 2017 9:59 AM<br clear=3D"none"> <b id=3D"yui_3_16_0_ym19_1_1487700=
549457_6345"><span style=3D"font-weight:bold;" id=3D"yui_3_16_0_ym19_1_1487=
700549457_6344">Subject:</span></b> Re: Gen-ART review of draft-ietf-ippm-6=
man-pdm-option:  Server Time<br clear=3D"none">  </div> <div class=3D"yiv00=
86422205y_msg_container" id=3D"yiv0086422205yui_3_16_0_ym19_1_1487699989064=
_29730"><br clear=3D"none"><div id=3D"yiv0086422205"><div id=3D"yiv00864222=
05yui_3_16_0_ym19_1_1487699989064_29732"><div id=3D"yiv0086422205yui_3_16_0=
_ym19_1_1487699989064_29731" style=3D"color:#000;background-color:#fff;font=
-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetic=
a, Arial, Lucida Grande, sans-serif;font-size:16px;">Jouni,<br clear=3D"non=
e"><br clear=3D"none">Here is the thread for your second major comment:<br =
clear=3D"none"><br clear=3D"none">Major comment #2 from you:<br clear=3D"no=
ne"><br clear=3D"none">&gt;2) The PDM option relation to actual "server" ti=
me is somewhat confusing and the 5-tuple does not allow me to detect the re=
al relationship between the &gt;server/application action that caused the g=
eneration of the packet and the PDM within the packet. This is specifically=
 an issue with transport/application protocols &gt;that multiplex/interleav=
e multiple application streams into one transport. I have no idea of the ac=
tual individual application time since the packets get generated &gt;indepe=
ndent of the processing of a single thread. I would welcome some discussion=
 around here. Section 1.4 last paragraph is going to this direction but is =
not &gt;sufficient IMHO.<br clear=3D"none"><br clear=3D"none">Yes, you are,=
 of course, correct that&nbsp;all traffic will flow between the matching po=
rts at the two endpoints. The 5-tuples will match regardless of the applica=
tion.<br clear=3D"none"><br clear=3D"none">The thing is that we never inten=
ded that PDM would distinguish between applications using the same 5-tuple.=
 &nbsp;That is, it is a feature, not a bug.<br clear=3D"none"><br clear=3D"=
none">What PDM WILL tell you is whether the problem is in the network or th=
e host. &nbsp; &nbsp;In our experience, which is primarily on networks for =
large data centers, there is a different group which is involved to trouble=
shoot the problem depending on the nature of the problem. &nbsp;That is, do=
 I get the application developers on the line or the team that deals with t=
he routers &amp; infrastructure.<br clear=3D"none"><br clear=3D"none">One o=
f the important functions of&nbsp;PDM is to allow you to do quick triage so=
 that you can get the right SWAT team going. &nbsp; PDM does not tell you i=
f the problem is in the IP stack or the application or buffer allocation. &=
nbsp; PDM also does not tell you which of the network segments or middle bo=
xes is at fault. &nbsp;The reason for PDM is to get the right specialists i=
n place who can then be dispatched to investigate their area.<br clear=3D"n=
one"><br clear=3D"none">In our experience, valuable time is often lost at t=
his first stage of triage. &nbsp; Both the network group and the applicatio=
n group have quite a few specialized tools at their disposal to further inv=
estigate their own areas.<br clear=3D"none"><br clear=3D"none">I am adding =
some of this verbiage to section 1.4. &nbsp; Please see below:<br clear=3D"=
none"><br clear=3D"none">CURRENT<br clear=3D"none">-----------<br clear=3D"=
none"><br clear=3D"none">1.4 Rationale for defined solution <br clear=3D"no=
ne"><br clear=3D"none">The current IPv6 specification does not provide timi=
ng nor a similar <br clear=3D"none">field in the IPv6 main header or in any=
 extension header. So, we <br clear=3D"none">define the IPv6 Performance an=
d Diagnostic Metrics destination option <br clear=3D"none">(PDM). <br clear=
=3D"none"><br clear=3D"none">Advantages include: <br clear=3D"none"><br cle=
ar=3D"none">1.  Real measure of actual transactions. <br clear=3D"none">2. =
 Independence from transport layer protocols. <br clear=3D"none">3.  Abilit=
y to span organizational boundaries with consistent <br clear=3D"none">inst=
rumentation <br clear=3D"none">4.  No time synchronization needed between s=
ession partners <br clear=3D"none">5.  Ability to handle all transport prot=
ocols (TCP, UDP, SCTP, etc) <br clear=3D"none">in a uniform way <br clear=
=3D"none"><br clear=3D"none">The PDM provides the ability to determine quic=
kly if the (latency) <br clear=3D"none">problem is in the network or in the=
 server (application).  More <br clear=3D"none">intermediate measurements m=
ay be needed if the host or network <br clear=3D"none">discrimination is no=
t sufficient.  At the client, TCP/IP stack time <br clear=3D"none">vs. appl=
ication time may still need to be broken out by client <br clear=3D"none">s=
oftware. <br clear=3D"none"><div id=3D"yiv0086422205yui_3_16_0_ym19_1_14876=
97725733_31288"><br clear=3D"none"></div><div><br clear=3D"none"></div><div=
 id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_31289">NEW</div><div id=
=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_31290">----</div><div id=
=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_31293"><br clear=3D"none">=
</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_37838"><div i=
d=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_31291">1.4 Rationale for =
defined solution=20
<br clear=3D"none">
<br clear=3D"none">The current IPv6 specification does not provide timing n=
or a similar=20
<br clear=3D"none">field in the IPv6 main header or in any extension header=
. So, we=20
<br clear=3D"none">define the IPv6 Performance and Diagnostic Metrics desti=
nation option=20
<br clear=3D"none">(PDM).=20
<br clear=3D"none">
<br clear=3D"none">Advantages include:=20
<br clear=3D"none">
<br clear=3D"none">1. Real measure of actual transactions.=20
<br clear=3D"none">2. Independence from transport layer protocols.=20
<br clear=3D"none">3. Ability to span organizational boundaries with consis=
tent=20
<br clear=3D"none">instrumentation=20
<br clear=3D"none">4. No time synchronization needed between session partne=
rs=20
<br clear=3D"none">5. Ability to handle all transport protocols (TCP, UDP, =
SCTP, etc)=20
<br clear=3D"none">in a uniform way=20
<br clear=3D"none">
<br clear=3D"none">The PDM provides the ability to determine quickly if the=
 (latency)=20
<br clear=3D"none">problem is in the network or in the server (application)=
. &nbsp;That is,</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_14876977257=
33_31291">it is a fast way to do triage.</div><div id=3D"yiv0086422205yui_3=
_16_0_ym19_1_1487697725733_31291"><br clear=3D"none"></div><div id=3D"yiv00=
86422205yui_3_16_0_ym19_1_1487697725733_37839"><div id=3D"yiv0086422205yui_=
3_16_0_ym19_1_1487697725733_33204">One of the important functions of PDM is=
 to allow you to do quickly dispatch</div><div id=3D"yiv0086422205yui_3_16_=
0_ym19_1_1487697725733_33204">the right set of diagnosticians. &nbsp;Within=
 network or server latency,</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_=
1487697725733_33204">there may be many components. &nbsp;The job of the dia=
gnostician is to rule</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_148769=
7725733_33204">each one out until the culprit is found.</div><div id=3D"yiv=
0086422205yui_3_16_0_ym19_1_1487697725733_33204"><br clear=3D"none"></div><=
div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_33204">How PDM fits =
into this diagnostic picture is that PDM will quickly tell&nbsp;</div><div =
id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_33204">you how to escala=
te. &nbsp;PDM will point to either the network area or the</div><div id=3D"=
yiv0086422205yui_3_16_0_ym19_1_1487697725733_33204">server area. &nbsp; Wit=
hin the server latency,&nbsp;<span id=3D"yiv0086422205yui_3_16_0_ym19_1_148=
7697725733_37177" style=3D"font-family:HelveticaNeue-Light,;">PDM does not =
tell you if the bottleneck</span></div><div id=3D"yiv0086422205yui_3_16_0_y=
m19_1_1487697725733_33204"><span id=3D"yiv0086422205yui_3_16_0_ym19_1_14876=
97725733_37689" style=3D"font-family:HelveticaNeue-Light,;">is in the IP st=
ack or the application or buffer allocation.&nbsp;</span>Within the network=
 latency,&nbsp;</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_148769772573=
3_33204">PDM does not tell you which of the network segments or middle boxe=
s is at fault.&nbsp;</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697=
725733_33204"><br clear=3D"none"></div><div dir=3D"ltr" id=3D"yiv0086422205=
yui_3_16_0_ym19_1_1487697725733_33204">What PDM will tell you is whether th=
e problem is in the network or the server. In our experience,&nbsp;</div><d=
iv dir=3D"ltr" id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_33204">th=
ere is often a different group which is involved to troubleshoot the proble=
m depending on the&nbsp;</div><div dir=3D"ltr" id=3D"yiv0086422205yui_3_16_=
0_ym19_1_1487697725733_33204">nature of the problem. &nbsp; That is, the pr=
oblem may be escalated to the application developers</div><div dir=3D"ltr" =
id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_33204">or the team that =
deals with the routers and infrastructure. &nbsp;Both the network group and=
 the&nbsp;</div><div dir=3D"ltr" id=3D"yiv0086422205yui_3_16_0_ym19_1_14876=
97725733_33204">application group have quite a few specialized tools at the=
ir disposal to further investigate their</div><div dir=3D"ltr" id=3D"yiv008=
6422205yui_3_16_0_ym19_1_1487697725733_33204">own areas. &nbsp; What is mis=
sing is the first step, which PDM provides.</div></div></div><div id=3D"yiv=
0086422205yui_3_16_0_ym19_1_1487697725733_37854"><div dir=3D"ltr" id=3D"yiv=
0086422205yui_3_16_0_ym19_1_1487697725733_33204"><br clear=3D"none"></div><=
/div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_37863"><div di=
r=3D"ltr" id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_31291"><div id=
=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_32708">In our experience, =
valuable time is often lost at this first stage of triage. &nbsp;PDM is exp=
ected to</div><div id=3D"yiv0086422205yui_3_16_0_ym19_1_1487697725733_32708=
">reduce this time substantially.&nbsp;</div><div class=3D"yiv0086422205yqt=
9051455253" id=3D"yiv0086422205yqtfd89895"><div id=3D"yiv0086422205yui_3_16=
_0_ym19_1_1487697725733_32708">&nbsp;<br clear=3D"none"></div></div></div><=
/div><div class=3D"yiv0086422205yqt9051455253" id=3D"yiv0086422205yqtfd5402=
4">Thanks,<br clear=3D"none"><br clear=3D"none">Nalini Elkins<br clear=3D"n=
one">Inside Products, Inc.<br clear=3D"none">www.insidethestack.com<br clea=
r=3D"none">(831) 659-8360<br clear=3D"none"><br clear=3D"none">____________=
____________________<br clear=3D"none"><br clear=3D"none">From: jouni korho=
nen &lt;jouni.nospam@gmail.com&gt;<br clear=3D"none">To: General Area Revie=
w Team &lt;gen-art@ietf.org&gt;; draft-ietf-ippm-6man-pdm-option.all@ietf.o=
rg <br clear=3D"none">Sent: Friday, September 23, 2016 11:14 AM<br clear=3D=
"none">Subject: Gen-ART review of<br clear=3D"none"><br clear=3D"none"><br =
clear=3D"none"><br clear=3D"none">I am the assigned Gen-ART reviewer for th=
is draft. The General Area<br clear=3D"none">Review Team (Gen-ART) reviews =
all IETF documents being processed<br clear=3D"none">by the IESG for the IE=
TF Chair. Please wait for direction from your<br clear=3D"none">document sh=
epherd or AD before posting a new version of the draft.<br clear=3D"none"><=
br clear=3D"none">For more information, please see the FAQ at<br clear=3D"n=
one"><br clear=3D"none">&lt;http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/=
GenArtfaq&gt;.<br clear=3D"none"><br clear=3D"none">Document: draft-ietf-ip=
pm-6man-pdm-option-05<br clear=3D"none">Reviewer: Jouni Korhonen<br clear=
=3D"none">Review Date: 9/23/2016<br clear=3D"none">IETF LC End Date: 2016-0=
9-28<br clear=3D"none">IESG Telechat date: (if known)<br clear=3D"none"><br=
 clear=3D"none">Summary: The draft needs some work.<br clear=3D"none"><br c=
lear=3D"none">Major issues:<br clear=3D"none"><br clear=3D"none"><br clear=
=3D"none">I have two technical issues here:<br clear=3D"none"><br clear=3D"=
none"><br clear=3D"none">1) There is no mention of what is the time referen=
ce plane for internal time stamping. All other timing and synchronization r=
elated documents I am aware of (at least outside IETF) describe it very cle=
arly where in the processing/packet handling the time stamp is to be taken.=
 Now the document gives me no idea as an implementer where that should take=
 place. At least it makes it hard to calculate the *network* RTT precisely.=
<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">2) The PDM option =
relation to actual "server" time is somewhat confusing and the 5-tuple does=
 not allow me to detect the real relationship between the server/applicatio=
n action that caused the generation of the packet and the PDM within the pa=
cket. This is specifically an issue with transport/application protocols th=
at multiplex/interleave multiple application streams into one transport. I =
have no idea of the actual individual application time since the packets ge=
t generated independent of the processing of a single thread. I would welco=
me some discussion around here. Section 1.4 last paragraph is going to this=
 direction but is not sufficient IMHO.<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">Minor issues:<br clear=3D"none"><br clear=3D"none"><br =
clear=3D"none">1) This is a larger editorial issue. The document is far too=
 long with a lot of repetition considering it describes only one IPv6 desti=
nation option. It is a writing style issue and I am fully aware of that. I =
have proposals how to cut text in the editorial comments section.<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">2) Section 1.2 3rd paragrap=
h talks about IoT and that speed matters there. I find this too generalized=
 statement. There are many other things that matter in this application dom=
ain and speed might not be that important as being able to send/receive tha=
t one to two bytes of data in a given time window. I suggest removing this =
paragraph.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">Nits/edi=
torial comments:<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">1)=
 Section 1.4 numbered list: add missing full stops.<br clear=3D"none"><br c=
lear=3D"none"><br clear=3D"none">2) Section 3.2: remove<br clear=3D"none">&=
nbsp; "The 5-tuple consists of<br clear=3D"none">&nbsp;&nbsp; the source an=
d destination IP addresses, the source and destination<br clear=3D"none">&n=
bsp;&nbsp; ports, and the upper layer protocol (ex. TCP, ICMP, etc)."<br cl=
ear=3D"none"><br clear=3D"none">since this is unnecessary repetition.<br cl=
ear=3D"none"><br clear=3D"none">3) Section 3.2: remove<br clear=3D"none">&n=
bsp; "Operating systems MUST NOT implement a single<br clear=3D"none">&nbsp=
;&nbsp; counter for all connections."<br clear=3D"none"><br clear=3D"none">=
Seems again like unnecessary repetition to previous sentence.<br clear=3D"n=
one"><br clear=3D"none"><br clear=3D"none">4) Section 3.2 again unnecessary=
 repetition of IPv6 basics that can be read from RFC2460. Suggest strongly =
to remove:<br clear=3D"none">&nbsp; "This indicates the<br clear=3D"none">&=
nbsp;&nbsp; following processing requirements:<br clear=3D"none"><br clear=
=3D"none">&nbsp;&nbsp; 00 - skip over this option and continue processing t=
he header.<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; RFC2460 [RFC24=
60] defines other values for the Option Type field.<br clear=3D"none">&nbsp=
;&nbsp; These MUST NOT be used in the PDM."<br clear=3D"none"><br clear=3D"=
none"><br clear=3D"none">and<br clear=3D"none"><br clear=3D"none">&nbsp; "T=
he<br clear=3D"none">&nbsp;&nbsp; possible values are as follows:<br clear=
=3D"none"><br clear=3D"none">&nbsp;&nbsp; 0 - Option Data does not change e=
n-route<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; 1 - Option Data m=
ay change en-route<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; The th=
ree high-order bits described above are to be treated as part<br clear=3D"n=
one">&nbsp;&nbsp; of the Option Type, not independent of the Option Type.&n=
bsp; That is, a<br clear=3D"none">&nbsp;&nbsp; particular option is identif=
ied by a full 8-bit Option Type, not just<br clear=3D"none">&nbsp;&nbsp; th=
e low-order 5 bits of an Option Type."<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">5) Section 3.3 same as in comment 4). Suggest strongly =
removing:<br clear=3D"none">&nbsp; "This follows the order defined in RFC24=
60 [RFC2460]<br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 header<br clear=
=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hop-by-Hop Options heade=
r<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Op=
tions header&nbsp; &lt;--------<br clear=3D"none"><br clear=3D"none">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Routing header<br clear=3D"none"><br clear=3D"none">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Fragment header<br clear=3D"none"><br clear=3D"none">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Authentication header<br clear=3D"none"><br clear=3D"none">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Encapsulating Security Payload header<br clear=3D"none=
"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Destination Options header &lt;-=
-----------<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; uppe=
r-layer header"<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">6) =
Suggest removing entire Section 3.4 and moving the following text to Sectio=
n 3.3:<br clear=3D"none">&nbsp; "PDM MUST be placed before the ESP header i=
n<br clear=3D"none">&nbsp;&nbsp; order to work.&nbsp; If placed before the =
ESP header, the PDM header will<br clear=3D"none">&nbsp;&nbsp; flow in the =
clear over the network thus allowing gathering of<br clear=3D"none">&nbsp;&=
nbsp; performance and diagnostic data without sacrificing security."<br cle=
ar=3D"none"><br clear=3D"none"><br clear=3D"none">7) Section 3.6 suggest re=
moving the following text. I see no value it would add to what has already =
been said:<br clear=3D"none">&nbsp; "As with all other destination options =
extension headers, the PDM is<br clear=3D"none">&nbsp;&nbsp; for destinatio=
n nodes only. As specified above, intermediate devices<br clear=3D"none">&n=
bsp;&nbsp; MUST neither set nor modify this field."<br clear=3D"none"><br c=
lear=3D"none"><br clear=3D"none">8) Section 3.6 suggest removing the follow=
ing 5-tuple text as it has already been described earlier in Section 2:<br =
clear=3D"none">&nbsp; "The 5-tuple is:<br clear=3D"none"><br clear=3D"none"=
>&nbsp;&nbsp; SADDR : IP address of the sender SPORT : Port for sender DADD=
R : IP<br clear=3D"none">&nbsp;&nbsp; address of the destination DPORT : Po=
rt for destination PROTC :<br clear=3D"none">&nbsp;&nbsp; Protocol for uppe=
r layer (ex. TCP, UDP, ICMP)"<br clear=3D"none"><br clear=3D"none"><br clea=
r=3D"none">9) Sections 4.2 and 4.3 suggest removing them entirely. I see wh=
at value these sections add. I acknowledge they are good to know informatio=
n of timer hardware implementation difference but do not really add value o=
n the on-wire encoding of the PDM option.<br clear=3D"none"><br clear=3D"no=
ne"><br clear=3D"none">10) Section 4.4 suggest removing the entire section.=
 Time Base was already described in detail enough in Section 3.2.<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">11) Section 4.5 time base f=
or picoseconds is 11 not 00.<br clear=3D"none"><br clear=3D"none"><br clear=
=3D"none">12) Section 4.5 suggest removing the following text, since it doe=
s not add any more clarity to what has already been said in my opinion. Thi=
s is because all the examples follow nice nybble increment in scaling:<br c=
lear=3D"none">&nbsp; "Sample binary values (high order 16 bits taken)<br cl=
ear=3D"none"><br clear=3D"none">&nbsp;&nbsp; 1 psec&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; 0001<br clear=3D"none">&nbsp;&nbsp; 1 nsec&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3E8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1110 1000<br clear=3D"none">&nbsp;&nbsp; 1 u=
sec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F4240&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1111 0100 0010 0100 000=
0<br clear=3D"none">&nbsp;&nbsp; 1 msec&nbsp;&nbsp;&nbsp;&nbsp; 3B9ACA00&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0011 1011 1001 10=
10 1100 1010 0000 0000<br clear=3D"none">&nbsp;&nbsp; 1 sec&nbsp;&nbsp;&nbs=
p; E8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000"<br clear=
=3D"none"><br clear=3D"none"><br clear=3D"none">12) Section 4.6 I do not un=
derstand why this section is here. I strongly suggest removing it. Sections=
 4.5 and 3.2 already describe how I would encode the delta time using scali=
ng as a separate fields not embedded (option fields ScaleDTLR and ScaleDTLS=
). Did I misunderstand something here?<br clear=3D"none"><br clear=3D"none"=
><br clear=3D"none">13) Section 5 suggest removing the following text becau=
se of it repeating what has already been said earlier:<br clear=3D"none">&n=
bsp; "Each packet, in addition to the PDM contains information on the<br cl=
ear=3D"none">&nbsp;&nbsp; sender and receiver. As discussed before, a 5-tup=
le consists of:<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; SADDR : IP address of the sender<br clear=3D"none">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; SPORT : Port for sender<br clear=3D"none">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; DADDR : IP address of the destination<br clear=3D"none">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; DPORT : Port for destination<br clear=3D"none">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; PROTC : Protocol for upper layer (ex. TCP, UDP=
, ICMP)<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; It should be unde=
rstood that the packet identification information is<br clear=3D"none">&nbs=
p;&nbsp; in each packet. We will not repeat that in each of the following<b=
r clear=3D"none">&nbsp;&nbsp; steps."<br clear=3D"none"><br clear=3D"none">=
<br clear=3D"none">14) Section 5.3 suggest merging the following text into =
one example and do necessary rewording. There is no need to do the same cal=
culation twice on almost adjacent lines:<br clear=3D"none"><br clear=3D"non=
e">&nbsp; "Sending time : packet 2 - receive time : packet 1<br clear=3D"no=
ne"><br clear=3D"none">&nbsp;&nbsp; We will call the result of this calcula=
tion: Delta Time Last Received<br clear=3D"none">&nbsp;&nbsp; (DELTATLR)<br=
 clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; That is:<br clear=3D"none">=
<br clear=3D"none">&nbsp;&nbsp; Delta Time Last Received =3D (Sending time:=
 packet 2 - receive time:<br clear=3D"none">&nbsp;&nbsp; packet 1)"<br clea=
r=3D"none"><br clear=3D"none"><br clear=3D"none">15) Expand RTT and PSN on =
their first use.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none">Ph=
ew.. after all this I found the document good reading and most likely a use=
ful tool to be used.<br clear=3D"none"><br clear=3D"none"><br clear=3D"none=
">Regards,<br clear=3D"none"><br clear=3D"none">&nbsp;&nbsp; Jouni</div></d=
iv></div></div><br clear=3D"none" id=3D"yui_3_16_0_ym19_1_1487700549457_637=
3"><br clear=3D"none"></div> </div> </div>  </div></div></div></div></div><=
br><br></div> </div> </div>  </div></div></body></html>
------=_Part_2617275_1323557547.1487700770753--

------=_Part_2617276_118908285.1487700770758
Content-Type: text/plain
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="serverTimeComments.txt"
Content-ID: <f90ff78e-64c4-c172-921f-db6127b40dcf@yahoo.com>

Sm91bmksDQoNCkhlcmUgaXMgdGhlIHRocmVhZCBmb3IgeW91ciBzZWNvbmQgbWFqb3IgY29tbWVu
dDoNCg0KTWFqb3IgY29tbWVudCAjMiBmcm9tIHlvdToNCg0KPjIpIFRoZSBQRE0gb3B0aW9uIHJl
bGF0aW9uIHRvIGFjdHVhbCAic2VydmVyIiB0aW1lIGlzIHNvbWV3aGF0IGNvbmZ1c2luZyBhbmQg
dGhlIDUtdHVwbGUgZG9lcyBub3QgYWxsb3cgbWUgdG8gZGV0ZWN0IHRoZSByZWFsIHJlbGF0aW9u
c2hpcCBiZXR3ZWVuIHRoZSA+c2VydmVyL2FwcGxpY2F0aW9uIGFjdGlvbiB0aGF0IGNhdXNlZCB0
aGUgZ2VuZXJhdGlvbiBvZiB0aGUgcGFja2V0IGFuZCB0aGUgUERNIHdpdGhpbiB0aGUgcGFja2V0
LiBUaGlzIGlzIHNwZWNpZmljYWxseSBhbiBpc3N1ZSB3aXRoIHRyYW5zcG9ydC9hcHBsaWNhdGlv
biBwcm90b2NvbHMgPnRoYXQgbXVsdGlwbGV4L2ludGVybGVhdmUgbXVsdGlwbGUgYXBwbGljYXRp
b24gc3RyZWFtcyBpbnRvIG9uZSB0cmFuc3BvcnQuIEkgaGF2ZSBubyBpZGVhIG9mIHRoZSBhY3R1
YWwgaW5kaXZpZHVhbCBhcHBsaWNhdGlvbiB0aW1lIHNpbmNlIHRoZSBwYWNrZXRzIGdldCBnZW5l
cmF0ZWQgPmluZGVwZW5kZW50IG9mIHRoZSBwcm9jZXNzaW5nIG9mIGEgc2luZ2xlIHRocmVhZC4g
SSB3b3VsZCB3ZWxjb21lIHNvbWUgZGlzY3Vzc2lvbiBhcm91bmQgaGVyZS4gU2VjdGlvbiAxLjQg
bGFzdCBwYXJhZ3JhcGggaXMgZ29pbmcgdG8gdGhpcyBkaXJlY3Rpb24gYnV0IGlzIG5vdCA+c3Vm
ZmljaWVudCBJTUhPLg0KDQpZZXMsIHlvdSBhcmUsIG9mIGNvdXJzZSwgY29ycmVjdCB0aGF0IGFs
bCB0cmFmZmljIHdpbGwgZmxvdyBiZXR3ZWVuIHRoZSBtYXRjaGluZyBwb3J0cyBhdCB0aGUgdHdv
IGVuZHBvaW50cy4gVGhlIDUtdHVwbGVzIHdpbGwgbWF0Y2ggcmVnYXJkbGVzcyBvZiB0aGUgYXBw
bGljYXRpb24uDQoNClRoZSB0aGluZyBpcyB0aGF0IHdlIG5ldmVyIGludGVuZGVkIHRoYXQgUERN
IHdvdWxkIGRpc3Rpbmd1aXNoIGJldHdlZW4gYXBwbGljYXRpb25zIHVzaW5nIHRoZSBzYW1lIDUt
dHVwbGUuICBUaGF0IGlzLCBpdCBpcyBhIGZlYXR1cmUsIG5vdCBhIGJ1Zy4NCg0KV2hhdCBQRE0g
V0lMTCB0ZWxsIHlvdSBpcyB3aGV0aGVyIHRoZSBwcm9ibGVtIGlzIGluIHRoZSBuZXR3b3JrIG9y
IHRoZSBob3N0LiAgICBJbiBvdXIgZXhwZXJpZW5jZSwgd2hpY2ggaXMgcHJpbWFyaWx5IG9uIG5l
dHdvcmtzIGZvciBsYXJnZSBkYXRhIGNlbnRlcnMsIHRoZXJlIGlzIGEgZGlmZmVyZW50IGdyb3Vw
IHdoaWNoIGlzIGludm9sdmVkIHRvIHRyb3VibGVzaG9vdCB0aGUgcHJvYmxlbSBkZXBlbmRpbmcg
b24gdGhlIG5hdHVyZSBvZiB0aGUgcHJvYmxlbS4gIFRoYXQgaXMsIGRvIEkgZ2V0IHRoZSBhcHBs
aWNhdGlvbiBkZXZlbG9wZXJzIG9uIHRoZSBsaW5lIG9yIHRoZSB0ZWFtIHRoYXQgZGVhbHMgd2l0
aCB0aGUgcm91dGVycyAmIGluZnJhc3RydWN0dXJlLg0KDQpPbmUgb2YgdGhlIGltcG9ydGFudCBm
dW5jdGlvbnMgb2YgUERNIGlzIHRvIGFsbG93IHlvdSB0byBkbyBxdWljayB0cmlhZ2Ugc28gdGhh
dCB5b3UgY2FuIGdldCB0aGUgcmlnaHQgU1dBVCB0ZWFtIGdvaW5nLiAgIFBETSBkb2VzIG5vdCB0
ZWxsIHlvdSBpZiB0aGUgcHJvYmxlbSBpcyBpbiB0aGUgSVAgc3RhY2sgb3IgdGhlIGFwcGxpY2F0
aW9uIG9yIGJ1ZmZlciBhbGxvY2F0aW9uLiAgIFBETSBhbHNvIGRvZXMgbm90IHRlbGwgeW91IHdo
aWNoIG9mIHRoZSBuZXR3b3JrIHNlZ21lbnRzIG9yIG1pZGRsZSBib3hlcyBpcyBhdCBmYXVsdC4g
IFRoZSByZWFzb24gZm9yIFBETSBpcyB0byBnZXQgdGhlIHJpZ2h0IHNwZWNpYWxpc3RzIGluIHBs
YWNlIHdobyBjYW4gdGhlbiBiZSBkaXNwYXRjaGVkIHRvIGludmVzdGlnYXRlIHRoZWlyIGFyZWEu
DQoNCkluIG91ciBleHBlcmllbmNlLCB2YWx1YWJsZSB0aW1lIGlzIG9mdGVuIGxvc3QgYXQgdGhp
cyBmaXJzdCBzdGFnZSBvZiB0cmlhZ2UuICAgQm90aCB0aGUgbmV0d29yayBncm91cCBhbmQgdGhl
IGFwcGxpY2F0aW9uIGdyb3VwIGhhdmUgcXVpdGUgYSBmZXcgc3BlY2lhbGl6ZWQgdG9vbHMgYXQg
dGhlaXIgZGlzcG9zYWwgdG8gZnVydGhlciBpbnZlc3RpZ2F0ZSB0aGVpciBvd24gYXJlYXMuDQoN
CkkgYW0gYWRkaW5nIHNvbWUgb2YgdGhpcyB2ZXJiaWFnZSB0byBzZWN0aW9uIDEuNC4gICBQbGVh
c2Ugc2VlIGJlbG93Og0KDQpDVVJSRU5UDQotLS0tLS0tLS0tLQ0KDQoxLjQgUmF0aW9uYWxlIGZv
ciBkZWZpbmVkIHNvbHV0aW9uIA0KDQpUaGUgY3VycmVudCBJUHY2IHNwZWNpZmljYXRpb24gZG9l
cyBub3QgcHJvdmlkZSB0aW1pbmcgbm9yIGEgc2ltaWxhciANCmZpZWxkIGluIHRoZSBJUHY2IG1h
aW4gaGVhZGVyIG9yIGluIGFueSBleHRlbnNpb24gaGVhZGVyLiBTbywgd2UgDQpkZWZpbmUgdGhl
IElQdjYgUGVyZm9ybWFuY2UgYW5kIERpYWdub3N0aWMgTWV0cmljcyBkZXN0aW5hdGlvbiBvcHRp
b24gDQooUERNKS4gDQoNCkFkdmFudGFnZXMgaW5jbHVkZTogDQoNCjEuIFJlYWwgbWVhc3VyZSBv
ZiBhY3R1YWwgdHJhbnNhY3Rpb25zLiANCjIuIEluZGVwZW5kZW5jZSBmcm9tIHRyYW5zcG9ydCBs
YXllciBwcm90b2NvbHMuIA0KMy4gQWJpbGl0eSB0byBzcGFuIG9yZ2FuaXphdGlvbmFsIGJvdW5k
YXJpZXMgd2l0aCBjb25zaXN0ZW50IA0KaW5zdHJ1bWVudGF0aW9uIA0KNC4gTm8gdGltZSBzeW5j
aHJvbml6YXRpb24gbmVlZGVkIGJldHdlZW4gc2Vzc2lvbiBwYXJ0bmVycyANCjUuIEFiaWxpdHkg
dG8gaGFuZGxlIGFsbCB0cmFuc3BvcnQgcHJvdG9jb2xzIChUQ1AsIFVEUCwgU0NUUCwgZXRjKSAN
CmluIGEgdW5pZm9ybSB3YXkgDQoNClRoZSBQRE0gcHJvdmlkZXMgdGhlIGFiaWxpdHkgdG8gZGV0
ZXJtaW5lIHF1aWNrbHkgaWYgdGhlIChsYXRlbmN5KSANCnByb2JsZW0gaXMgaW4gdGhlIG5ldHdv
cmsgb3IgaW4gdGhlIHNlcnZlciAoYXBwbGljYXRpb24pLiBNb3JlIA0KaW50ZXJtZWRpYXRlIG1l
YXN1cmVtZW50cyBtYXkgYmUgbmVlZGVkIGlmIHRoZSBob3N0IG9yIG5ldHdvcmsgDQpkaXNjcmlt
aW5hdGlvbiBpcyBub3Qgc3VmZmljaWVudC4gQXQgdGhlIGNsaWVudCwgVENQL0lQIHN0YWNrIHRp
bWUgDQp2cy4gYXBwbGljYXRpb24gdGltZSBtYXkgc3RpbGwgbmVlZCB0byBiZSBicm9rZW4gb3V0
IGJ5IGNsaWVudCANCnNvZnR3YXJlLiANCg0KDQpORVcNCi0tLS0NCg0KMS40IFJhdGlvbmFsZSBm
b3IgZGVmaW5lZCBzb2x1dGlvbiANCg0KVGhlIGN1cnJlbnQgSVB2NiBzcGVjaWZpY2F0aW9uIGRv
ZXMgbm90IHByb3ZpZGUgdGltaW5nIG5vciBhIHNpbWlsYXIgDQpmaWVsZCBpbiB0aGUgSVB2NiBt
YWluIGhlYWRlciBvciBpbiBhbnkgZXh0ZW5zaW9uIGhlYWRlci4gU28sIHdlIA0KZGVmaW5lIHRo
ZSBJUHY2IFBlcmZvcm1hbmNlIGFuZCBEaWFnbm9zdGljIE1ldHJpY3MgZGVzdGluYXRpb24gb3B0
aW9uIA0KKFBETSkuIA0KDQpBZHZhbnRhZ2VzIGluY2x1ZGU6IA0KDQoxLiBSZWFsIG1lYXN1cmUg
b2YgYWN0dWFsIHRyYW5zYWN0aW9ucy4gDQoyLiBJbmRlcGVuZGVuY2UgZnJvbSB0cmFuc3BvcnQg
bGF5ZXIgcHJvdG9jb2xzLiANCjMuIEFiaWxpdHkgdG8gc3BhbiBvcmdhbml6YXRpb25hbCBib3Vu
ZGFyaWVzIHdpdGggY29uc2lzdGVudCANCmluc3RydW1lbnRhdGlvbiANCjQuIE5vIHRpbWUgc3lu
Y2hyb25pemF0aW9uIG5lZWRlZCBiZXR3ZWVuIHNlc3Npb24gcGFydG5lcnMgDQo1LiBBYmlsaXR5
IHRvIGhhbmRsZSBhbGwgdHJhbnNwb3J0IHByb3RvY29scyAoVENQLCBVRFAsIFNDVFAsIGV0Yykg
DQppbiBhIHVuaWZvcm0gd2F5IA0KDQpUaGUgUERNIHByb3ZpZGVzIHRoZSBhYmlsaXR5IHRvIGRl
dGVybWluZSBxdWlja2x5IGlmIHRoZSAobGF0ZW5jeSkgDQpwcm9ibGVtIGlzIGluIHRoZSBuZXR3
b3JrIG9yIGluIHRoZSBzZXJ2ZXIgKGFwcGxpY2F0aW9uKS4gIFRoYXQgaXMsDQppdCBpcyBhIGZh
c3Qgd2F5IHRvIGRvIHRyaWFnZS4NCg0KT25lIG9mIHRoZSBpbXBvcnRhbnQgZnVuY3Rpb25zIG9m
IFBETSBpcyB0byBhbGxvdyB5b3UgdG8gZG8gcXVpY2tseSBkaXNwYXRjaA0KdGhlIHJpZ2h0IHNl
dCBvZiBkaWFnbm9zdGljaWFucy4gIFdpdGhpbiBuZXR3b3JrIG9yIHNlcnZlciBsYXRlbmN5LA0K
dGhlcmUgbWF5IGJlIG1hbnkgY29tcG9uZW50cy4gIFRoZSBqb2Igb2YgdGhlIGRpYWdub3N0aWNp
YW4gaXMgdG8gcnVsZQ0KZWFjaCBvbmUgb3V0IHVudGlsIHRoZSBjdWxwcml0IGlzIGZvdW5kLg0K
DQpIb3cgUERNIGZpdHMgaW50byB0aGlzIGRpYWdub3N0aWMgcGljdHVyZSBpcyB0aGF0IFBETSB3
aWxsIHF1aWNrbHkgdGVsbCANCnlvdSBob3cgdG8gZXNjYWxhdGUuICBQRE0gd2lsbCBwb2ludCB0
byBlaXRoZXIgdGhlIG5ldHdvcmsgYXJlYSBvciB0aGUNCnNlcnZlciBhcmVhLiAgIFdpdGhpbiB0
aGUgc2VydmVyIGxhdGVuY3ksIFBETSBkb2VzIG5vdCB0ZWxsIHlvdSBpZiB0aGUgYm90dGxlbmVj
aw0KaXMgaW4gdGhlIElQIHN0YWNrIG9yIHRoZSBhcHBsaWNhdGlvbiBvciBidWZmZXIgYWxsb2Nh
dGlvbi4gV2l0aGluIHRoZSBuZXR3b3JrIGxhdGVuY3ksIA0KUERNIGRvZXMgbm90IHRlbGwgeW91
IHdoaWNoIG9mIHRoZSBuZXR3b3JrIHNlZ21lbnRzIG9yIG1pZGRsZSBib3hlcyBpcyBhdCBmYXVs
dC4gDQoNCldoYXQgUERNIHdpbGwgdGVsbCB5b3UgaXMgd2hldGhlciB0aGUgcHJvYmxlbSBpcyBp
biB0aGUgbmV0d29yayBvciB0aGUgc2VydmVyLiBJbiBvdXIgZXhwZXJpZW5jZSwgDQp0aGVyZSBp
cyBvZnRlbiBhIGRpZmZlcmVudCBncm91cCB3aGljaCBpcyBpbnZvbHZlZCB0byB0cm91Ymxlc2hv
b3QgdGhlIHByb2JsZW0gZGVwZW5kaW5nIG9uIHRoZSANCm5hdHVyZSBvZiB0aGUgcHJvYmxlbS4g
ICBUaGF0IGlzLCB0aGUgcHJvYmxlbSBtYXkgYmUgZXNjYWxhdGVkIHRvIHRoZSBhcHBsaWNhdGlv
biBkZXZlbG9wZXJzDQpvciB0aGUgdGVhbSB0aGF0IGRlYWxzIHdpdGggdGhlIHJvdXRlcnMgYW5k
IGluZnJhc3RydWN0dXJlLiAgQm90aCB0aGUgbmV0d29yayBncm91cCBhbmQgdGhlIA0KYXBwbGlj
YXRpb24gZ3JvdXAgaGF2ZSBxdWl0ZSBhIGZldyBzcGVjaWFsaXplZCB0b29scyBhdCB0aGVpciBk
aXNwb3NhbCB0byBmdXJ0aGVyIGludmVzdGlnYXRlIHRoZWlyDQpvd24gYXJlYXMuICAgV2hhdCBp
cyBtaXNzaW5nIGlzIHRoZSBmaXJzdCBzdGVwLCB3aGljaCBQRE0gcHJvdmlkZXMuDQoNCkluIG91
ciBleHBlcmllbmNlLCB2YWx1YWJsZSB0aW1lIGlzIG9mdGVuIGxvc3QgYXQgdGhpcyBmaXJzdCBz
dGFnZSBvZiB0cmlhZ2UuICBQRE0gaXMgZXhwZWN0ZWQgdG8NCnJlZHVjZSB0aGlzIHRpbWUgc3Vi
c3RhbnRpYWxseS4g

------=_Part_2617276_118908285.1487700770758--


From nobody Tue Feb 21 11:33:02 2017
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF4D21294D0 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 11:33:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WnMEwDvd4zR for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2017 11:32:59 -0800 (PST)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5551D129442 for <gen-art@ietf.org>; Tue, 21 Feb 2017 11:32:59 -0800 (PST)
Received: by mail-it0-x234.google.com with SMTP id d9so35801678itc.0 for <gen-art@ietf.org>; Tue, 21 Feb 2017 11:32:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cy8Ox+cZSlbkMN27RdXCdyU5h6ih0h9PWYqTJrF7u8A=; b=g3iE3ztkKycQ7OjRH+Y/SYRLeKMS04NBEvk/JNEcxNycMhaYT73jQNC8V43L4EACXA 2oBLPy4wQPptX4XyykmzzPiv0MyK8El6sYHcS9XuD1l5AY5vBznL+S9Wg1lVPSpJZ1xN vrzUzpnCGvm6AgXLW5nJKSBJabRbaOi/aFb3QMbY2kSAXGxtAfbk39bDd8Yp9WGATbg9 ltCC22HAmK8c8jDqnQB5t1n4cD4SoGbfcC79+ENfw9DECl99YYMNUSDnShYvTa6P3hME TuT9m5PiPpLknsDFR7WHQzMUI9KYIUtbriG82t3bSsm5gIvrX0QEB0sZdnHjqoty8ajk 6wXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cy8Ox+cZSlbkMN27RdXCdyU5h6ih0h9PWYqTJrF7u8A=; b=qaBU3rvtG7ZPsorKjLWTInVJD0eECF08sKNu7lEbNLDtBS2/jCCWP0tbUD+DyBMkSp ykUVwONJhzZjB1MejAN2CDFoZ6zK1ZUWYCjiTYijXYRFs56zFXrmrEl3e3tv+ShATC2f S7x9ThXXPQWqmQDzujGJdeqjET/S1XaQvPtCVQwl6p9R0CBplcGXjzooub7xhtu4j3tZ iLsy1INzwBgLXgaZ/FAdMizMtSuV7322YdpPC7PPyC+SLxnqMgIz9qbZVejTAopviU47 CxwLw7t7MH/JcuNXgZALv2t6nyQnGv5ZyhuRoxBah115IFO4PvwNPhAd3Vzj7WasEcGs S9aA==
X-Gm-Message-State: AMke39mtvi0UsrwyZBAhU5mdeFhmDuJaCxl8rHX9i2dkw34gXs29KgZ2o0Xf4+wJSgTdG3E4P8bXCGtmZPgcmw==
X-Received: by 10.36.117.148 with SMTP id y142mr26134618itc.14.1487705578725;  Tue, 21 Feb 2017 11:32:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.32.148 with HTTP; Tue, 21 Feb 2017 11:32:43 -0800 (PST)
In-Reply-To: <D4A67CE6.15FA6%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B4BF7D017@ESESSMB209.ericsson.se> <CAF4+nEGACaLibMcA5Xszz76xPmbdca22pEGh7bF7G=EFXHyhtg@mail.gmail.com> <D4A67CE6.15FA6%christer.holmberg@ericsson.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 21 Feb 2017 14:32:43 -0500
Message-ID: <CAF4+nEGVc-jpzyMxWU3GRytkwoAENTG=heGBSARPppEADbxT3Q@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114aace28ceca605490f7264
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/qFqeRcnJSqXASkAJbjdUuRPmBWE>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-trill-rfc6439bis.all@tools.ietf.org" <draft-ietf-trill-rfc6439bis.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-rfc6439bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:33:01 -0000

--001a114aace28ceca605490f7264
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Christer,

Version -05 of the draft, which was just posted, is intended to resolve
your comments.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Thu, Jan 19, 2017 at 7:47 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Donald,
>
> Please see inline.
>
> >> Also, in general, the document does expand some acronyms on first
> >> occurrence, while it does not expand others. Can the authors verify
> >>that all
> >> the acronyms NOT expanded so called =C2=B3well known=C2=B2 acronyms?
> >
> >Can you point to one that isn't well known?
>
> I didn=C2=B9t check - it was more a generic question whether you have che=
cked
> the non-expanded acronyms.
>
> But, looking in the Introduction:
>
> 1) I see that you have expanded LAN, but not VLAN. Both are well-known, s=
o
> they do not need to be enhanced.
>
> 2) LSP IS a well known acronym, and LSP actually have multiple meanings
> (perhaps they all mean the same thing).
>
> LSP        - Label Switched Path (LSP) or
>            - Label Switching Path (LSP) -- RARELY USED
>            - Link State Packet (LSP) or
>            - Link State PDU (LSP) (or Link State Protocol Data Unit)
>
>
> 3) FGL is not a well known acronym.
>
> 4) In the case of DRB you use the following format: 'enhanced (acronym)'.
> In other cases you use 'acronym (enhanced)=C2=B9. Please be consistent wh=
enever
> you do write both the acronym and the enhanced name.
>
> Having said that, DRB is a well known acronym, so I don=C2=B9t think you =
need
> to enhance it. Still, as it may be a "less known well known=C2=B2, a refe=
rence
> would still be useful.
>
> ...
>
> >> Q4:        The end of the introduction contains the following text:
> >>
> >> =C2=B3This documents obsoletes [RFC6439], updates [RFC6325], and updat=
es
> >> [RFC7177], as described in Appendix B.=C2=B2
> >>
> >> That=C2=B9s all good, but I think it would be good to have a few words=
 also
> >>in
> >> the Introduction, explaining exactly what is obsoleted and updated.
> >
> >OK, especially as it is more like it incorporates RFC 6439 to simplify
> >things and reduce the number of documents that implementers have to
> >look at.
>
>
> That is also very good information. The details can be in Appendix B, but
> I think it would be good to have a high-level description in the
> Introduction.
>
>
> >> Q5:        The end of the introduction contains the following text:
> >>
> >> =C2=B3It also includes reference implementation details.
> >>               Alternative implementations that interoperate on the wir=
e
> >>are
> >>               permitted.=C2=B2
> >>
> >> Is the last sentence really needed? I don=C2=B9t think an RFC can mand=
ate the
> >> usage of one specific implementation of the RFC.
> >
> >Well, I think the TRILL WG likes wording similar to that. It also
> >occurs in at least RFC 6325, the TRILL base protocol specification.
>
> Ok. I won=C2=B9t argue against it, I just think it sounds a little strang=
e :)
>
> But, could you then add a reference to the section describing the
> reference implementation details, because I don=C2=B9t think it is explic=
it
> anywhere.
>
> Also, if the reference implementation details are different from the ones
> in 6325 I think it would be useful to point out.
>
> Regards,
>
> Christer
>
>

--001a114aace28ceca605490f7264
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Christer,<div><br></div><div>Version -05 of the draft, =
which was just posted, is intended to resolve your comments.</div><div><br>=
</div><div class=3D"gmail_extra"><div><div class=3D"gmail_signature" data-s=
martmail=3D"gmail_signature">Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
=C2=A0Donald E. Eastlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A0155 Bea=
ver Street, Milford, MA 01757 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gmail.c=
om" target=3D"_blank">d3e3e3@gmail.com</a></div></div>
<br><div class=3D"gmail_quote">On Thu, Jan 19, 2017 at 7:47 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Hi Donald,<br>
<br>
Please see inline.<br>
<span class=3D""><br>
&gt;&gt; Also, in general, the document does expand some acronyms on first<=
br>
&gt;&gt; occurrence, while it does not expand others. Can the authors verif=
y<br>
&gt;&gt;that all<br>
&gt;&gt; the acronyms NOT expanded so called =C2=B3well known=C2=B2 acronym=
s?<br>
&gt;<br>
&gt;Can you point to one that isn&#39;t well known?<br>
<br>
</span>I didn=C2=B9t check - it was more a generic question whether you hav=
e checked<br>
the non-expanded acronyms.<br>
<br>
But, looking in the Introduction:<br>
<br>
1) I see that you have expanded LAN, but not VLAN. Both are well-known, so<=
br>
they do not need to be enhanced.<br>
<br>
2) LSP IS a well known acronym, and LSP actually have multiple meanings<br>
(perhaps they all mean the same thing).<br>
<br>
LSP=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Label Switched Path (LSP) or<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Label Switching Path (LSP) -- RA=
RELY USED<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Link State Packet (LSP) or<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Link State PDU (LSP) (or Link St=
ate Protocol Data Unit)<br>
<br>
<br>
3) FGL is not a well known acronym.<br>
<br>
4) In the case of DRB you use the following format: &#39;enhanced (acronym)=
&#39;.<br>
In other cases you use &#39;acronym (enhanced)=C2=B9. Please be consistent =
whenever<br>
you do write both the acronym and the enhanced name.<br>
<br>
Having said that, DRB is a well known acronym, so I don=C2=B9t think you ne=
ed<br>
to enhance it. Still, as it may be a &quot;less known well known=C2=B2, a r=
eference<br>
would still be useful.<br>
<br>
...<br>
<span class=3D""><br>
&gt;&gt; Q4:=C2=A0 =C2=A0 =C2=A0 =C2=A0 The end of the introduction contain=
s the following text:<br>
&gt;&gt;<br>
&gt;&gt; =C2=B3This documents obsoletes [RFC6439], updates [RFC6325], and u=
pdates<br>
&gt;&gt; [RFC7177], as described in Appendix B.=C2=B2<br>
&gt;&gt;<br>
&gt;&gt; That=C2=B9s all good, but I think it would be good to have a few w=
ords also<br>
&gt;&gt;in<br>
&gt;&gt; the Introduction, explaining exactly what is obsoleted and updated=
.<br>
&gt;<br>
&gt;OK, especially as it is more like it incorporates RFC 6439 to simplify<=
br>
&gt;things and reduce the number of documents that implementers have to<br>
&gt;look at.<br>
<br>
<br>
</span>That is also very good information. The details can be in Appendix B=
, but<br>
I think it would be good to have a high-level description in the<br>
Introduction.<br>
<span class=3D""><br>
<br>
&gt;&gt; Q5:=C2=A0 =C2=A0 =C2=A0 =C2=A0 The end of the introduction contain=
s the following text:<br>
&gt;&gt;<br>
&gt;&gt; =C2=B3It also includes reference implementation details.<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Alternative =
implementations that interoperate on the wire<br>
&gt;&gt;are<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0permitted.=
=C2=B2<br>
&gt;&gt;<br>
&gt;&gt; Is the last sentence really needed? I don=C2=B9t think an RFC can =
mandate the<br>
&gt;&gt; usage of one specific implementation of the RFC.<br>
&gt;<br>
&gt;Well, I think the TRILL WG likes wording similar to that. It also<br>
&gt;occurs in at least RFC 6325, the TRILL base protocol specification.<br>
<br>
</span>Ok. I won=C2=B9t argue against it, I just think it sounds a little s=
trange :)<br>
<br>
But, could you then add a reference to the section describing the<br>
reference implementation details, because I don=C2=B9t think it is explicit=
<br>
anywhere.<br>
<br>
Also, if the reference implementation details are different from the ones<b=
r>
in 6325 I think it would be useful to point out.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote></div><br></div></div>

--001a114aace28ceca605490f7264--


From nobody Tue Feb 21 11:33:59 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D88131294BF; Tue, 21 Feb 2017 11:33:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148770562388.19070.16770867288080366155.idtracker@ietfa.amsl.com>
Date: Tue, 21 Feb 2017 11:33:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/L_k9j59tEt3d4A5BMlsnQ637_IE>
Cc: draft-ietf-ccamp-ospf-availability-extension.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-ccamp-ospf-availability-extension-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:33:44 -0000

Reviewer: Jouni Korhonen
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ccamp-ospf-availability-extension-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-21
IETF LC End Date: 2016-10-24
IESG Telechat date: 2017-03-16

Summary:

I have reviewed two earlier versions of this document. All my comments
have been addressed. I am also happy to see my earlier comments
generated (I believe) a draft addressing the generalized SCSI TLV
specification work in TEAS, and this draft referencing to that work.

Major issues:

none.

Minor issues:

none.

Nits/editorial comments: 

There are minor editorials here and there, but those will be picked up
by the RFC editor in any case.


From nobody Tue Feb 21 15:29:08 2017
Return-Path: <nrooney@gsma.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885701293DF; Tue, 21 Feb 2017 15:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gsmasso.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8c4av7skV_0; Tue, 21 Feb 2017 15:28:55 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0066.outbound.protection.outlook.com [104.47.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71DF21204D9; Tue, 21 Feb 2017 15:28:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=GSMASSO.onmicrosoft.com; s=selector1-gsma-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=6gYsPkN2X4IWhAAmUHZhoKkTQ3QWAJTPSl4GK0E9/dA=; b=iXgGDNAoP7dsubF5/cLUyvW89P9uNSTwtNikM3rWx0pbiGaRlVMFsJNX3esjv7I1B28pWAQ+R8VjYBlHu0DoEiZnNU5AZ7aRZpiY2C3ZpuV7AmlU6glaKFgXONvnmWxwekqRGZMqD7zTQhym6xij7C+48eSthfeY9NqkSTUU4H0=
Received: from HE1PR04MB3113.eurprd04.prod.outlook.com (10.171.196.31) by HE1PR04MB3116.eurprd04.prod.outlook.com (10.171.196.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Tue, 21 Feb 2017 23:28:51 +0000
Received: from HE1PR04MB3113.eurprd04.prod.outlook.com ([10.171.196.31]) by HE1PR04MB3113.eurprd04.prod.outlook.com ([10.171.196.31]) with mapi id 15.01.0919.018; Tue, 21 Feb 2017 23:28:51 +0000
From: Natasha Rooney <nrooney@gsma.com>
To: Dale Worley <worley@ariadne.com>, "slim@ietf.org" <slim@ietf.org>
Thread-Topic: Review of draft-ietf-slim-negotiating-human-language-06
Thread-Index: AQHSiY9AG5SIuWMvTkWvq4pl7gSV96F0IWOA
Date: Tue, 21 Feb 2017 23:28:50 +0000
Message-ID: <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
In-Reply-To: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nrooney@gsma.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.39.120.58]
x-ms-office365-filtering-correlation-id: b1762689-c66c-48c4-64f5-08d45ab164ab
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR04MB3116;
x-microsoft-exchange-diagnostics: 1; HE1PR04MB3116; 7:qs5+nnuX0DtYS8RoxUf1I18DpTDPshEzm+uo1/rvUyBm4byHHnWwza8a2l2Qv+p61CRqGXim7FxRw7XIzz4p+qgAEqWcCHo4S1BYT8Kjg4Wqf4vJE9RSqVjwB17D7qKHg+91gfgW1JfRszpq51UH94Y/9W2L3lJO4LDsnCgBS6Uv9kyVUjGcFucOToah0NatAdZ5Pbubvfv0ATkufh3YJ6MASJxz1N8WpB5VKdiGMJwxwZ5JDK/b4SGH+0zy1EK56TQGznWaVP/5jNXTlf1w78tO8vM+VGpIvgpEaP1/ALeiyu8UBTG7TOKbvMoh+Gn2zWtK8p1aJohmhdCrgqg/zw==
x-microsoft-antispam-prvs: <HE1PR04MB311636487A0B8ACC21D3F164C3510@HE1PR04MB3116.eurprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123558025)(20161123560025)(6072148); SRVR:HE1PR04MB3116; BCL:0; PCL:0; RULEID:; SRVR:HE1PR04MB3116; 
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(51914003)(189002)(377424004)(199003)(66654002)(24454002)(50986999)(5660300001)(76176999)(36756003)(122556002)(2950100002)(38730400002)(6246003)(53936002)(2906002)(77096006)(606005)(83716003)(5890100001)(6506006)(57306001)(66066001)(102836003)(6486002)(229853002)(6116002)(2501003)(3846002)(6306002)(25786008)(6436002)(82746002)(6512007)(54896002)(99286003)(236005)(54906002)(92566002)(97736004)(189998001)(4326007)(3280700002)(86362001)(3660700001)(68736007)(33656002)(2900100001)(53546006)(50226002)(105586002)(7906003)(106116001)(81166006)(81156014)(7736002)(106356001)(8676002)(8936002)(101416001)(561944003)(230783001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR04MB3116; H:HE1PR04MB3113.eurprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: gsma.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_"
MIME-Version: 1.0
X-OriginatorOrg: gsma.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Feb 2017 23:28:50.8396 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72a4ff82-fec3-469d-aafb-ac8276216699
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR04MB3116
X-MS-Exchange-CrossPremises-AuthAs: Internal
X-MS-Exchange-CrossPremises-AuthMechanism: 04
X-MS-Exchange-CrossPremises-AuthSource: HE1PR04MB3113.eurprd04.prod.outlook.com
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-messagesource: StoreDriver
X-MS-Exchange-CrossPremises-BCC: 
X-MS-Exchange-CrossPremises-originalclientipaddress: 217.39.120.58
X-MS-Exchange-CrossPremises-avstamp-service: 1.0
X-MS-Exchange-CrossPremises-disclaimer-hash: 78ca8040c6722e32c2f5b0a45bf37e74b9409d645a53be96aa19958e0cee0f00
X-MS-Exchange-CrossPremises-antispam-scancontext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-MS-Exchange-CrossPremises-processed-by-journaling: Journal Agent
X-OrganizationHeadersPreserved: HE1PR04MB3116.eurprd04.prod.outlook.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_AaCOoSm7zIkpD5HsTl_K5PQjzc>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-slim-negotiating-human-language.all@ietf.org" <draft-ietf-slim-negotiating-human-language.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 23:28:59 -0000

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgRGFsZSEgTWFueSB0aGFua3MgZm9yIHRoZXNlIGNvbW1lbnRzLCBhcyBvbmUgb2YgdGhlIFNM
SU0gY2hhaXJzIEnigJlsbCB3b3JrIG9uIGdldHRpbmcgc29tZSBhbnN3ZXJzIHRvIHlvdSBvciBJ
4oCZbGwgcmVxdWVzdCB0aGUgYXV0aG9yIG9yIG9uZSBvZiB0aGUgU0xJTSBhY3RpdmUgcGFydGlj
aXBhbnRzIHRvIHJlc3BvbmQuDQoNCkJlcm5hcmQsIFJhbmRhbGwgYW5kIFNMSU0gLSBzZWUgYmVs
b3cgcmUgRGFsZeKAmXMgcG9pbnRzLg0KDQoqKioqIEEuIENhbGwgZmFpbHVyZSAqKioqDQpSYW5k
YWxsIG9yIEJlcm5hcmQgY2FuIHlvdSByZXNwb25kIHRvIHRoaXM/IEkgaW1hZ2luZSB0aGUgVUEg
Y2FsbCBmYWlsdXJlIG1ldGhvZCBpcyBVQSBzcGVjaWZpYywgYnV0IGlmIHRoZXJlIGlzIGEgY2xh
c2ggd2l0aCBTSVAgbGV2ZWwgY2FsbCBmYWlsIHRoZW4gdGhpcyBzaG91bGQgYmUgYWRkcmVzc2Vk
Lg0KDQoqKioqIEIuIEF1ZGlvL1ZpZGVvIGNvb3JkaW5hdGlvbiAqKioqDQpJIGJlbGlldmUgdGhl
IHRoZW9yeSBiZWhpbmQgdGhlIGN1cnJlbnQgZHJhZnQgaXMgdGhhdCB0aGUgc3Bva2VuIGFuZCB2
aWRlbyBzdHJlYW1zIHdpbGwgYmUgZGlmZmVyZW50IGluIHRoZSBjYXNlcyBvZiBzdWNoIHRoaW5n
cyBhcyBzaWduIGxhbmd1YWdlLiBWaWRlbyBjb3VsZCB0aGVyZWZvcmUgYmUgc2lnbiBhbmQgYXVk
aW8gd291bGQgYmUgYSBzcG9rZW4gbGFuZ3VhZ2UuIEnigJltIG5vdCBzdXJlIGlmIHRoZSBzdWdn
ZXN0aW9uIGhlIHNhdGlzZmllcyB0aGlzIGNhc2U/DQoNCioqKiogQy4gImh1bWludGxhbmciIHNl
ZW1zIGxvbmcgdG8gbWUgKioqKg0KQmVybmFyZCAtIEkgZG9u4oCZdCBzZWUgdGhlIGlzc3VlIHdp
dGggc2hvcnRlbmluZyBodW1pbnRsYW5nLCBidXQgdGhlIGdyb3VwIG1pZ2h0LiBJIHN1Z2dlc3Qg
d2UgdGhyb3cgdGhpcyB0byB0aGUgZ3JvdXAgZm9yIGRpc2N1c3Npb24uDQoNCioqKiogRC4gVXNl
IHRoZSBBY2NlcHQtTGFuZ3VhZ2Ugc3ludGF4ICoqKioNClJhbmRhbGwgYW5kIEJlcm5hcmQgLSBp
cyB0aGlzIGFuIGFjY2VwdGFibGUgY2hhbmdlPyBPciBvbmUgd2UgbmVlZCB0byBkaXNjdXNzIGZ1
cnRoZXIuIFNlZW1zIGxpa2UgYSByZWFzb25hYmxlIHJlcXVlc3QsIGJ1dCBhbHNvIGEgbGFyZ2Vy
IGNoYW5nZSwgd2hpY2ggaXMgd2h5IEkgYXNrIQ0KDQoqKioqIEUuIEhhdmUgYW4gYXR0cmlidXRl
IHRvIGFiYnJldmlhdGUgdGhlIGJpZGlyZWN0aW9uYWxseS1zeW1tZXRyaWMgY2FzZSAqKioqDQpJ
IGRvIG5vdCByZW1lbWJlciB1cyBoYXZpbmcgdGhpcyBkaXNjdXNzaW9uIHdpdGhpbiB0aGUgZ3Jv
dXAsIGFsdGhvdWdoIGl0IG1heSBoYXZlIG9jY3VycmVkIGJlZm9yZSBJIGJlY2FtZSBjaGFpci4N
ClJhbmRhbGwsIEJyaWFuIG9yIEJlcm5hcmQgLSBoYXMgdGhpcyBpZGVhIGJlZW4gZGlzY3Vzc2Vk
IGJlZm9yZT8gSWYgc28sIGNhbiBvbmUgb2YgeW91IHJlc3BvbmQgd2l0aCBhbiBleHBsYW5hdGlv
biBhcyB0byB3aHkgd2UgaGF2ZW7igJl0IGRvbmUgdGhpcz8NCg0KKioqKiBFZGl0b3JpYWwgY29t
bWVudHMgYW5kIG5pdHMgKioqKioNClJhbmRhbGwgLSBjYW4geW91IHRha2UgYSBsb29rIHRocm91
Z2ggRGFsZeKAmXMgZWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBzaG91dCBpZiB0aGVyZSBpcyBhbnkg
cHJvYmxlbXMgd2l0aCB0aGVzZSBzdWdnZXN0aW9uczsgaWYgZXZlcnl0aGluZyBpcyBvayBwbGVh
c2UgbWFrZSB0aGUgY2hhbmdlcy4NCg0KVGhhbmtzIGFsbCENCg0KTmF0YXNoYSBSb29uZXkgfCBJ
bnRlcm5ldCBFbmdpbmVlcmluZyBEaXJlY3RvciB8IEludGVybmV0IGFuZCBXZWIgVGVhbSB8IFRl
Y2hub2xvZ3kgfCBHU01BIHwgbnJvb25leUBnc21hLmNvbTxtYWlsdG86bnJvb25leUBnc21hLmNv
bT4gfCArNDQgKDApIDc3MzAgMjE5IDc2NSB8IEB0aGlzTmF0YXNoYSB8IFNreXBlOiBucm9vbmV5
QGdzbS5vcmc8bWFpbHRvOm5yb29uZXlAZ3NtLm9yZz4NCg0KT24gMTggRmViIDIwMTcsIGF0IDAy
OjMyLCBEYWxlIFdvcmxleSA8d29ybGV5QGFyaWFkbmUuY29tPG1haWx0bzp3b3JsZXlAYXJpYWRu
ZS5jb20+PiB3cm90ZToNCg0KUmV2aWV3ZXI6IERhbGUgV29ybGV5DQpSZXZpZXcgcmVzdWx0OiBS
ZWFkeSB3aXRoIE5pdHMNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3Ig
dGhpcyBkcmFmdC4gIFRoZSBHZW5lcmFsIEFyZWENClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZp
ZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQNCmJ5IHRoZSBJRVNHIGZvciB0
aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQpsaWtlIGFu
eSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQNCjxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCg0KRG9jdW1lbnQ6ICBkcmFmdC1pZXRmLXNsaW0tbmVnb3Rp
YXRpbmctaHVtYW4tbGFuZ3VhZ2UtMDYNClJldmlld2VyOiAgRGFsZSBSLiBXb3JsZXkNClJldmll
dyBEYXRlOiAgMjAxNy0wMi0xNw0KSUVURiBMQyBFbmQgRGF0ZTogIDIwMTctMDItMjANCklFU0cg
VGVsZWNoYXQgZGF0ZTogIFt1bmtub3duXQ0KDQpTdW1tYXJ5Og0KICAgICAgVGhpcyBkcmFmdCBp
cyBiYXNpY2FsbHkgcmVhZHkgZm9yIHB1YmxpY2F0aW9uLCBidXQgaGFzIG5pdHMNCiAgICAgIHRo
YXQgc2hvdWxkIGJlIGZpeGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4NCg0KKiBUZWNobmljYWwgY29t
bWVudHMNCg0KQS4gQ2FsbCBmYWlsdXJlDQoNCklmIGEgY2FsbCBmYWlscyBkdWUgdG8gbm8gYXZh
aWxhYmxlIGxhbmd1YWdlIG1hdGNoLCBpbiB3aGF0IHdheShzKQ0KZG9lcyBpdCBmYWlsPyAgU2Vj
dGlvbiA1LjMgc2F5cw0KDQogIElmIHN1Y2ggYW4gb2ZmZXIgaXMgcmVjZWl2ZWQsIHRoZSByZWNl
aXZlciBNQVkNCiAgcmVqZWN0IHRoZSBtZWRpYSwgaWdub3JlIHRoZSBsYW5ndWFnZSBzcGVjaWZp
ZWQsIG9yIGF0dGVtcHQgdG8NCiAgaW50ZXJwcmV0IHRoZSBpbnRlbnQNCg0KQnV0IEkgc3VzcGVj
dCBpdCdzIGFsc28gYWxsb3dlZCBmb3IgdGhlIFVBUyB0byBmYWlsIHRoZSBjYWxsIGF0IHRoZQ0K
U0lQIGxldmVsLiAgV2hldGhlciBvciBub3QgdGhhdCBpcyBhbGxvd2VkIChvciBhdCBsZWFzdCBl
bnZpc2lvbmVkKQ0Kc2hvdWxkIGJlIGRlc2NyaWJlZC4gIEFuZCB3aGF0IHJlc3BvbnNlIGNvZGUo
cykvd2Fybi1jb2RlKHMpIHNob3VsZA0KYmUNCnVzZWQgZm9yIHRoYXQ/DQoNCkIuIEF1ZGlvL1Zp
ZGVvIGNvb3JkaW5hdGlvbg0KDQogIDUuMi4gIE5ldyAnaHVtaW50bGFuZy1zZW5kJyBhbmQgJ2h1
bWludGxhbmctcmVjdicgYXR0cmlidXRlcw0KDQogIE5vdGUgdGhhdCB3aGlsZSBzaWduZWQgbGFu
Z3VhZ2UgdGFncyBhcmUgdXNlZCB3aXRoIGEgdmlkZW8gc3RyZWFtDQp0bw0KICBpbmRpY2F0ZSBz
aWduIGxhbmd1YWdlLCBhIHNwb2tlbiBsYW5ndWFnZSB0YWcgZm9yIGEgdmlkZW8gc3RyZWFtDQpp
bg0KICBwYXJhbGxlbCB3aXRoIGFuIGF1ZGlvIHN0cmVhbSB3aXRoIHRoZSBzYW1lIHNwb2tlbiBs
YW5ndWFnZSB0YWcNCiAgaW5kaWNhdGVzIGEgcmVxdWVzdCBmb3IgYSBzdXBwbGVtZW50YWwgdmlk
ZW8gc3RyZWFtIHRvIHNlZSB0aGUNCiAgc3BlYWtlci4NCg0KQW5kIHRoZXJlJ3MgYSBzaW1pbGFy
IHBhcmFncmFwaCBpbiA1LjQ6DQoNCiAgQSBzcG9rZW4gbGFuZ3VhZ2UgdGFnIGZvciBhIHZpZGVv
IHN0cmVhbSBpbiBjb25qdW5jdGlvbiB3aXRoIGFuDQphdWRpbw0KICBzdHJlYW0gd2l0aCB0aGUg
c2FtZSBsYW5ndWFnZSBtaWdodCBpbmRpY2F0ZSBhIHJlcXVlc3QgZm9yDQogIHN1cHBsZW1lbnRh
bCB2aWRlbyB0byBzZWUgdGhlIHNwZWFrZXIuDQoNCkkgdGhpbmsgdGhpcyBtZWNoYW5pc20gbmVl
ZHMgdG8gYmUgZGVzY3JpYmVkIG1vcmUgZXhhY3RseSwgYW5kIGluDQpwYXJ0aWN1bGFyLCBpdCBz
aG91bGQgbm90IGRlcGVuZCBvbiB0aGUgVUEgdW5kZXJzdGFuZGluZyB3aGljaA0KbGFuZ3VhZ2Ug
dGFncyBhcmUgc3Bva2VuIGxhbmd1YWdlIHRhZ3MuICBJdCBzZWVtcyB0byBtZSB0aGF0IGENCndv
cmthYmxlIHJ1bGUgaXMgdGhhdCB0aGVyZSBpcyBhbiBhdWRpbyBzdHJlYW0gYW5kIGEgdmlkZW8g
c3RyZWFtIGFuZA0KdGhleSBzcGVjaWZ5IGV4YWN0bHkgdGhlIHNhbWUgbGFuZ3VhZ2UgdGFnIGlu
IHRoZWlyIHJlc3BlY3RpdmUNCmh1bWludGxhbmcgYXR0cmlidXRlcy4gIEluIHRoYXQgY2FzZSwg
aXQgaXMgYSByZXF1ZXN0IGZvciBhIHNwb2tlbg0KbGFuZ3VhZ2Ugd2l0aCBzaW11bHRhbmVvdXMg
dmlkZW8gb2YgdGhlIHNwZWFrZXIsIGFuZCB0aG9zZSByZXF1ZXN0cw0Kc2hvdWxkIGJlIGNvbnNp
ZGVyZWQgc2F0aXNmaWVkIG9ubHkgaWYgYm90aCBzdHJlYW1zIGNhbiBiZQ0KZXN0YWJsaXNoZWQu
DQoNCiogVGhlIGZvbGxvd2luZyB0aHJlZSBpdGVtcyBhcmUgYWRqdXN0bWVudHMgdG8gdGhlIGRl
c2lnbiB3aGljaCBJJ2QNCmxpa2UgdG8ga25vdyBoYXZlIGJlZW4gY29uc2lkZXJlZC4NCg0KQy4g
Imh1bWludGxhbmciIHNlZW1zIGxvbmcgdG8gbWUNCg0KR2l2ZW4gdGhlIGV4Y2Vzc2l2ZSBsZW5n
dGggb2YgU0RQIGluIHByYWN0aWNlLCBpdCBzZWVtcyB0byBtZSB0aGF0IGENCnNob3J0ZXIgYXR0
cmlidXRlIG5hbWUgd291bGQgYmUgZGVzaXJhYmxlLiAgRS5nLiwgImh1bWxhbmciIGFzIHdhcw0K
dXNlZCBpbiBzb21lIHByZXZpb3VzIHZlcnNpb25zLiAgT3IgaXMgdGhlcmUgYSBjb29yZGluYXRl
ZCB1c2FnZSB3aXRoDQpvdGhlciBuYW1lcyBpbiB0aGUgImh1bSpsYW5nIiBwYXR0ZXJuPw0KDQpE
LiBVc2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXgNCg0KSXQgc2VlbXMgdG8gbWUgdGhhdCBp
dCB3b3VsZCBiZXR0ZXIgdG8gdXNlIHRoZSBBY2NlcHQtTGFuZ3VhZ2Ugc3ludGF4DQpmb3IgdGhl
IGF0dHJpYnV0ZSB2YWx1ZXMuICBUaGlzIGFsbG93cyAoMSkgc3BlY2lmaXlpbmcgdGhlIHF1YWxp
dHkgb2YNCmxhbmd1YWdlIGV4cGVyaWVuY2UsIGFsbG93aW5nIGNsZWFyIGRlc2NyaXB0aW9uIG9m
IGJpbGluZ3VhbGlzbSwgKDIpDQphDQp1bmlmaWVkIG1ldGhvZCBvZiBzcGVjaWZ5aW5nIHdoZXRo
ZXIgb3Igbm90IGFyYml0cmFyeSBsYW5ndWFnZXMgYXJlDQphY2NlcHRhYmxlLCBhbmQgKDMpIGFi
YnJldmlhdGluZyBTRFAgZGVzY3JpcHRpb25zLg0KDQpJbiBhIHdheSwgdGhlIGZhY3QgdGhhdCB0
aGUgY3VycmVudCBwcm9wb3NhbCBzZWVtcyB0byByZXF1aXJlIChidXQNCmRvZXMgbm90IGRpcmVj
dGx5IHNwZWNpZnkpIHRoZSBjb29yZGluYXRlZCBhYnNlbmNlL3ByZXNlbmNlIG9mIGFuDQphc3Rl
cmlzayBvbiBhbGwgb2YgdGhlIHJlcGV0aXRpb25zIG9mIGh1bWludGxhbmctc2VuZCBvcg0KaHVt
aW50bGFuZy1yZWN2IGlzIGEgd2FybmluZyB0aGF0IHRoZSBzeW50YXggZG9lc24ndCByZXByZXNl
bnQgdGhlDQpzZW1hbnRpY3MgYXMgd2VsbCBhcyBpdCBtaWdodC4NCg0KRS4gSGF2ZSBhbiBhdHRy
aWJ1dGUgdG8gYWJicmV2aWF0ZSB0aGUgYmlkaXJlY3Rpb25hbGx5LXN5bW1ldHJpYyBjYXNlDQoN
Ck5vdGUgdGhhdCBhbGwgZXhhbXBsZXMgYXJlIGJpZGlyZWN0aW9uYWxseSBzeW1tZXRyaWMsIGFu
ZCB0aGUgdGV4dA0Kc2F5cyB0aGF0IHJlcXVlc3RzIGFuZCByZXNwb25zZXMgU0hPVUxEIGJlIGJp
ZGlyZWN0aW9uYWxseSBzeW1tZXRyaWMuDQpTbyBpdCB3b3VsZCBiZSBhIHZlcnkgdXNlZnVsIGFi
YnJldmlhdGlvbiB0byBkZWZpbmUNCiJodW1pbnRsYW5nPTx2YWx1ZT4iIHRvIGJlIGVxdWl2YWxl
bnQgdG8gdGhlIGNvbWJpbmF0aW9uIG9mDQoiaHVtaW50bGFuZy1zZW5kPTx2YWx1ZT4iIGFuZCAi
aHVtaW50bGFuZy1yZWN2PTx2YWx1ZT4iLg0KDQpDb21iaW5pbmcgcHJvcG9zYWxzIEMsIEQsIGFu
ZCBFLCB0aGUgZXhhbXBsZXMgYmVjb21lDQoNCiAgICAgbT1hdWRpbyA0OTE3MCBSVFAvQVZQIDAN
CiAgICAgYT1odW1sYW5nOmVuDQoNCiAgICAgbT12aWRlbyA1MTM3MiBSVFAvQVZQIDMxIDMyDQog
ICAgIGE9aHVtbGFuZzphc2UsKjtxPTAuMQ0KDQogICAgIG09YXVkaW8gNDkyNTAgUlRQL0FWUCAy
MA0KICAgICBhPWh1bWxhbmc6ZXMsZXU7cT0wLjksZW47cT0wLjgsKjtxPTAuMQ0KDQogICAgIG09
dGV4dCA0NTAyMCBSVFAvQVZQIDEwMyAxMDQNCiAgICAgYT1odW1sYW5nOmdyDQoNCndoaWNoIHJl
cXVpcmVzIGFib3V0IGhhbGYgYXMgbWFueSBjaGFyYWN0ZXJzIGFzIHRoZXkgaGF2ZSBub3cuDQoN
CiogRWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBuaXRzDQoNCkFic3RyYWN0DQoNCiAgVGhpcyBkb2N1
bWVudCBkZXNjcmliZXMgdGhlIG5lZWQgYW5kIGEgc29sdXRpb24gdXNpbmcgbmV3IFNEUA0Kc3Ry
ZWFtDQogIGF0dHJpYnV0ZXMuDQoNCkkgZG9uJ3QgdGhpbmsgdGhlIHRlcm0gInN0cmVhbSBhdHRy
aWJ1dGUiIGlzIHVzZWQgaW4gUkZDIDQ1NjYuDQpJbnN0ZWFkLCBpdCB1c2VzICJtZWRpYSBhdHRy
aWJ1dGUiLg0KDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgY2FsbGVyIGFuZCBjYWxsZWUga25vdyBl
YWNoIG90aGVyIG9yIHRoZXJlIGlzIGNvbnRleHR1YWwgb3Igb3V0IG9mDQogIGJhbmQgaW5mb3Jt
YXRpb24gZnJvbSB3aGljaCB0aGUgbGFuZ3VhZ2UocykgYW5kIG1lZGlhIG1vZGFsaXRpZXMNCmNh
bg0KDQpJIHRoaW5rIHRoaXMgY29udGV4dCwgaXQncyBwcmVmZXJyZWQgdG8gaHlwaGVuYXRlICJv
dXQtb2YtYmFuZCIgdG8NCm1ha2UgaXQgY2xlYXJseSBiZSBhbiBhZGplY3RpdmUuDQoNCiAgVGhp
cyBhcHByb2FjaCBoYXMgYSBudW1iZXIgb2YgYmVuZWZpdHMsIGluY2x1ZGluZyB0aGF0IGl0IGlz
DQpnZW5lcmljDQogIChhcHBsaWVzIHRvIGFsbCBpbnRlcmFjdGl2ZSBjb21tdW5pY2F0aW9ucyBu
ZWdvdGlhdGVkIHVzaW5nIFNEUCkNCmFuZA0KICBub3QgbGltaXRlZCB0byBlbWVyZ2VuY3kgY2Fs
bHMuDQoNCkkgdGhpbmsgcy9hbmQgbm90IGxpbWl0ZWQgdG8vYW5kIGlzIG5vdCBsaW1pdGVkIHRv
LyByZWFkcyBtb3JlDQpzbW9vdGhseS4NCg0KICBCdXQgaXQgaXMgY2xlYXJseSB1c2VmdWwgaW4g
bWFueSBvdGhlciBjYXNlcy4gIEZvcg0KICBleGFtcGxlLCBzb21lb25lIGNhbGxpbmcgYSBjb21w
YW55IGNhbGwgY2VudGVyIG9yIGEgUHVibGljIFNhZmV0eQ0KICBBbnN3ZXJpbmcgUG9pbnQgKFBT
QVApIHNob3VsZCBiZSBhYmxlIHRvIGluZGljYXRlIGlmIG9uZSBvciBtb3JlDQogIHNwZWNpZmlj
IHNpZ25lZCwgd3JpdHRlbiwgYW5kL29yIHNwb2tlbiBsYW5ndWFnZXMgYXJlIHByZWZlcnJlZCwN
CnRoZQ0KICBjYWxsZWUgc2hvdWxkIGJlIGFibGUgdG8gaW5kaWNhdGUgaXRzIGNhcGFiaWxpdGll
cyBpbiB0aGlzIGFyZWEsDQphbmQNCiAgdGhlIGNhbGwgcHJvY2VlZCB1c2luZyBpbi1jb21tb24g
bGFuZ3VhZ2UocykgYW5kIG1lZGlhIGZvcm1zLg0KDQpJIHRoaW5rIHMvcHJlZmVycmVkLCB0aGUg
Y2FsbGVlL3ByZWZlcnJlZDsgdGhlIGNhbGxlZS8gYmVjYXVzZSB0aGUNCnNlbnRlbmNlIGlzIHRo
ZSBjb25jYXRlbmF0aW9uIG9mIHR3byBzZW50ZW5jZXMuDQoNClBlcmhhcHMgcy9pbi1jb21tb24v
c2hhcmVkLy4NCg0KICBJbmNsdWRpbmcgdGhlIHVzZXIncyBodW1hbiAobmF0dXJhbCkgbGFuZ3Vh
Z2UgcHJlZmVyZW5jZXMgaW4gdGhlDQogIHNlc3Npb24gZXN0YWJsaXNobWVudCBuZWdvdGlhdGlv
biBpcyBpbmRlcGVuZGVudCBvZiB0aGUgdXNlIG9mIGENCiAgcmVsYXkgc2VydmljZSBhbmQgaXMg
dHJhbnNwYXJlbnQgdG8gYSB2b2ljZSBzZXJ2aWNlIHByb3ZpZGVyLg0KDQpJIHRoaW5rIGl0J3Mg
ZXZlbiBicm9hZGVyIHRoYW4gInRyYW5zcGFyZW50IHRvIGEgdm9pY2Ugc2VydmljZQ0KcHJvdmlk
ZXIiIC0tIGl0J3MgdHJhbnNwYXJlbnQgdG8gYW55IHNlcml2aWNlIHByb3ZpZGVyLCBhc3N1bWlu
ZyB0aGF0DQp0aGUgbWVkaWEgYXJlIGxhbmd1YWdlLW5ldXRyYWwuDQoNCiAgSW4gdGhlIGNhc2Ug
b2YgYSBjYWxsIHRvIGUuZy4sIGFuIGFpcmxpbmUsIHRoZSBjYWxsIGNvdWxkIGJlDQogIGF1dG9t
YXRpY2FsbHkgaGFuZGxlZCBieSBhIFNwYW5pc2gtc3BlYWtpbmcgYWdlbnQuDQoNCkkgdGhpbmsg
cy9oYW5kbGVkIGJ5L3JvdXRlZCB0by8gaXMgdGhlIHVzdWFsIHVzYWdlLg0KDQozLiAgRGVzaXJl
ZCBTZW1hbnRpY3MNCg0KICBUaGUgZGVzaXJlZCBzb2x1dGlvbiBpcyBhIG1lZGlhIGF0dHJpYnV0
ZSAocHJlZmVyYWJseSBwZXINCmRpcmVjdGlvbikNCiAgdGhhdCBtYXkgYmUgdXNlZCB3aXRoaW4g
YW4gb2ZmZXIgdG8gaW5kaWNhdGUgdGhlIHByZWZlcnJlZA0KbGFuZ3VhZ2UNCiAgb2YgZWFjaCAo
ZGlyZWN0aW9uIG9mIGEpIG1lZGlhIHN0cmVhbSwgYW5kIHdpdGhpbiBhbiBhbnN3ZXIgdG8NCiAg
aW5kaWNhdGUgdGhlIGFjY2VwdGVkIGxhbmd1YWdlLg0KDQpJbiB0aGlzIG9uZSBpbnN0YW5jZSwg
SSB0aGluayB5b3Ugd2FudCB0byB1c2UgImxhbmd1YWdlKHMpIiB0byBkcml2ZQ0KaG9tZSB0aGF0
IHRoYXQgbXVsdGlwbGUgbGFuZ3VhZ2VzIGNhbiBiZSBzcGVjaWZpZWQ6ICAid2l0aGluIGFuIG9m
ZmVyDQp0byBpbmRpY2F0ZSB0aGUgcHJlZmVycmVkIGxhbmd1YWdlKHMpIi4NCg0KICAoTmVnb3Rp
YXRpbmcgbXVsdGlwbGUgc2ltdWx0YW5lb3VzIGxhbmd1YWdlcyB3aXRoaW4gYSBtZWRpYSBzdHJl
YW0NCmlzDQogIG91dCBvZiBzY29wZSwgYXMgdGhlIGNvbXBsZXhpdHkgb2YgZG9pbmcgc28gb3V0
d2VpZ2hzIHRoZQ0KICB1c2VmdWxuZXNzLikNCg0KWW91IG1pZ2h0IHdhbnQgdG8gc2F5IGluc3Rl
YWQgIihOZWdvdGlhdGluZyBtdWx0aXBsZSBzaW11bHRhbmVvdXMNCmxhbmd1YWdlcyB3aXRoaW4g
YSBtZWRpYSBzdHJlYW0gaXMgb3V0IG9mIHNjb3BlIGZvciB0aGlzIGRvY3VtZW50LikiDQp0byBl
bnN1cmUgdGhhdCBub2JvZHkgZGVjaWRlcyB0byBhcmd1ZSB3aGV0aGVyICJ0aGUgY29tcGxleGl0
eSBvZg0KZG9pbmcgc28gb3V0d2VpZ2hzIHRoZSB1c2VmdWxuZXNzIi4NCg0KNC4gIFRoZSBleGlz
dGluZyAnbGFuZycgYXR0cmlidXRlDQoNCiAgUkZDIDQ1NjYgW1JGQzQ1NjZdIHNwZWNpZmllcyBh
biBhdHRyaWJ1dGUgJ2xhbmcnIHdoaWNoIGFwcGVhcnMNCiAgc2ltaWxhciB0byB3aGF0IGlzIG5l
ZWRlZCBoZXJlLCBidXQgaXMgbm90IHN1ZmZpY2llbnRseSBkZXRhaWxlZA0KZm9yDQogIHVzZSBo
ZXJlLg0KDQoiZm9yIHVzZSBoZXJlIiBpc24ndCBxdWl0ZSByaWdodC4gIE1heWJlICJpcyBub3Qg
c3VmZmljaWVudGx5DQpzcGVjaWZpYw0Kb3IgZmxleGlibGUgdG8gc2F0aXNmeSB0aGUgcmVxdWly
ZW1lbnRzIi4NCg0KICBJbiBhZGRpdGlvbiwgaXQgaXMgbm90IG1lbnRpb25lZCBpbiBbUkZDMzI2
NF0NCg0KIml0IiBpcyBzb21ld2hhdCBhbWJpZ3VvdXMgaGVyZSwgcGVyaGFwcyBjaGFuZ2UgdG8g
InRoZSAnbGFuZycNCmF0dHJpYnV0ZSIuDQoNCjUuICBQcm9wb3NlZCBTb2x1dGlvbg0KDQpQZXJo
YXBzIC9Qcm9wb3NlZCBTb2x1dGlvbi9Tb2x1dGlvbi8sIHNpbmNlIG9uY2UgdGhpcyBkcmFmdCBp
cw0KYXBwcm92ZWQsIGl0IGJlY29tZXMgdGhlIHNvbHV0aW9uLg0KDQo1LjIuICBOZXcgJ2h1bWlu
dGxhbmctc2VuZCcgYW5kICdodW1pbnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXMNCg0KICAgICBhPWh1
bWludGxhbmctc2VuZDo8bGFuZ3VhZ2UgdGFnPg0KICAgICBhPWh1bWludGxhbmctcmVjdjo8bGFu
Z3VhZ2UgdGFnPg0KDQpUaGlzIGlzIHByZXNlbnRlZCBhcyB0aGUgZ2VuZXJpYyBmb3JtIG9mIHRo
ZSBhdHRyaWJ1dGVzLCBidXQgdGhlcmUgaXMNCm5vIGluZGljYXRpb24gb2YgdGhlIHBvc2libGUg
YXN0ZXJpc2suDQoNCiAgVGhlIHZhbHVlcyBjb25zdGl0dXRlIGEgbGlzdCBvZiBsYW5ndWFnZXMN
CiAgaW4gcHJlZmVyZW5jZSBvcmRlciAoZmlyc3QgaXMgbW9zdCBwcmVmZXJyZWQpLg0KDQoiVGhl
IHZhbHVlcyIgaXNuJ3QgdmVyeSBjbGVhciwgYmVjYXVzZSB0aGUgdmFsdWVzIGFyZSBpbiBzdWNj
ZXNzaXZlDQphdHRyaWJ1dGVzLiAgWW91IHdhbnQgdG8gc2F5IHNvbWV0aGluZyBsaWtlICJUaGUg
c2VxdWVuY2Ugb2YgdmFsdWVzDQppbg0KdGhlIG9jY3VycmVuY2VzIG9mIG9uZSBvZiB0aGVzZSBh
dHRyaWJ1dGVzIGNvbnN0aXR1dGVzIC4uLiIuDQpIb3dldmVyLA0Kc2VlIHRoZSB0ZWNobmljYWwg
Y29tbWVudHMgYWJvdmUuDQoNCiAgV2hlbiBwbGFjaW5nIGFuIGVtZXJnZW5jeSBjYWxsLCBhbmQg
aW4gYW55IG90aGVyIGNhc2Ugd2hlcmUgdGhlDQogIGxhbmd1YWdlIGNhbm5vdCBiZSBhc3N1bWVk
IGZyb20gY29udGV4dCwgZWFjaCBtZWRpYSBzdHJlYW0gaW4gYW4NCiAgb2ZmZXIgcHJpbWFyaWx5
IGludGVuZGVkIGZvciBodW1hbiBsYW5ndWFnZSBjb21tdW5pY2F0aW9uIFNIT1VMRA0KICBzcGVj
aWZ5IGJvdGggKG9yIGluIHNvbWUgY2FzZXMsIG9uZSBvZikgdGhlICdodW1pbnRsYW5nLXNlbmQn
IGFuZA0KICAnaHVtaW50bGFuZy1yZWN2JyBhdHRyaWJ1dGVzLg0KDQpQcm9iYWJseSBzL2Fzc3Vt
ZWQvaW5mZXJyZWQvLg0KDQpDb3VsZCB5b3UgYmUgbW9yZSBhY2N1cmF0ZSBieQ0Kcy9vciBpbiBz
b21lIGNhc2VzL29yIGZvciB1bmlkaXJlY3Rpb25hbCBzdHJlYW1zLz8NCg0KNS4zLiAgQWR2aXNv
cnkgdnMgUmVxdWlyZWQNCg0KICBUaGUgbWVjaGFuaXNtIGZvciBpbmRpY2F0aW5nIHRoaXMgcHJl
ZmVyZW5jZSBpcyB0aGF0LCBpbiBhbiBvZmZlciwNCmlmDQogIHRoZSBsYXN0IGNoYXJhY3RlciBv
ZiBhbnkgb2YgdGhlICdodW1pbnRsYW5nLXJlY3YnIG9yICdodW1pbnRsYW5nLQ0KICBzZW5kJyB2
YWx1ZXMgaXMgYW4gYXN0ZXJpc2ssIHRoaXMgaW5kaWNhdGVzIGEgcmVxdWVzdCB0byBub3QgZmFp
bA0KdGhlDQogIGNhbGwgKHNpbWlsYXIgdG8gU0lQIEFjY2VwdC1MYW5ndWFnZSBzeW50YXgpLiAg
RWl0aGVyIHdheSwgdGhlDQpjYWxsZWQNCiAgcGFydHkgTUFZIGlnbm9yZSB0aGlzLCBlLmcuLCBm
b3IgdGhlIGVtZXJnZW5jeSBzZXJ2aWNlcyB1c2UgY2FzZSwNCmENCiAgUFNBUCB3aWxsIGxpa2Vs
eSBub3QgZmFpbCB0aGUgY2FsbC4NCg0KVGhlIGNvbnN0cnVjdGlvbiBvZiB0aGlzIHBhcmFncmFw
aCBpc24ndCBxdWl0ZSBjb21wbGV0ZS4gIEl0IHNheXMNCnRoYXQNCmlmIGFuIGFzdGVyaXNrIGlz
IHByZXNlbnQsIGEgcmVxdWVzdCBzaG91bGRuJ3QgZmFpbCwgYnV0IGl0IGRvZXNuJ3QNCnNheSB0
aGF0IGlmIG5vIGFzdGVyaXNrIGlzIHByZXNlbnQsIGEgcmVxdWVzdCBzaG91bGQgZmFpbCBpZiB0
aGVyZSBpcw0Kbm8gbGFuZ3VhZ2UgbWF0Y2guICBBbmQgaXQncyB0aGUgbGF0dGVyIGNvbmRpdGlv
biB0aGF0IG1ha2VzIHRoZQ0Kc2Vjb25kIHNlbnRlbmNlIG1lYW5pbmdmdWwuICBTbyBJIHRoaW5r
IHlvdSB3YW50IHRvIGluc2VydCBiZXR3ZWVuDQp0aGUNCnR3byBzZW50ZW5jZXMgb25lIHJlZ2Fy
ZGluZyB0aGUgYWJzZW5jZSBvZiBhbiBhc3Rlcmlzay4NCg0KNS41LiAgRXhhbXBsZXMNCg0KR2l2
ZW4gdGhhdCB0aGUgY29tYmluZWQgYXVkaW8vdmlkZW8gbWVjaGFuaXNtIGlzIHRoZSBvbmx5DQpp
cnJlZ3VsYXJpdHkNCmluIHRoaXMgc3lzdGVtLCB0aGVyZSBvdWdodCB0byBiZSBhbiBleGFtcGxl
IG9mIGl0LiAgRS5nLiwNCg0KICBBbiBleGFtcGxlIG9mIGEgc3VwcGxlbWVudGFsIHZpZGVvIHN0
cmVhbSB3aXRoIGEgc3Bva2VuIGxhbmd1YWdlDQogIGF1ZGlvIHN0cmVhbToNCg0KICAgICBtPXZp
ZGVvIDUxMzcyIFJUUC9BVlAgMzEgMzINCiAgICAgYT1odW1pbnRsYW5nLXNlbmQ6ZW4NCiAgICAg
YT1odW1pbnRsYW5nLXJlY3Y6ZW4NCg0KICAgICBtPWF1ZGlvIDQ5MjUwIFJUUC9BVlAgMjANCiAg
ICAgYT1odW1pbnRsYW5nLXNlbmQ6ZW4NCiAgICAgYT1odW1pbnRsYW5nLXJlY3Y6ZW4NCg0KNi4g
IElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgICBodW1pbnRsYW5nLXZhbHVlID0gIExhbmd1YWdl
LVRhZyBbIGFzdGVyaXNrIF0NCiAgICAgICAgICAgICAgICAgICAgICAgICA7IExhbmd1YWdlLVRh
ZyBkZWZpbmVkIGluIFJGQyA1NjQ2DQogICAgIGFzdGVyaXNrICAgICAgICAgPSAgIioiDQoNCnMv
TGFuZ3VhZ2UtVGFnIGRlZmluZWQgaW4gUkZDIDU2NDYvTGFuZ3VhZ2UtVGFnIGFzIGRlZmluZWQg
aW4gUkZDDQo1NjQ2Lw0KDQpCdXQgcGVyaGFwcyBhbHNvIHMvUkZDIDU2NDYvQkNQIDQ3Lywgd2hp
Y2ggZW5zdXJlcyB0aGF0ICJodW1pbnRsYW5nIg0KdHJhY2tzIHRoZSBjdXJyZW50IHZlcnNpb24g
b2YgbGFuZ3VhZ2UgdGFncy4NCg0KQXBwZW5kaXggQS4gIEhpc3RvcmljIEFsdGVybmF0aXZlIFBy
b3Bvc2FsOiBDYWxsZXItcHJlZnMNCg0KICBUaGlzDQogIHJlc3VsdHMgaW4gYSBtb3JlIGZyYWdp
bGUgc29sdXRpb24gc2luY2UgdGhlIG1lZGlhIG1vZGFsaXR5IGFuZA0KICBsYW5ndWFnZSB3b3Vs
ZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNpZmljDQptZWRpYQ0K
ICBmb3JtYXRzICh3aGljaCBpbmhlcmVudGx5IGluY2x1ZGUgdGhlIG1vZGFsaXR5KSB3b3VsZCBi
ZQ0KbmVnb3RpYXRlZA0KICBhdCBhIGRpZmZlcmVudCBsZXZlbCAodHlwaWNhbGx5IFNEUCwgZXNw
ZWNpYWxseSBpbiB0aGUgZW1lcmdlbmN5DQogIGNhbGxpbmcgY2FzZXMpLCBtYWtpbmcgaXQgZWFz
aWVyIHRvIGhhdmUgbWlzbWF0Y2hlcyAoc3VjaCBhcyB3aGVyZQ0KICB0aGUgbWVkaWEgbW9kYWxp
dHkgbmVnb3RpYXRlZCBpbiBTSVAgZG9uJ3QgbWF0Y2ggd2hhdCB3YXMNCm5lZ290aWF0ZWQNCiAg
dXNpbmcgU0RQKS4NCg0KInRoZSBtZWRpYSBtb2RhbGl0eSBhbmQgbGFuZ3VhZ2Ugd291bGQgYmUg
bmVnb3RpYXRlZCB1c2luZyBTSVAiIGlzbid0DQpxdWl0ZSB0aGUgcmlnaHQgd2F5IHRvIHNheSBp
dCBiZWNhdXNlIFNJUCBpc24ndCBleHBsaWNpdGx5DQpuZWdvdGlhdGluZw0KdGhlIG1vZGFsaXR5
LiAgQmV0dGVyIHdvdWxkIGJlDQoNCiAgLi4uIHRoZSBsYW5ndWFnZSAoYW5kIGJ5IGltcGxpY2F0
aW9uIHRoZSBtZWRpYSBtb2RhbGl0eSkgd291bGQgYmUNCiAgbmVnb3RpYXRlZCB1c2luZyBTSVAs
IGFuZCB0aGVuIHRoZSBzcGVjaWZpYyBtZWRpYSAod2hpY2gNCmluaGVyZW50bHkNCiAgaW5jbHVk
ZSB0aGUgbW9kYWxpdGllcyBhbmQgZm9ybWF0cykgd291bGQgYmUgbmVnb3RpYXRlZCBhdCBhDQog
IGRpZmZlcmVudCBsZXZlbCAuLi4NCg0KW0VORF0NCg0KDQoNCg0KVGhpcyBlbWFpbCBhbmQgaXRz
IGF0dGFjaG1lbnRzIGFyZSBpbnRlbmRlZCBmb3IgdGhlIGFib3ZlIG5hbWVkIG9ubHkgYW5kIG1h
eSBiZSBjb25maWRlbnRpYWwuIElmIHRoZXkgaGF2ZSBjb21lIHRvIHlvdSBpbiBlcnJvciB5b3Ug
bXVzdCB0YWtlIG5vIGFjdGlvbiBiYXNlZCBvbiB0aGVtLCBub3IgbXVzdCB5b3UgY29weSBvciBz
aG93IHRoZW0gdG8gYW55b25lOyBwbGVhc2UgcmVwbHkgdG8gdGhpcyBlbWFpbCBvciBjYWxsICs0
NCAyMDcgMzU2IDA2MDAgYW5kIGhpZ2hsaWdodCB0aGUgZXJyb3IuDQo=

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_
Content-Type: text/html; charset="utf-8"
Content-ID: <1F5EA51BAA990E4EBDCD38D9D0B94897@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgRGFsZSEgTWFueSB0aGFua3Mg
Zm9yIHRoZXNlIGNvbW1lbnRzLCBhcyBvbmUgb2YgdGhlIFNMSU0gY2hhaXJzIEnigJlsbCB3b3Jr
IG9uIGdldHRpbmcgc29tZSBhbnN3ZXJzIHRvIHlvdSBvciBJ4oCZbGwgcmVxdWVzdCB0aGUgYXV0
aG9yIG9yIG9uZSBvZiB0aGUgU0xJTSBhY3RpdmUgcGFydGljaXBhbnRzIHRvIHJlc3BvbmQuJm5i
c3A7DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5C
ZXJuYXJkLCBSYW5kYWxsIGFuZCBTTElNIC0gc2VlIGJlbG93IHJlIERhbGXigJlzIHBvaW50cy4m
bmJzcDs8YnIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj4qKioqIEEuIENhbGwgZmFpbHVyZSAqKioqPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPlJhbmRhbGwgb3IgQmVybmFyZCBjYW4geW91IHJlc3BvbmQgdG8gdGhpcz8gSSBpbWFnaW5l
IHRoZSBVQSBjYWxsIGZhaWx1cmUgbWV0aG9kIGlzIFVBIHNwZWNpZmljLCBidXQgaWYgdGhlcmUg
aXMgYSBjbGFzaCB3aXRoIFNJUCBsZXZlbCBjYWxsIGZhaWwgdGhlbiB0aGlzIHNob3VsZCBiZSBh
ZGRyZXNzZWQuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj4qKioqJm5ic3A7Qi4gQXVkaW8vVmlkZW8gY29vcmRpbmF0aW9uICoqKio8L2Rp
dj4NCjxkaXYgY2xhc3M9IiI+SSBiZWxpZXZlIHRoZSB0aGVvcnkgYmVoaW5kIHRoZSBjdXJyZW50
IGRyYWZ0IGlzIHRoYXQgdGhlIHNwb2tlbiBhbmQgdmlkZW8gc3RyZWFtcyB3aWxsIGJlIGRpZmZl
cmVudCBpbiB0aGUgY2FzZXMgb2Ygc3VjaCB0aGluZ3MgYXMgc2lnbiBsYW5ndWFnZS4gVmlkZW8g
Y291bGQgdGhlcmVmb3JlIGJlIHNpZ24gYW5kIGF1ZGlvIHdvdWxkIGJlIGEgc3Bva2VuIGxhbmd1
YWdlLiBJ4oCZbSBub3Qgc3VyZSBpZiB0aGUgc3VnZ2VzdGlvbg0KIGhlIHNhdGlzZmllcyB0aGlz
IGNhc2U/PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj4qKioqIEMuICZxdW90O2h1bWludGxhbmcmcXVvdDsgc2VlbXMgbG9uZyB0byBtZSAq
KioqPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkJlcm5hcmQgLSBJIGRvbuKAmXQgc2VlIHRoZSBpc3N1
ZSB3aXRoIHNob3J0ZW5pbmcgaHVtaW50bGFuZywgYnV0IHRoZSBncm91cCBtaWdodC4gSSBzdWdn
ZXN0IHdlIHRocm93IHRoaXMgdG8gdGhlIGdyb3VwIGZvciBkaXNjdXNzaW9uLjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+KioqKiBELiBV
c2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXggKioqKjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5S
YW5kYWxsIGFuZCBCZXJuYXJkIC0gaXMgdGhpcyBhbiBhY2NlcHRhYmxlIGNoYW5nZT8gT3Igb25l
IHdlIG5lZWQgdG8gZGlzY3VzcyBmdXJ0aGVyLiBTZWVtcyBsaWtlIGEgcmVhc29uYWJsZSByZXF1
ZXN0LCBidXQgYWxzbyBhIGxhcmdlciBjaGFuZ2UsIHdoaWNoIGlzIHdoeSBJIGFzayE8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPioqKiog
RS4gSGF2ZSBhbiBhdHRyaWJ1dGUgdG8gYWJicmV2aWF0ZSB0aGUgYmlkaXJlY3Rpb25hbGx5LXN5
bW1ldHJpYyBjYXNlICoqKio8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+SSBkbyBub3QgcmVtZW1iZXIg
dXMgaGF2aW5nIHRoaXMgZGlzY3Vzc2lvbiB3aXRoaW4gdGhlIGdyb3VwLCBhbHRob3VnaCBpdCBt
YXkgaGF2ZSBvY2N1cnJlZCBiZWZvcmUgSSBiZWNhbWUgY2hhaXIuPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPlJhbmRhbGwsIEJyaWFuIG9yIEJlcm5hcmQgLSBoYXMgdGhpcyBpZGVhIGJlZW4gZGlzY3Vz
c2VkIGJlZm9yZT8gSWYgc28sIGNhbiBvbmUgb2YgeW91IHJlc3BvbmQgd2l0aCBhbiBleHBsYW5h
dGlvbiBhcyB0byB3aHkgd2UgaGF2ZW7igJl0IGRvbmUgdGhpcz88L2Rpdj4NCjxkaXYgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qKioqJm5ic3A7RWRpdG9yaWFsIGNvbW1l
bnRzIGFuZCBuaXRzICoqKioqPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlJhbmRhbGwgLSBjYW4geW91
IHRha2UgYSBsb29rIHRocm91Z2ggRGFsZeKAmXMgZWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBzaG91
dCBpZiB0aGVyZSBpcyBhbnkgcHJvYmxlbXMgd2l0aCB0aGVzZSBzdWdnZXN0aW9uczsgaWYgZXZl
cnl0aGluZyBpcyBvayBwbGVhc2UgbWFrZSB0aGUgY2hhbmdlcy48L2Rpdj4NCjxkaXYgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlRoYW5rcyBhbGwhPC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1m
YW1pbHk6IEhlbHZldGljYTsgZm9udC1zaXplOiAxMnB4OyBmb250LXN0eWxlOiBub3JtYWw7IGZv
bnQtdmFyaWFudC1jYXBzOiBub3JtYWw7IGZvbnQtd2VpZ2h0OiBub3JtYWw7IGxldHRlci1zcGFj
aW5nOiBub3JtYWw7IG9ycGhhbnM6IGF1dG87IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVu
dDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd2lkb3dz
OiBhdXRvOyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBhdXRv
OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7Ij4NCjxiciBjbGFzcz0iIj4NCk5hdGFz
aGEgUm9vbmV5IHwgSW50ZXJuZXQgRW5naW5lZXJpbmcmbmJzcDtEaXJlY3RvciB8IEludGVybmV0
IGFuZCBXZWIgVGVhbSB8Jm5ic3A7VGVjaG5vbG9neSB8IEdTTUEgfCZuYnNwOzxhIGhyZWY9Im1h
aWx0bzpucm9vbmV5QGdzbWEuY29tIiBjbGFzcz0iIj5ucm9vbmV5QGdzbWEuY29tPC9hPiZuYnNw
O3wgJiM0Mzs0NCAoMCkgNzczMCAyMTkmbmJzcDs3NjUgfCBAdGhpc05hdGFzaGEgfCBTa3lwZTom
bmJzcDs8YSBocmVmPSJtYWlsdG86bnJvb25leUBnc20ub3JnIiBjbGFzcz0iIj5ucm9vbmV5QGdz
bS5vcmc8L2E+PC9kaXY+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90
ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gMTggRmViIDIwMTcsIGF0
IDAyOjMyLCBEYWxlIFdvcmxleSAmbHQ7PGEgaHJlZj0ibWFpbHRvOndvcmxleUBhcmlhZG5lLmNv
bSIgY2xhc3M9IiI+d29ybGV5QGFyaWFkbmUuY29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIg
Y2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYg
Y2xhc3M9IiI+UmV2aWV3ZXI6IERhbGUgV29ybGV5PGJyIGNsYXNzPSIiPg0KUmV2aWV3IHJlc3Vs
dDogUmVhZHkgd2l0aCBOaXRzPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KSSBhbSB0aGUg
YXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gJm5ic3A7VGhlIEdlbmVy
YWwgQXJlYTxiciBjbGFzcz0iIj4NClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJ
RVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQ8YnIgY2xhc3M9IiI+DQpieSB0aGUgSUVTRyBm
b3IgdGhlIElFVEYgQ2hhaXIuICZuYnNwO1BsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0
PGJyIGNsYXNzPSIiPg0KbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLjxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQ8YnIgY2xhc3M9IiI+DQombHQ7PGEgaHJlZj0iaHR0cDovL3dpa2kudG9vbHMuaWV0
Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcSIgY2xhc3M9IiI+aHR0cDovL3dpa2ku
dG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcTwvYT4mZ3Q7LjxiciBj
bGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkRvY3VtZW50OiAmbmJzcDtkcmFmdC1pZXRmLXNsaW0t
bmVnb3RpYXRpbmctaHVtYW4tbGFuZ3VhZ2UtMDY8YnIgY2xhc3M9IiI+DQpSZXZpZXdlcjogJm5i
c3A7RGFsZSBSLiBXb3JsZXk8YnIgY2xhc3M9IiI+DQpSZXZpZXcgRGF0ZTogJm5ic3A7MjAxNy0w
Mi0xNzxiciBjbGFzcz0iIj4NCklFVEYgTEMgRW5kIERhdGU6ICZuYnNwOzIwMTctMDItMjA8YnIg
Y2xhc3M9IiI+DQpJRVNHIFRlbGVjaGF0IGRhdGU6ICZuYnNwO1t1bmtub3duXTxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NClN1bW1hcnk6PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhpcyBkcmFmdCBpcyBiYXNpY2FsbHkgcmVhZHkgZm9yIHB1
YmxpY2F0aW9uLCBidXQgaGFzIG5pdHM8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDt0aGF0IHNob3VsZCBiZSBmaXhlZCBiZWZvcmUgcHVibGljYXRpb24u
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KKiBUZWNobmljYWwgY29tbWVudHM8YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpBLiBDYWxsIGZhaWx1cmU8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpJZiBhIGNhbGwgZmFpbHMgZHVlIHRvIG5vIGF2YWlsYWJsZSBsYW5ndWFnZSBt
YXRjaCwgaW4gd2hhdCB3YXkocyk8YnIgY2xhc3M9IiI+DQpkb2VzIGl0IGZhaWw/ICZuYnNwO1Nl
Y3Rpb24gNS4zIHNheXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtJ
ZiBzdWNoIGFuIG9mZmVyIGlzIHJlY2VpdmVkLCB0aGUgcmVjZWl2ZXIgTUFZPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7cmVqZWN0IHRoZSBtZWRpYSwgaWdub3JlIHRoZSBsYW5ndWFnZSBzcGVj
aWZpZWQsIG9yIGF0dGVtcHQgdG88YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtpbnRlcnByZXQg
dGhlIGludGVudDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkJ1dCBJIHN1c3BlY3QgaXQn
cyBhbHNvIGFsbG93ZWQgZm9yIHRoZSBVQVMgdG8gZmFpbCB0aGUgY2FsbCBhdCB0aGU8YnIgY2xh
c3M9IiI+DQpTSVAgbGV2ZWwuICZuYnNwO1doZXRoZXIgb3Igbm90IHRoYXQgaXMgYWxsb3dlZCAo
b3IgYXQgbGVhc3QgZW52aXNpb25lZCk8YnIgY2xhc3M9IiI+DQpzaG91bGQgYmUgZGVzY3JpYmVk
LiAmbmJzcDtBbmQgd2hhdCByZXNwb25zZSBjb2RlKHMpL3dhcm4tY29kZShzKSBzaG91bGQ8YnIg
Y2xhc3M9IiI+DQpiZTxiciBjbGFzcz0iIj4NCnVzZWQgZm9yIHRoYXQ/PGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KQi4gQXVkaW8vVmlkZW8gY29vcmRpbmF0aW9uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7NS4yLiAmbmJzcDtOZXcgJ2h1bWludGxhbmctc2Vu
ZCcgYW5kICdodW1pbnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQombmJzcDsmbmJzcDtOb3RlIHRoYXQgd2hpbGUgc2lnbmVkIGxhbmd1YWdlIHRhZ3Mg
YXJlIHVzZWQgd2l0aCBhIHZpZGVvIHN0cmVhbTxiciBjbGFzcz0iIj4NCnRvPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7aW5kaWNhdGUgc2lnbiBsYW5ndWFnZSwgYSBzcG9rZW4gbGFuZ3VhZ2Ug
dGFnIGZvciBhIHZpZGVvIHN0cmVhbTxiciBjbGFzcz0iIj4NCmluPGJyIGNsYXNzPSIiPg0KJm5i
c3A7Jm5ic3A7cGFyYWxsZWwgd2l0aCBhbiBhdWRpbyBzdHJlYW0gd2l0aCB0aGUgc2FtZSBzcG9r
ZW4gbGFuZ3VhZ2UgdGFnPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7aW5kaWNhdGVzIGEgcmVx
dWVzdCBmb3IgYSBzdXBwbGVtZW50YWwgdmlkZW8gc3RyZWFtIHRvIHNlZSB0aGU8YnIgY2xhc3M9
IiI+DQombmJzcDsmbmJzcDtzcGVha2VyLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkFu
ZCB0aGVyZSdzIGEgc2ltaWxhciBwYXJhZ3JhcGggaW4gNS40OjxiciBjbGFzcz0iIj4NCjxiciBj
bGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPiZuYnNwOyZuYnNwO0Eg
c3Bva2VuIGxhbmd1YWdlIHRhZyBmb3IgYSB2aWRlbyBzdHJlYW0gaW4gY29uanVuY3Rpb24gd2l0
aCBhbjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCmF1ZGlvPGJyIGNsYXNzPSIiPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+Jm5ic3A7Jm5ic3A7c3RyZWFtIHdpdGggdGhl
IHNhbWUgbGFuZ3VhZ2UgbWlnaHQgaW5kaWNhdGUgYSByZXF1ZXN0IGZvcjxiciBjbGFzcz0iIj4N
CiZuYnNwOyZuYnNwO3N1cHBsZW1lbnRhbCB2aWRlbyB0byBzZWUgdGhlIHNwZWFrZXIuPGJyIGNs
YXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPGJyIGNsYXNzPSIiPg0KSSB0aGluayB0aGlzIG1lY2hh
bmlzbSBuZWVkcyB0byBiZSBkZXNjcmliZWQgbW9yZSBleGFjdGx5LCBhbmQgaW48YnIgY2xhc3M9
IiI+DQpwYXJ0aWN1bGFyLCBpdCBzaG91bGQgbm90IGRlcGVuZCBvbiB0aGUgVUEgdW5kZXJzdGFu
ZGluZyB3aGljaDxiciBjbGFzcz0iIj4NCmxhbmd1YWdlIHRhZ3MgYXJlIHNwb2tlbiBsYW5ndWFn
ZSB0YWdzLiAmbmJzcDtJdCBzZWVtcyB0byBtZSB0aGF0IGE8YnIgY2xhc3M9IiI+DQp3b3JrYWJs
ZSBydWxlIGlzIHRoYXQgdGhlcmUgaXMgYW4gYXVkaW8gc3RyZWFtIGFuZCBhIHZpZGVvIHN0cmVh
bSBhbmQ8YnIgY2xhc3M9IiI+DQp0aGV5IHNwZWNpZnkgZXhhY3RseSB0aGUgc2FtZSBsYW5ndWFn
ZSB0YWcgaW4gdGhlaXIgcmVzcGVjdGl2ZTxiciBjbGFzcz0iIj4NCmh1bWludGxhbmcgYXR0cmli
dXRlcy4gJm5ic3A7SW4gdGhhdCBjYXNlLCBpdCBpcyBhIHJlcXVlc3QgZm9yIGEgc3Bva2VuPGJy
IGNsYXNzPSIiPg0KbGFuZ3VhZ2Ugd2l0aCBzaW11bHRhbmVvdXMgdmlkZW8gb2YgdGhlIHNwZWFr
ZXIsIGFuZCB0aG9zZSByZXF1ZXN0czxiciBjbGFzcz0iIj4NCnNob3VsZCBiZSBjb25zaWRlcmVk
IHNhdGlzZmllZCBvbmx5IGlmIGJvdGggc3RyZWFtcyBjYW4gYmU8YnIgY2xhc3M9IiI+DQplc3Rh
Ymxpc2hlZC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQoqIFRoZSBmb2xsb3dpbmcgdGhy
ZWUgaXRlbXMgYXJlIGFkanVzdG1lbnRzIHRvIHRoZSBkZXNpZ24gd2hpY2ggSSdkPGJyIGNsYXNz
PSIiPg0KbGlrZSB0byBrbm93IGhhdmUgYmVlbiBjb25zaWRlcmVkLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCkMuICZxdW90O2h1bWludGxhbmcmcXVvdDsgc2VlbXMgbG9uZyB0byBtZTxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkdpdmVuIHRoZSBleGNlc3NpdmUgbGVuZ3RoIG9m
IFNEUCBpbiBwcmFjdGljZSwgaXQgc2VlbXMgdG8gbWUgdGhhdCBhPGJyIGNsYXNzPSIiPg0Kc2hv
cnRlciBhdHRyaWJ1dGUgbmFtZSB3b3VsZCBiZSBkZXNpcmFibGUuICZuYnNwO0UuZy4sICZxdW90
O2h1bWxhbmcmcXVvdDsgYXMgd2FzPGJyIGNsYXNzPSIiPg0KdXNlZCBpbiBzb21lIHByZXZpb3Vz
IHZlcnNpb25zLiAmbmJzcDtPciBpcyB0aGVyZSBhIGNvb3JkaW5hdGVkIHVzYWdlIHdpdGg8YnIg
Y2xhc3M9IiI+DQpvdGhlciBuYW1lcyBpbiB0aGUgJnF1b3Q7aHVtKmxhbmcmcXVvdDsgcGF0dGVy
bj88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpELiBVc2UgdGhlIEFjY2VwdC1MYW5ndWFn
ZSBzeW50YXg8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJdCBzZWVtcyB0byBtZSB0aGF0
IGl0IHdvdWxkIGJldHRlciB0byB1c2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXg8YnIgY2xh
c3M9IiI+DQpmb3IgdGhlIGF0dHJpYnV0ZSB2YWx1ZXMuICZuYnNwO1RoaXMgYWxsb3dzICgxKSBz
cGVjaWZpeWluZyB0aGUgcXVhbGl0eSBvZjxiciBjbGFzcz0iIj4NCmxhbmd1YWdlIGV4cGVyaWVu
Y2UsIGFsbG93aW5nIGNsZWFyIGRlc2NyaXB0aW9uIG9mIGJpbGluZ3VhbGlzbSwgKDIpPGJyIGNs
YXNzPSIiPg0KYTxiciBjbGFzcz0iIj4NCnVuaWZpZWQgbWV0aG9kIG9mIHNwZWNpZnlpbmcgd2hl
dGhlciBvciBub3QgYXJiaXRyYXJ5IGxhbmd1YWdlcyBhcmU8YnIgY2xhc3M9IiI+DQphY2NlcHRh
YmxlLCBhbmQgKDMpIGFiYnJldmlhdGluZyBTRFAgZGVzY3JpcHRpb25zLjxiciBjbGFzcz0iIj4N
CjxiciBjbGFzcz0iIj4NCkluIGEgd2F5LCB0aGUgZmFjdCB0aGF0IHRoZSBjdXJyZW50IHByb3Bv
c2FsIHNlZW1zIHRvIHJlcXVpcmUgKGJ1dDxiciBjbGFzcz0iIj4NCmRvZXMgbm90IGRpcmVjdGx5
IHNwZWNpZnkpIHRoZSBjb29yZGluYXRlZCBhYnNlbmNlL3ByZXNlbmNlIG9mIGFuPGJyIGNsYXNz
PSIiPg0KYXN0ZXJpc2sgb24gYWxsIG9mIHRoZSByZXBldGl0aW9ucyBvZiBodW1pbnRsYW5nLXNl
bmQgb3I8YnIgY2xhc3M9IiI+DQpodW1pbnRsYW5nLXJlY3YgaXMgYSB3YXJuaW5nIHRoYXQgdGhl
IHN5bnRheCBkb2Vzbid0IHJlcHJlc2VudCB0aGU8YnIgY2xhc3M9IiI+DQpzZW1hbnRpY3MgYXMg
d2VsbCBhcyBpdCBtaWdodC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpFLiBIYXZlIGFu
IGF0dHJpYnV0ZSB0byBhYmJyZXZpYXRlIHRoZSBiaWRpcmVjdGlvbmFsbHktc3ltbWV0cmljIGNh
c2U8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpOb3RlIHRoYXQgYWxsIGV4YW1wbGVzIGFy
ZSBiaWRpcmVjdGlvbmFsbHkgc3ltbWV0cmljLCBhbmQgdGhlIHRleHQ8YnIgY2xhc3M9IiI+DQpz
YXlzIHRoYXQgcmVxdWVzdHMgYW5kIHJlc3BvbnNlcyBTSE9VTEQgYmUgYmlkaXJlY3Rpb25hbGx5
IHN5bW1ldHJpYy48YnIgY2xhc3M9IiI+DQpTbyBpdCB3b3VsZCBiZSBhIHZlcnkgdXNlZnVsIGFi
YnJldmlhdGlvbiB0byBkZWZpbmU8YnIgY2xhc3M9IiI+DQomcXVvdDtodW1pbnRsYW5nPSZsdDt2
YWx1ZSZndDsmcXVvdDsgdG8gYmUgZXF1aXZhbGVudCB0byB0aGUgY29tYmluYXRpb24gb2Y8YnIg
Y2xhc3M9IiI+DQomcXVvdDtodW1pbnRsYW5nLXNlbmQ9Jmx0O3ZhbHVlJmd0OyZxdW90OyBhbmQg
JnF1b3Q7aHVtaW50bGFuZy1yZWN2PSZsdDt2YWx1ZSZndDsmcXVvdDsuPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KQ29tYmluaW5nIHByb3Bvc2FscyBDLCBELCBhbmQgRSwgdGhlIGV4YW1w
bGVzIGJlY29tZTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwO209YXVkaW8gNDkxNzAgUlRQL0FWUCAwPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmVuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT12aWRlbyA1MTM3MiBSVFAv
QVZQIDMxIDMyPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1o
dW1sYW5nOmFzZSwqO3E9MC4xPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT1hdWRpbyA0OTI1MCBSVFAvQVZQIDIwPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmVzLGV1O3E9MC45LGVu
O3E9MC44LCo7cT0wLjE8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDttPXRleHQgNDUwMjAgUlRQL0FWUCAxMDMgMTA0PGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmdyPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0Kd2hpY2ggcmVxdWlyZXMgYWJvdXQgaGFsZiBhcyBtYW55IGNoYXJh
Y3RlcnMgYXMgdGhleSBoYXZlIG5vdy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQoqIEVk
aXRvcmlhbCBjb21tZW50cyBhbmQgbml0czxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkFi
c3RyYWN0PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7VGhpcyBkb2N1
bWVudCBkZXNjcmliZXMgdGhlIG5lZWQgYW5kIGEgc29sdXRpb24gdXNpbmcgbmV3IFNEUDxiciBj
bGFzcz0iIj4NCnN0cmVhbTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2F0dHJpYnV0ZXMuPGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KSSBkb24ndCB0aGluayB0aGUgdGVybSAmcXVvdDtz
dHJlYW0gYXR0cmlidXRlJnF1b3Q7IGlzIHVzZWQgaW4gUkZDIDQ1NjYuPGJyIGNsYXNzPSIiPg0K
SW5zdGVhZCwgaXQgdXNlcyAmcXVvdDttZWRpYSBhdHRyaWJ1dGUmcXVvdDsuPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KMS4gJm5ic3A7SW50cm9kdWN0aW9uPGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbGVyIGFuZCBjYWxsZWUga25vdyBlYWNoIG90aGVy
IG9yIHRoZXJlIGlzIGNvbnRleHR1YWwgb3Igb3V0IG9mPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7YmFuZCBpbmZvcm1hdGlvbiBmcm9tIHdoaWNoIHRoZSBsYW5ndWFnZShzKSBhbmQgbWVkaWEg
bW9kYWxpdGllczxiciBjbGFzcz0iIj4NCmNhbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CkkgdGhpbmsgdGhpcyBjb250ZXh0LCBpdCdzIHByZWZlcnJlZCB0byBoeXBoZW5hdGUgJnF1b3Q7
b3V0LW9mLWJhbmQmcXVvdDsgdG88YnIgY2xhc3M9IiI+DQptYWtlIGl0IGNsZWFybHkgYmUgYW4g
YWRqZWN0aXZlLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoaXMg
YXBwcm9hY2ggaGFzIGEgbnVtYmVyIG9mIGJlbmVmaXRzLCBpbmNsdWRpbmcgdGhhdCBpdCBpczxi
ciBjbGFzcz0iIj4NCmdlbmVyaWM8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsoYXBwbGllcyB0
byBhbGwgaW50ZXJhY3RpdmUgY29tbXVuaWNhdGlvbnMgbmVnb3RpYXRlZCB1c2luZyBTRFApPGJy
IGNsYXNzPSIiPg0KYW5kPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7bm90IGxpbWl0ZWQgdG8g
ZW1lcmdlbmN5IGNhbGxzLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkkgdGhpbmsgcy9h
bmQgbm90IGxpbWl0ZWQgdG8vYW5kIGlzIG5vdCBsaW1pdGVkIHRvLyByZWFkcyBtb3JlPGJyIGNs
YXNzPSIiPg0Kc21vb3RobHkuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7QnV0IGl0IGlzIGNsZWFybHkgdXNlZnVsIGluIG1hbnkgb3RoZXIgY2FzZXMuICZuYnNwO0Zv
cjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2V4YW1wbGUsIHNvbWVvbmUgY2FsbGluZyBhIGNv
bXBhbnkgY2FsbCBjZW50ZXIgb3IgYSBQdWJsaWMgU2FmZXR5PGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7QW5zd2VyaW5nIFBvaW50IChQU0FQKSBzaG91bGQgYmUgYWJsZSB0byBpbmRpY2F0ZSBp
ZiBvbmUgb3IgbW9yZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3NwZWNpZmljIHNpZ25lZCwg
d3JpdHRlbiwgYW5kL29yIHNwb2tlbiBsYW5ndWFnZXMgYXJlIHByZWZlcnJlZCw8YnIgY2xhc3M9
IiI+DQp0aGU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtjYWxsZWUgc2hvdWxkIGJlIGFibGUg
dG8gaW5kaWNhdGUgaXRzIGNhcGFiaWxpdGllcyBpbiB0aGlzIGFyZWEsPGJyIGNsYXNzPSIiPg0K
YW5kPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7dGhlIGNhbGwgcHJvY2VlZCB1c2luZyBpbi1j
b21tb24gbGFuZ3VhZ2UocykgYW5kIG1lZGlhIGZvcm1zLjxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCkkgdGhpbmsgcy9wcmVmZXJyZWQsIHRoZSBjYWxsZWUvcHJlZmVycmVkOyB0aGUgY2Fs
bGVlLyBiZWNhdXNlIHRoZTxiciBjbGFzcz0iIj4NCnNlbnRlbmNlIGlzIHRoZSBjb25jYXRlbmF0
aW9uIG9mIHR3byBzZW50ZW5jZXMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KUGVyaGFw
cyBzL2luLWNvbW1vbi9zaGFyZWQvLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNw
OyZuYnNwO0luY2x1ZGluZyB0aGUgdXNlcidzIGh1bWFuIChuYXR1cmFsKSBsYW5ndWFnZSBwcmVm
ZXJlbmNlcyBpbiB0aGU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtzZXNzaW9uIGVzdGFibGlz
aG1lbnQgbmVnb3RpYXRpb24gaXMgaW5kZXBlbmRlbnQgb2YgdGhlIHVzZSBvZiBhPGJyIGNsYXNz
PSIiPg0KJm5ic3A7Jm5ic3A7cmVsYXkgc2VydmljZSBhbmQgaXMgdHJhbnNwYXJlbnQgdG8gYSB2
b2ljZSBzZXJ2aWNlIHByb3ZpZGVyLiA8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJIHRo
aW5rIGl0J3MgZXZlbiBicm9hZGVyIHRoYW4gJnF1b3Q7dHJhbnNwYXJlbnQgdG8gYSB2b2ljZSBz
ZXJ2aWNlPGJyIGNsYXNzPSIiPg0KcHJvdmlkZXImcXVvdDsgLS0gaXQncyB0cmFuc3BhcmVudCB0
byBhbnkgc2VyaXZpY2UgcHJvdmlkZXIsIGFzc3VtaW5nIHRoYXQ8YnIgY2xhc3M9IiI+DQp0aGUg
bWVkaWEgYXJlIGxhbmd1YWdlLW5ldXRyYWwuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7SW4gdGhlIGNhc2Ugb2YgYSBjYWxsIHRvIGUuZy4sIGFuIGFpcmxpbmUsIHRo
ZSBjYWxsIGNvdWxkIGJlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7YXV0b21hdGljYWxseSBo
YW5kbGVkIGJ5IGEgU3BhbmlzaC1zcGVha2luZyBhZ2VudC48YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQpJIHRoaW5rIHMvaGFuZGxlZCBieS9yb3V0ZWQgdG8vIGlzIHRoZSB1c3VhbCB1c2Fn
ZS48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQozLiAmbmJzcDtEZXNpcmVkIFNlbWFudGlj
czxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoZSBkZXNpcmVkIHNv
bHV0aW9uIGlzIGEgbWVkaWEgYXR0cmlidXRlIChwcmVmZXJhYmx5IHBlcjxiciBjbGFzcz0iIj4N
CmRpcmVjdGlvbik8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDt0aGF0IG1heSBiZSB1c2VkIHdp
dGhpbiBhbiBvZmZlciB0byBpbmRpY2F0ZSB0aGUgcHJlZmVycmVkPGJyIGNsYXNzPSIiPg0KbGFu
Z3VhZ2U8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtvZiBlYWNoIChkaXJlY3Rpb24gb2YgYSkg
bWVkaWEgc3RyZWFtLCBhbmQgd2l0aGluIGFuIGFuc3dlciB0bzxiciBjbGFzcz0iIj4NCiZuYnNw
OyZuYnNwO2luZGljYXRlIHRoZSBhY2NlcHRlZCBsYW5ndWFnZS48YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpJbiB0aGlzIG9uZSBpbnN0YW5jZSwgSSB0aGluayB5b3Ugd2FudCB0byB1c2Ug
JnF1b3Q7bGFuZ3VhZ2UocykmcXVvdDsgdG8gZHJpdmU8YnIgY2xhc3M9IiI+DQpob21lIHRoYXQg
dGhhdCBtdWx0aXBsZSBsYW5ndWFnZXMgY2FuIGJlIHNwZWNpZmllZDogJm5ic3A7JnF1b3Q7d2l0
aGluIGFuIG9mZmVyPGJyIGNsYXNzPSIiPg0KdG8gaW5kaWNhdGUgdGhlIHByZWZlcnJlZCBsYW5n
dWFnZShzKSZxdW90Oy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDso
TmVnb3RpYXRpbmcgbXVsdGlwbGUgc2ltdWx0YW5lb3VzIGxhbmd1YWdlcyB3aXRoaW4gYSBtZWRp
YSBzdHJlYW08YnIgY2xhc3M9IiI+DQppczxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO291dCBv
ZiBzY29wZSwgYXMgdGhlIGNvbXBsZXhpdHkgb2YgZG9pbmcgc28gb3V0d2VpZ2hzIHRoZTxiciBj
bGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzZWZ1bG5lc3MuKTxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCllvdSBtaWdodCB3YW50IHRvIHNheSBpbnN0ZWFkICZxdW90OyhOZWdvdGlhdGluZyBt
dWx0aXBsZSBzaW11bHRhbmVvdXM8YnIgY2xhc3M9IiI+DQpsYW5ndWFnZXMgd2l0aGluIGEgbWVk
aWEgc3RyZWFtIGlzIG91dCBvZiBzY29wZSBmb3IgdGhpcyBkb2N1bWVudC4pJnF1b3Q7PGJyIGNs
YXNzPSIiPg0KdG8gZW5zdXJlIHRoYXQgbm9ib2R5IGRlY2lkZXMgdG8gYXJndWUgd2hldGhlciAm
cXVvdDt0aGUgY29tcGxleGl0eSBvZjxiciBjbGFzcz0iIj4NCmRvaW5nIHNvIG91dHdlaWdocyB0
aGUgdXNlZnVsbmVzcyZxdW90Oy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo0LiAmbmJz
cDtUaGUgZXhpc3RpbmcgJ2xhbmcnIGF0dHJpYnV0ZTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCiZuYnNwOyZuYnNwO1JGQyA0NTY2IFtSRkM0NTY2XSBzcGVjaWZpZXMgYW4gYXR0cmlidXRl
ICdsYW5nJyB3aGljaCBhcHBlYXJzPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7c2ltaWxhciB0
byB3aGF0IGlzIG5lZWRlZCBoZXJlLCBidXQgaXMgbm90IHN1ZmZpY2llbnRseSBkZXRhaWxlZDxi
ciBjbGFzcz0iIj4NCmZvcjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzZSBoZXJlLjxiciBj
bGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZxdW90O2ZvciB1c2UgaGVyZSZxdW90OyBpc24ndCBx
dWl0ZSByaWdodC4gJm5ic3A7TWF5YmUgJnF1b3Q7aXMgbm90IHN1ZmZpY2llbnRseTxiciBjbGFz
cz0iIj4NCnNwZWNpZmljPGJyIGNsYXNzPSIiPg0Kb3IgZmxleGlibGUgdG8gc2F0aXNmeSB0aGUg
cmVxdWlyZW1lbnRzJnF1b3Q7LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZu
YnNwO0luIGFkZGl0aW9uLCBpdCBpcyBub3QgbWVudGlvbmVkIGluIFtSRkMzMjY0XTxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCiZxdW90O2l0JnF1b3Q7IGlzIHNvbWV3aGF0IGFtYmlndW91
cyBoZXJlLCBwZXJoYXBzIGNoYW5nZSB0byAmcXVvdDt0aGUgJ2xhbmcnPGJyIGNsYXNzPSIiPg0K
YXR0cmlidXRlJnF1b3Q7LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjUuICZuYnNwO1By
b3Bvc2VkIFNvbHV0aW9uPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KUGVyaGFwcyAvUHJv
cG9zZWQgU29sdXRpb24vU29sdXRpb24vLCBzaW5jZSBvbmNlIHRoaXMgZHJhZnQgaXM8YnIgY2xh
c3M9IiI+DQphcHByb3ZlZCwgaXQgYmVjb21lcyB0aGUgc29sdXRpb24uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KNS4yLiAmbmJzcDtOZXcgJ2h1bWludGxhbmctc2VuZCcgYW5kICdodW1p
bnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDthPWh1bWludGxhbmctc2VuZDombHQ7bGFuZ3VhZ2Ug
dGFnJmd0OzxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2E9aHVt
aW50bGFuZy1yZWN2OiZsdDtsYW5ndWFnZSB0YWcmZ3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KVGhpcyBpcyBwcmVzZW50ZWQgYXMgdGhlIGdlbmVyaWMgZm9ybSBvZiB0aGUgYXR0cmli
dXRlcywgYnV0IHRoZXJlIGlzPGJyIGNsYXNzPSIiPg0Kbm8gaW5kaWNhdGlvbiBvZiB0aGUgcG9z
aWJsZSBhc3Rlcmlzay48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtU
aGUgdmFsdWVzIGNvbnN0aXR1dGUgYSBsaXN0IG9mIGxhbmd1YWdlczxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwO2luIHByZWZlcmVuY2Ugb3JkZXIgKGZpcnN0IGlzIG1vc3QgcHJlZmVycmVkKS48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQomcXVvdDtUaGUgdmFsdWVzJnF1b3Q7IGlzbid0
IHZlcnkgY2xlYXIsIGJlY2F1c2UgdGhlIHZhbHVlcyBhcmUgaW4gc3VjY2Vzc2l2ZTxiciBjbGFz
cz0iIj4NCmF0dHJpYnV0ZXMuICZuYnNwO1lvdSB3YW50IHRvIHNheSBzb21ldGhpbmcgbGlrZSAm
cXVvdDtUaGUgc2VxdWVuY2Ugb2YgdmFsdWVzPGJyIGNsYXNzPSIiPg0KaW48YnIgY2xhc3M9IiI+
DQp0aGUgb2NjdXJyZW5jZXMgb2Ygb25lIG9mIHRoZXNlIGF0dHJpYnV0ZXMgY29uc3RpdHV0ZXMg
Li4uJnF1b3Q7LiA8YnIgY2xhc3M9IiI+DQpIb3dldmVyLDxiciBjbGFzcz0iIj4NCnNlZSB0aGUg
dGVjaG5pY2FsIGNvbW1lbnRzIGFib3ZlLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwO1doZW4gcGxhY2luZyBhbiBlbWVyZ2VuY3kgY2FsbCwgYW5kIGluIGFueSBvdGhl
ciBjYXNlIHdoZXJlIHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2xhbmd1YWdlIGNhbm5v
dCBiZSBhc3N1bWVkIGZyb20gY29udGV4dCwgZWFjaCBtZWRpYSBzdHJlYW0gaW4gYW48YnIgY2xh
c3M9IiI+DQombmJzcDsmbmJzcDtvZmZlciBwcmltYXJpbHkgaW50ZW5kZWQgZm9yIGh1bWFuIGxh
bmd1YWdlIGNvbW11bmljYXRpb24gU0hPVUxEPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7c3Bl
Y2lmeSBib3RoIChvciBpbiBzb21lIGNhc2VzLCBvbmUgb2YpIHRoZSAnaHVtaW50bGFuZy1zZW5k
JyBhbmQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsnaHVtaW50bGFuZy1yZWN2JyBhdHRyaWJ1
dGVzLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClByb2JhYmx5IHMvYXNzdW1lZC9pbmZl
cnJlZC8uPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KQ291bGQgeW91IGJlIG1vcmUgYWNj
dXJhdGUgYnk8YnIgY2xhc3M9IiI+DQpzL29yIGluIHNvbWUgY2FzZXMvb3IgZm9yIHVuaWRpcmVj
dGlvbmFsIHN0cmVhbXMvPzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjUuMy4gJm5ic3A7
QWR2aXNvcnkgdnMgUmVxdWlyZWQ8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsm
bmJzcDtUaGUgbWVjaGFuaXNtIGZvciBpbmRpY2F0aW5nIHRoaXMgcHJlZmVyZW5jZSBpcyB0aGF0
LCBpbiBhbiBvZmZlciw8YnIgY2xhc3M9IiI+DQppZjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNw
O3RoZSBsYXN0IGNoYXJhY3RlciBvZiBhbnkgb2YgdGhlICdodW1pbnRsYW5nLXJlY3YnIG9yICdo
dW1pbnRsYW5nLTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3NlbmQnIHZhbHVlcyBpcyBhbiBh
c3RlcmlzaywgdGhpcyBpbmRpY2F0ZXMgYSByZXF1ZXN0IHRvIG5vdCBmYWlsPGJyIGNsYXNzPSIi
Pg0KdGhlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbCAoc2ltaWxhciB0byBTSVAgQWNj
ZXB0LUxhbmd1YWdlIHN5bnRheCkuICZuYnNwO0VpdGhlciB3YXksIHRoZTxiciBjbGFzcz0iIj4N
CmNhbGxlZDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3BhcnR5IE1BWSBpZ25vcmUgdGhpcywg
ZS5nLiwgZm9yIHRoZSBlbWVyZ2VuY3kgc2VydmljZXMgdXNlIGNhc2UsPGJyIGNsYXNzPSIiPg0K
YTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1BTQVAgd2lsbCBsaWtlbHkgbm90IGZhaWwgdGhl
IGNhbGwuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KVGhlIGNvbnN0cnVjdGlvbiBvZiB0
aGlzIHBhcmFncmFwaCBpc24ndCBxdWl0ZSBjb21wbGV0ZS4gJm5ic3A7SXQgc2F5czxiciBjbGFz
cz0iIj4NCnRoYXQ8YnIgY2xhc3M9IiI+DQppZiBhbiBhc3RlcmlzayBpcyBwcmVzZW50LCBhIHJl
cXVlc3Qgc2hvdWxkbid0IGZhaWwsIGJ1dCBpdCBkb2Vzbid0PGJyIGNsYXNzPSIiPg0Kc2F5IHRo
YXQgaWYgbm8gYXN0ZXJpc2sgaXMgcHJlc2VudCwgYSByZXF1ZXN0IHNob3VsZCBmYWlsIGlmIHRo
ZXJlIGlzPGJyIGNsYXNzPSIiPg0Kbm8gbGFuZ3VhZ2UgbWF0Y2guICZuYnNwO0FuZCBpdCdzIHRo
ZSBsYXR0ZXIgY29uZGl0aW9uIHRoYXQgbWFrZXMgdGhlPGJyIGNsYXNzPSIiPg0Kc2Vjb25kIHNl
bnRlbmNlIG1lYW5pbmdmdWwuICZuYnNwO1NvIEkgdGhpbmsgeW91IHdhbnQgdG8gaW5zZXJ0IGJl
dHdlZW48YnIgY2xhc3M9IiI+DQp0aGU8YnIgY2xhc3M9IiI+DQp0d28gc2VudGVuY2VzIG9uZSBy
ZWdhcmRpbmcgdGhlIGFic2VuY2Ugb2YgYW4gYXN0ZXJpc2suPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KNS41LiAmbmJzcDtFeGFtcGxlczxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CkdpdmVuIHRoYXQgdGhlIGNvbWJpbmVkIGF1ZGlvL3ZpZGVvIG1lY2hhbmlzbSBpcyB0aGUgb25s
eTxiciBjbGFzcz0iIj4NCmlycmVndWxhcml0eTxiciBjbGFzcz0iIj4NCmluIHRoaXMgc3lzdGVt
LCB0aGVyZSBvdWdodCB0byBiZSBhbiBleGFtcGxlIG9mIGl0LiAmbmJzcDtFLmcuLDxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO0FuIGV4YW1wbGUgb2YgYSBzdXBwbGVt
ZW50YWwgdmlkZW8gc3RyZWFtIHdpdGggYSBzcG9rZW4gbGFuZ3VhZ2U8YnIgY2xhc3M9IiI+DQom
bmJzcDsmbmJzcDthdWRpbyBzdHJlYW06PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT12aWRlbyA1MTM3MiBSVFAvQVZQIDMxIDMyPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1pbnRsYW5nLXNl
bmQ6ZW48YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDthPWh1bWlu
dGxhbmctcmVjdjplbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwO209YXVkaW8gNDkyNTAgUlRQL0FWUCAyMDxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2E9aHVtaW50bGFuZy1zZW5kOmVuPGJyIGNsYXNz
PSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1pbnRsYW5nLXJlY3Y6ZW48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo2LiAmbmJzcDtJQU5BIENvbnNpZGVyYXRpb25z
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7aHVtaW50bGFuZy12YWx1ZSA9ICZuYnNwO0xhbmd1YWdlLVRhZyBbIGFzdGVyaXNrIF08YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs7IExhbmd1YWdl
LVRhZyBkZWZpbmVkIGluIFJGQyA1NjQ2PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7YXN0ZXJpc2sgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7PSAmbmJzcDsmcXVvdDsqJnF1b3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0Kcy9MYW5ndWFnZS1UYWcgZGVmaW5lZCBpbiBSRkMgNTY0Ni9MYW5ndWFnZS1UYWcgYXMg
ZGVmaW5lZCBpbiBSRkM8YnIgY2xhc3M9IiI+DQo1NjQ2LzxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCkJ1dCBwZXJoYXBzIGFsc28gcy9SRkMgNTY0Ni9CQ1AgNDcvLCB3aGljaCBlbnN1cmVz
IHRoYXQgJnF1b3Q7aHVtaW50bGFuZyZxdW90OzxiciBjbGFzcz0iIj4NCnRyYWNrcyB0aGUgY3Vy
cmVudCB2ZXJzaW9uIG9mIGxhbmd1YWdlIHRhZ3MuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KQXBwZW5kaXggQS4gJm5ic3A7SGlzdG9yaWMgQWx0ZXJuYXRpdmUgUHJvcG9zYWw6IENhbGxl
ci1wcmVmczxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoaXM8YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDtyZXN1bHRzIGluIGEgbW9yZSBmcmFnaWxlIHNvbHV0aW9u
IHNpbmNlIHRoZSBtZWRpYSBtb2RhbGl0eSBhbmQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDts
YW5ndWFnZSB3b3VsZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNp
ZmljPGJyIGNsYXNzPSIiPg0KbWVkaWE8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtmb3JtYXRz
ICh3aGljaCBpbmhlcmVudGx5IGluY2x1ZGUgdGhlIG1vZGFsaXR5KSB3b3VsZCBiZTxiciBjbGFz
cz0iIj4NCm5lZ290aWF0ZWQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDthdCBhIGRpZmZlcmVu
dCBsZXZlbCAodHlwaWNhbGx5IFNEUCwgZXNwZWNpYWxseSBpbiB0aGUgZW1lcmdlbmN5PGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbGluZyBjYXNlcyksIG1ha2luZyBpdCBlYXNpZXIgdG8g
aGF2ZSBtaXNtYXRjaGVzIChzdWNoIGFzIHdoZXJlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7
dGhlIG1lZGlhIG1vZGFsaXR5IG5lZ290aWF0ZWQgaW4gU0lQIGRvbid0IG1hdGNoIHdoYXQgd2Fz
PGJyIGNsYXNzPSIiPg0KbmVnb3RpYXRlZDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzaW5n
IFNEUCkuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJnF1b3Q7dGhlIG1lZGlhIG1vZGFs
aXR5IGFuZCBsYW5ndWFnZSB3b3VsZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCZxdW90OyBpc24n
dDxiciBjbGFzcz0iIj4NCnF1aXRlIHRoZSByaWdodCB3YXkgdG8gc2F5IGl0IGJlY2F1c2UgU0lQ
IGlzbid0IGV4cGxpY2l0bHk8YnIgY2xhc3M9IiI+DQpuZWdvdGlhdGluZzxiciBjbGFzcz0iIj4N
CnRoZSBtb2RhbGl0eS4gJm5ic3A7QmV0dGVyIHdvdWxkIGJlPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Li4uIHRoZSBsYW5ndWFnZSAoYW5kIGJ5IGltcGxpY2F0aW9u
IHRoZSBtZWRpYSBtb2RhbGl0eSkgd291bGQgYmU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtu
ZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNpZmljIG1lZGlhICh3aGljaDxi
ciBjbGFzcz0iIj4NCmluaGVyZW50bHk8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtpbmNsdWRl
IHRoZSBtb2RhbGl0aWVzIGFuZCBmb3JtYXRzKSB3b3VsZCBiZSBuZWdvdGlhdGVkIGF0IGE8YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDtkaWZmZXJlbnQgbGV2ZWwgLi4uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KW0VORF08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCxzYW5zLXNl
cmlmO2ZvbnQtc2l6ZToxMXB4O2NvbG9yOiM5OTk5OTk7Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCxzYW5zLXNlcmlmO2NvbG9yOiM5OTk5OTk7IG1zby1mYXJl
YXN0LWZvbnQtZmFtaWx5OiBBcmlhbDsgbXNvLWZhcmVhc3QtdGhlbWUtZm9udDogbWlub3ItbGF0
aW47IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAmcXVvdDtBcmlhbCZxdW90OzsgbXNvLWFuc2ktbGFu
Z3VhZ2U6IEVOLVVTOyBtc28tZmFyZWFzdC1sYW5ndWFnZTogRU4tR0I7IG1zby1iaWRpLWxhbmd1
YWdlOiBBUi1TQSI+VGhpcw0KIGVtYWlsIGFuZCBpdHMgYXR0YWNobWVudHMgYXJlIGludGVuZGVk
IGZvciB0aGUgYWJvdmUgbmFtZWQgb25seSBhbmQgbWF5IGJlIGNvbmZpZGVudGlhbC4gSWYgdGhl
eSBoYXZlIGNvbWUgdG8geW91IGluIGVycm9yIHlvdSBtdXN0IHRha2Ugbm8gYWN0aW9uIGJhc2Vk
IG9uIHRoZW0sIG5vciBtdXN0IHlvdSBjb3B5IG9yIHNob3cgdGhlbSB0byBhbnlvbmU7IHBsZWFz
ZSByZXBseSB0byB0aGlzIGVtYWlsIG9yIGNhbGwgJiM0Mzs0NCAyMDcgMzU2IDA2MDANCiBhbmQg
aGlnaGxpZ2h0IHRoZSBlcnJvci4gPC9zcGFuPjwvcD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_--


From nobody Tue Feb 21 17:13:53 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297D11294A9; Tue, 21 Feb 2017 17:13:44 -0800 (PST)
X-Quarantine-ID: <UaO1YlHoDi94>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaO1YlHoDi94; Tue, 21 Feb 2017 17:13:41 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5FF129443; Tue, 21 Feb 2017 17:13:41 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 21 Feb 2017 17:04:27 -0800
Mime-Version: 1.0
Message-Id: <p06240608d4d2961c0304@[99.111.97.136]>
In-Reply-To: <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 21 Feb 2017 17:13:33 -0800
To: Natasha Rooney <nrooney@gsma.com>, Dale Worley <worley@ariadne.com>, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/CP8aU723znnIKfkDXiECRGYru5I>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-slim-negotiating-human-language.all@ietf.org" <draft-ietf-slim-negotiating-human-language.all@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:13:44 -0000

I am almost done with my reply.  I wasn't ignoring Dale, I've been 
working on his comments.

At 11:28 PM +0000 2/21/17, Natasha Rooney wrote:

>  Hi Dale! Many thanks for these comments, as one of the SLIM chairs 
> I'll work on getting some answers to you or I'll request the author 
> or one of the SLIM active participants to respond.
>
>  Bernard, Randall and SLIM - see below re Dale's points. 
>
>
>  **** A. Call failure ****
>  Randall or Bernard can you respond to this? I imagine the UA call 
> failure method is UA specific, but if there is a clash with SIP 
> level call fail then this should be addressed.
>
>  **** B. Audio/Video coordination ****
>  I believe the theory behind the current draft is that the spoken 
> and video streams will be different in the cases of such things as 
> sign language. Video could therefore be sign and audio would be a 
> spoken language. I'm not sure if the suggestion he satisfies this 
> case?
>
>  **** C. "humintlang" seems long to me ****
>  Bernard - I don't see the issue with shortening humintlang, but the 
> group might. I suggest we throw this to the group for discussion.
>
>  **** D. Use the Accept-Language syntax ****
>  Randall and Bernard - is this an acceptable change? Or one we need 
> to discuss further. Seems like a reasonable request, but also a 
> larger change, which is why I ask!
>
>  **** E. Have an attribute to abbreviate the 
> bidirectionally-symmetric case ****
>  I do not remember us having this discussion within the group, 
> although it may have occurred before I became chair.
>  Randall, Brian or Bernard - has this idea been discussed before? If 
> so, can one of you respond with an explanation as to why we haven't 
> done this?
>
>  **** Editorial comments and nits *****
>  Randall - can you take a look through Dale's editorial comments and 
> shout if there is any problems with these suggestions; if 
> everything is ok please make the changes.
>
>  Thanks all!
>
>  Natasha Rooney | Internet Engineering Director | Internet and Web 
> Team | Technology | GSMA 
> | <mailto:nrooney@gsma.com>nrooney@gsma.com | +44 (0) 7730 219 765 
> | @thisNatasha | Skype: <mailto:nrooney@gsm.org>nrooney@gsm.org
>
>>  On 18 Feb 2017, at 02:32, Dale Worley 
>> <<mailto:worley@ariadne.com>worley@ariadne.com> wrote:
>>
>>  Reviewer: Dale Worley
>>  Review result: Ready with Nits
>>
>>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>>  Review Team (Gen-ART) reviews all IETF documents being processed
>>  by the IESG for the IETF Chair.  Please treat these comments just
>>  like any other last call comments.
>>
>>  For more information, please see the FAQ at
>> 
>> <<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>  Document:  draft-ietf-slim-negotiating-human-language-06
>>  Reviewer:  Dale R. Worley
>>  Review Date:  2017-02-17
>>  IETF LC End Date:  2017-02-20
>>  IESG Telechat date:  [unknown]
>>
>>  Summary:
>>        This draft is basically ready for publication, but has nits
>>        that should be fixed before publication.
>>
>>  * Technical comments
>>
>>  A. Call failure
>>
>>  If a call fails due to no available language match, in what way(s)
>>  does it fail?  Section 5.3 says
>>
>>    If such an offer is received, the receiver MAY
>>    reject the media, ignore the language specified, or attempt to
>>    interpret the intent
>>
>>  But I suspect it's also allowed for the UAS to fail the call at the
>>  SIP level.  Whether or not that is allowed (or at least envisioned)
>>  should be described.  And what response code(s)/warn-code(s) should
>>  be
>>  used for that?
>>
>>  B. Audio/Video coordination
>>
>>    5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>    Note that while signed language tags are used with a video stream
>>  to
>>    indicate sign language, a spoken language tag for a video stream
>>  in
>>    parallel with an audio stream with the same spoken language tag
>>    indicates a request for a supplemental video stream to see the
>>    speaker.
>>
>>  And there's a similar paragraph in 5.4:
>>
>>>    A spoken language tag for a video stream in conjunction with an
>>>
>>  audio
>>
>>>    stream with the same language might indicate a request for
>>>    supplemental video to see the speaker.
>>>
>>
>>  I think this mechanism needs to be described more exactly, and in
>>  particular, it should not depend on the UA understanding which
>>  language tags are spoken language tags.  It seems to me that a
>>  workable rule is that there is an audio stream and a video stream and
>>  they specify exactly the same language tag in their respective
>>  humintlang attributes.  In that case, it is a request for a spoken
>>  language with simultaneous video of the speaker, and those requests
>>  should be considered satisfied only if both streams can be
>>  established.
>>
>>  * The following three items are adjustments to the design which I'd
>>  like to know have been considered.
>>
>>  C. "humintlang" seems long to me
>>
>>  Given the excessive length of SDP in practice, it seems to me that a
>>  shorter attribute name would be desirable.  E.g., "humlang" as was
>>  used in some previous versions.  Or is there a coordinated usage with
>>  other names in the "hum*lang" pattern?
>>
>>  D. Use the Accept-Language syntax
>>
>>  It seems to me that it would better to use the Accept-Language syntax
>>  for the attribute values.  This allows (1) specifiying the quality of
>>  language experience, allowing clear description of bilingualism, (2)
>>  a
>>  unified method of specifying whether or not arbitrary languages are
>>  acceptable, and (3) abbreviating SDP descriptions.
>>
>>  In a way, the fact that the current proposal seems to require (but
>>  does not directly specify) the coordinated absence/presence of an
>>  asterisk on all of the repetitions of humintlang-send or
>>  humintlang-recv is a warning that the syntax doesn't represent the
>>  semantics as well as it might.
>>
>>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>
>>  Note that all examples are bidirectionally symmetric, and the text
>>  says that requests and responses SHOULD be bidirectionally symmetric.
>>  So it would be a very useful abbreviation to define
>>  "humintlang=<value>" to be equivalent to the combination of
>>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>>
>>  Combining proposals C, D, and E, the examples become
>>
>>       m=audio 49170 RTP/AVP 0
>>       a=humlang:en
>>
>>       m=video 51372 RTP/AVP 31 32
>>       a=humlang:ase,*;q=0.1
>>
>>       m=audio 49250 RTP/AVP 20
>>       a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>>
>>       m=text 45020 RTP/AVP 103 104
>>       a=humlang:gr
>>
>>  which requires about half as many characters as they have now.
>>
>>  * Editorial comments and nits
>>
>>  Abstract
>>
>>    This document describes the need and a solution using new SDP
>>  stream
>>    attributes.
>>
>>  I don't think the term "stream attribute" is used in RFC 4566.
>>  Instead, it uses "media attribute".
>>
>>  1.  Introduction
>>
>>    caller and callee know each other or there is contextual or out of
>>    band information from which the language(s) and media modalities
>>  can
>>
>>  I think this context, it's preferred to hyphenate "out-of-band" to
>>  make it clearly be an adjective.
>>
>>    This approach has a number of benefits, including that it is
>>  generic
>>    (applies to all interactive communications negotiated using SDP)
>>  and
>>    not limited to emergency calls.
>>
>>  I think s/and not limited to/and is not limited to/ reads more
>>  smoothly.
>>
>>    But it is clearly useful in many other cases.  For
>>    example, someone calling a company call center or a Public Safety
>>    Answering Point (PSAP) should be able to indicate if one or more
>>    specific signed, written, and/or spoken languages are preferred,
>>  the
>>    callee should be able to indicate its capabilities in this area,
>>  and
>>    the call proceed using in-common language(s) and media forms.
>>
>>  I think s/preferred, the callee/preferred; the callee/ because the
>>  sentence is the concatenation of two sentences.
>>
>>  Perhaps s/in-common/shared/.
>>
>>    Including the user's human (natural) language preferences in the
>>    session establishment negotiation is independent of the use of a
>>    relay service and is transparent to a voice service provider.
>>
>>  I think it's even broader than "transparent to a voice service
>>  provider" -- it's transparent to any serivice provider, assuming that
>>  the media are language-neutral.
>>
>>    In the case of a call to e.g., an airline, the call could be
>>    automatically handled by a Spanish-speaking agent.
>>
>>  I think s/handled by/routed to/ is the usual usage.
>>
>>  3.  Desired Semantics
>>
>>    The desired solution is a media attribute (preferably per
>>  direction)
>>    that may be used within an offer to indicate the preferred
>>  language
>>    of each (direction of a) media stream, and within an answer to
>>    indicate the accepted language.
>>
>>  In this one instance, I think you want to use "language(s)" to drive
>>  home that that multiple languages can be specified:  "within an offer
>>  to indicate the preferred language(s)".
>>
>>    (Negotiating multiple simultaneous languages within a media stream
>>  is
>>    out of scope, as the complexity of doing so outweighs the
>>    usefulness.)
>>
>>  You might want to say instead "(Negotiating multiple simultaneous
>>  languages within a media stream is out of scope for this document.)"
>>  to ensure that nobody decides to argue whether "the complexity of
>>  doing so outweighs the usefulness".
>>
>>  4.  The existing 'lang' attribute
>>
>>    RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>    similar to what is needed here, but is not sufficiently detailed
>>  for
>>    use here.
>>
>>  "for use here" isn't quite right.  Maybe "is not sufficiently
>>  specific
>>  or flexible to satisfy the requirements".
>>
>>    In addition, it is not mentioned in [RFC3264]
>>
>>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>  attribute".
>>
>>  5.  Proposed Solution
>>
>>  Perhaps /Proposed Solution/Solution/, since once this draft is
>>  approved, it becomes the solution.
>>
>>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>       a=humintlang-send:<language tag>
>>       a=humintlang-recv:<language tag>
>>
>>  This is presented as the generic form of the attributes, but there is
>>  no indication of the posible asterisk.
>>
>>    The values constitute a list of languages
>>    in preference order (first is most preferred).
>>
>>  "The values" isn't very clear, because the values are in successive
>>  attributes.  You want to say something like "The sequence of values
>>  in
>>  the occurrences of one of these attributes constitutes ...".
>>  However,
>>  see the technical comments above.
>>
>>    When placing an emergency call, and in any other case where the
>>    language cannot be assumed from context, each media stream in an
>>    offer primarily intended for human language communication SHOULD
>>    specify both (or in some cases, one of) the 'humintlang-send' and
>>    'humintlang-recv' attributes.
>>
>>  Probably s/assumed/inferred/.
>>
>>  Could you be more accurate by
>>  s/or in some cases/or for unidirectional streams/?
>>
>>  5.3.  Advisory vs Required
>>
>>    The mechanism for indicating this preference is that, in an offer,
>>  if
>>    the last character of any of the 'humintlang-recv' or 'humintlang-
>>    send' values is an asterisk, this indicates a request to not fail
>>  the
>>    call (similar to SIP Accept-Language syntax).  Either way, the
>>  called
>>    party MAY ignore this, e.g., for the emergency services use case,
>>  a
>>    PSAP will likely not fail the call.
>>
>>  The construction of this paragraph isn't quite complete.  It says
>>  that
>>  if an asterisk is present, a request shouldn't fail, but it doesn't
>>  say that if no asterisk is present, a request should fail if there is
>>  no language match.  And it's the latter condition that makes the
>>  second sentence meaningful.  So I think you want to insert between
>>  the
>>  two sentences one regarding the absence of an asterisk.
>>
>>  5.5.  Examples
>>
>>  Given that the combined audio/video mechanism is the only
>>  irregularity
>>  in this system, there ought to be an example of it.  E.g.,
>>
>>    An example of a supplemental video stream with a spoken language
>>    audio stream:
>>
>>       m=video 51372 RTP/AVP 31 32
>>       a=humintlang-send:en
>>       a=humintlang-recv:en
>>
>>       m=audio 49250 RTP/AVP 20
>>       a=humintlang-send:en
>>       a=humintlang-recv:en
>>
>>  6.  IANA Considerations
>>
>>       humintlang-value =  Language-Tag [ asterisk ]
>>                           ; Language-Tag defined in RFC 5646
>>       asterisk         =  "*"
>>
>>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>  5646/
>>
>>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>  tracks the current version of language tags.
>>
>>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>>
>>    This
>>    results in a more fragile solution since the media modality and
>>    language would be negotiated using SIP, and then the specific
>>  media
>>    formats (which inherently include the modality) would be
>>  negotiated
>>    at a different level (typically SDP, especially in the emergency
>>    calling cases), making it easier to have mismatches (such as where
>>    the media modality negotiated in SIP don't match what was
>>  negotiated
>>    using SDP).
>>
>>  "the media modality and language would be negotiated using SIP" isn't
>>  quite the right way to say it because SIP isn't explicitly
>>  negotiating
>>  the modality.  Better would be
>>
>>    ... the language (and by implication the media modality) would be
>>    negotiated using SIP, and then the specific media (which
>>  inherently
>>    include the modalities and formats) would be negotiated at a
>>    different level ...
>>
>>  [END]
>>
>
>  This email and its attachments are intended for the above named 
> only and may be confidential. If they have come to you in error you 
> must take no action based on them, nor must you copy or show them 
> to anyone; please reply to this email or call +44 207 356 0600 and 
> highlight the error.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
There's nothing wrong with me.  Maybe there's something wrong with
the universe.       --'Dr. Beverly Crusher' in ST:TNG _Remember Me_.


From nobody Tue Feb 21 17:45:01 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127401294D2; Tue, 21 Feb 2017 17:45:00 -0800 (PST)
X-Quarantine-ID: <1vzWfK52Lwnm>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vzWfK52Lwnm; Tue, 21 Feb 2017 17:44:58 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEBF1294E4; Tue, 21 Feb 2017 17:44:58 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 21 Feb 2017 17:35:44 -0800
Mime-Version: 1.0
Message-Id: <p06240602d4d236a5a2dd@[99.111.97.136]>
In-Reply-To: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 21 Feb 2017 17:44:42 -0800
To: "Dale Worley" <worley@ariadne.com>, <gen-art@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nseBPO__ghC1ZBX1-K1e0rvnz3M>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:45:00 -0000

Hi Dale,

Thank you for your review, I appreciate it.  Please see inline.

At 6:32 PM -0800 2/17/17, Dale Worley wrote:

>  Reviewer: Dale Worley
>  Review result: Ready with Nits
>
>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>  Review Team (Gen-ART) reviews all IETF documents being processed
>  by the IESG for the IETF Chair.  Please treat these comments just
>  like any other last call comments.
>
>  For more information, please see the FAQ at
>  <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>  Document:  draft-ietf-slim-negotiating-human-language-06
>  Reviewer:  Dale R. Worley
>  Review Date:  2017-02-17
>  IETF LC End Date:  2017-02-20
>  IESG Telechat date:  [unknown]
>
>  Summary:
>         This draft is basically ready for publication, but has nits
>         that should be fixed before publication.
>
>  * Technical comments
>
>  A. Call failure
>
>  If a call fails due to no available language match, in what way(s)
>  does it fail?  Section 5.3 says
>
>     If such an offer is received, the receiver MAY
>     reject the media, ignore the language specified, or attempt to
>     interpret the intent
>
>  But I suspect it's also allowed for the UAS to fail the call at the
>  SIP level.  Whether or not that is allowed (or at least envisioned)
>  should be described.  And what response code(s)/warn-code(s) should
>  be
>  used for that?

The text you quote has been deleted.  The draft does not mandate if 
the call should proceed or fail if there is no language match 
possible, although the draft does provide an optional mechanism to 
indicate the caller's preference that the call not fail, and the 
draft does mention that in the emergency services case, the call will 
likely proceed, but that's a matter of policy not protocol.

>
>  B. Audio/Video coordination
>
>     5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>
>     Note that while signed language tags are used with a video stream
>  to
>     indicate sign language, a spoken language tag for a video stream
>  in
>     parallel with an audio stream with the same spoken language tag
>     indicates a request for a supplemental video stream to see the
>     speaker.
>
>  And there's a similar paragraph in 5.4:
>
>>     A spoken language tag for a video stream in conjunction with an
>  audio
>>     stream with the same language might indicate a request for
>>     supplemental video to see the speaker.
>
>  I think this mechanism needs to be described more exactly, and in
>  particular, it should not depend on the UA understanding which
>  language tags are spoken language tags.  It seems to me that a
>  workable rule is that there is an audio stream and a video stream and
>  they specify exactly the same language tag in their respective
>  humintlang attributes.  In that case, it is a request for a spoken
>  language with simultaneous video of the speaker, and those requests
>  should be considered satisfied only if both streams can be
>  established.

The text you quote has been deleted.  A media stream for supplemental 
purposes can be negotiated without a language tag, as normal.

>
>  * The following three items are adjustments to the design which I'd
>  like to know have been considered.
>
>  C. "humintlang" seems long to me
>
>  Given the excessive length of SDP in practice, it seems to me that a
>  shorter attribute name would be desirable.  E.g., "humlang" as was
>  used in some previous versions.  Or is there a coordinated usage with
>  other names in the "hum*lang" pattern?

There is no intent for a coordinated pattern.  The name was chosen 
years ago to avoid potential confusion with the 'lang' attribute.  Is 
it worth reopening the issue to potentially save three characters per 
SDP line with a language?

>
>  D. Use the Accept-Language syntax
>
>  It seems to me that it would better to use the Accept-Language syntax
>  for the attribute values.  This allows (1) specifiying the quality of
>  language experience, allowing clear description of bilingualism, (2)
>  a
>  unified method of specifying whether or not arbitrary languages are
>  acceptable, and (3) abbreviating SDP descriptions.
>
>  In a way, the fact that the current proposal seems to require (but
>  does not directly specify) the coordinated absence/presence of an
>  asterisk on all of the repetitions of humintlang-send or
>  humintlang-recv is a warning that the syntax doesn't represent the
>  semantics as well as it might.

The group considered multiple proposals to permit specifying quality, 
preference, q-values, etc. but decided to keep things simple for this 
draft.  There is no intent to require the use of an asterisk (to 
indicate a preference by the caller to not fail the call).  The 
asterisk is a very mild mechanism with no normative effects.  It 
merely conveys the preference of the caller, and is not binding on 
the answerer.

>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>
>  Note that all examples are bidirectionally symmetric, and the text
>  says that requests and responses SHOULD be bidirectionally symmetric.
>  So it would be a very useful abbreviation to define
>  "humintlang=<value>" to be equivalent to the combination of
>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>
>  Combining proposals C, D, and E, the examples become
>
>        m=audio 49170 RTP/AVP 0
>        a=humlang:en
>
>        m=video 51372 RTP/AVP 31 32
>        a=humlang:ase,*;q=0.1
>
>        m=audio 49250 RTP/AVP 20
>        a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>
>        m=text 45020 RTP/AVP 103 104
>        a=humlang:gr
>
>  which requires about half as many characters as they have now.

A third attribute without the "-send" or "-recv" to indicate 
bidirectionality would reduce the characters in the SDP block, at the 
cost of some added complexity (e.g., what if all three appear).  I 
don't believe this has been discussed in the group.

>  * Editorial comments and nits
>
>  Abstract
>
>     This document describes the need and a solution using new SDP
>  stream
>     attributes.
>
>  I don't think the term "stream attribute" is used in RFC 4566.
>  Instead, it uses "media attribute".

Fixed.

>  1.  Introduction
>
>     caller and callee know each other or there is contextual or out of
>     band information from which the language(s) and media modalities
>  can
>
>  I think this context, it's preferred to hyphenate "out-of-band" to
>  make it clearly be an adjective.

>  OK.


>     This approach has a number of benefits, including that it is
>  generic
>     (applies to all interactive communications negotiated using SDP)
>  and
>     not limited to emergency calls.
>
>  I think s/and not limited to/and is not limited to/ reads more
>  smoothly.

There's no harm in the extra "is" so I'm happy to add it.

>     But it is clearly useful in many other cases.  For
>     example, someone calling a company call center or a Public Safety
>     Answering Point (PSAP) should be able to indicate if one or more
>     specific signed, written, and/or spoken languages are preferred,
>  the
>     callee should be able to indicate its capabilities in this area,
>  and
>     the call proceed using in-common language(s) and media forms.
>
>  I think s/preferred, the callee/preferred; the callee/ because the
>  sentence is the concatenation of two sentences.

I reworded the sentence to flow better:

    For example, it is helpful that someone calling a company call center
    or a Public Safety Answering Point (PSAP) be able to indicate
    preferred signed, written, and/or spoken languages, the callee be
    able to indicate its capabilities in this area, and the call proceed
    using the language(s) and media forms supported by both.

>  Perhaps s/in-common/shared/.

Fixed in the rewording above.

>
>     Including the user's human (natural) language preferences in the
>     session establishment negotiation is independent of the use of a
>     relay service and is transparent to a voice service provider.
>
>  I think it's even broader than "transparent to a voice service
>  provider" -- it's transparent to any serivice provider, assuming that
>  the media are language-neutral.

I changed it to read "voice or other service provider".

>
>     In the case of a call to e.g., an airline, the call could be
>     automatically handled by a Spanish-speaking agent.
>
>  I think s/handled by/routed to/ is the usual usage.

We are trying to be careful in the draft to not imply that it is 
discussing call routing.  I'd rather keep the more generic "handled 
by".

>
>  3.  Desired Semantics
>
>     The desired solution is a media attribute (preferably per
>  direction)
>     that may be used within an offer to indicate the preferred
>  language
>     of each (direction of a) media stream, and within an answer to
>     indicate the accepted language.
>
>  In this one instance, I think you want to use "language(s)" to drive
>  home that that multiple languages can be specified:  "within an offer
>  to indicate the preferred language(s)".
>
>     (Negotiating multiple simultaneous languages within a media stream
>  is
>     out of scope, as the complexity of doing so outweighs the
>     usefulness.)
>
>  You might want to say instead "(Negotiating multiple simultaneous
>  languages within a media stream is out of scope for this document.)"
>  to ensure that nobody decides to argue whether "the complexity of
>  doing so outweighs the usefulness".

I agree and deleted "the complexity of doing so outweighs the usefulness".

>
>  4.  The existing 'lang' attribute
>
>     RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>     similar to what is needed here, but is not sufficiently detailed
>  for
>     use here.
>
>  "for use here" isn't quite right.  Maybe "is not sufficiently
>  specific
>  or flexible to satisfy the requirements".
>
>     In addition, it is not mentioned in [RFC3264]
>
>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>  attribute".

OK, accepted both changes.

>
>  5.  Proposed Solution
>
>  Perhaps /Proposed Solution/Solution/, since once this draft is
>  approved, it becomes the solution.

OK.

>
>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>
>        a=humintlang-send:<language tag>
>        a=humintlang-recv:<language tag>
>
>  This is presented as the generic form of the attributes, but there is
>  no indication of the posible asterisk.

The syntax has been deleted from 5.2 since it's now in 6.

>
>     The values constitute a list of languages
>     in preference order (first is most preferred).
>
>  "The values" isn't very clear, because the values are in successive
>  attributes.  You want to say something like "The sequence of values
>  in
>  the occurrences of one of these attributes constitutes ...".
>  However,
>  see the technical comments above.

The text was reworded to read:

    The values from all
    instances of the attribute constitute a list of languages in
    preference order (first is most preferred).


>
>     When placing an emergency call, and in any other case where the
>     language cannot be assumed from context, each media stream in an
>     offer primarily intended for human language communication SHOULD
>     specify both (or in some cases, one of) the 'humintlang-send' and
>     'humintlang-recv' attributes.
>
>  Probably s/assumed/inferred/.

I agree.

>
>  Could you be more accurate by
>  s/or in some cases/or for unidirectional streams/?

I agree.

>
>  5.3.  Advisory vs Required
>
>     The mechanism for indicating this preference is that, in an offer,
>  if
>     the last character of any of the 'humintlang-recv' or 'humintlang-
>     send' values is an asterisk, this indicates a request to not fail
>  the
>     call (similar to SIP Accept-Language syntax).  Either way, the
>  called
>     party MAY ignore this, e.g., for the emergency services use case,
>  a
>     PSAP will likely not fail the call.
>
>  The construction of this paragraph isn't quite complete.  It says
>  that
>  if an asterisk is present, a request shouldn't fail, but it doesn't
>  say that if no asterisk is present, a request should fail if there is
>  no language match.  And it's the latter condition that makes the
>  second sentence meaningful.  So I think you want to insert between
>  the
>  two sentences one regarding the absence of an asterisk.

I've reworded the section to read:

    A consideration with the ability to negotiate language is if the call
    proceeds or fails if the callee does not support any of the languages
    requested by the caller.  This document does not mandate either
    behavior, although it does provide a way for the caller to indicate a
    preference for the call succeeding when there is no language in
    common.  It is OPTIONAL for the callee to honor this preference.  For
    example, a PSAP is likely to attempt the call even without an
    indicated preference when there is no language in common, while a
    call center might choose to fail the call.

    The mechanism for indicating this preference is that, in an offer, if
    the last character of any of the 'humintlang-recv' or 'humintlang-
    send' values is an asterisk, this indicates a request to not fail the
    call.  The called party MAY ignore the indication, e.g., for the
    emergency services use case, regardless of the absence of an
    asterisk, a PSAP will likely not fail the call; some call centers
    might reject a call even with an asterisk.

>  5.5.  Examples
>
>  Given that the combined audio/video mechanism is the only
>  irregularity
>  in this system, there ought to be an example of it.  E.g.,
>
>     An example of a supplemental video stream with a spoken language
>     audio stream:
>
>        m=video 51372 RTP/AVP 31 32
>        a=humintlang-send:en
>        a=humintlang-recv:en
>
>        m=audio 49250 RTP/AVP 20
>        a=humintlang-send:en
>        a=humintlang-recv:en

If the video stream is supplemental then it doesn't have a language 
(the text that suggested otherwise has been deleted).  But I am 
considering adding more examples.

>
>  6.  IANA Considerations
>
>        humintlang-value =  Language-Tag [ asterisk ]
>                            ; Language-Tag defined in RFC 5646
>        asterisk         =  "*"
>
>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>  5646/
>
>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>  tracks the current version of language tags.

Ok.

>
>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>
>     This
>     results in a more fragile solution since the media modality and
>     language would be negotiated using SIP, and then the specific
>  media
>     formats (which inherently include the modality) would be
>  negotiated
>     at a different level (typically SDP, especially in the emergency
>     calling cases), making it easier to have mismatches (such as where
>     the media modality negotiated in SIP don't match what was
>  negotiated
>     using SDP).
>
>  "the media modality and language would be negotiated using SIP" isn't
>  quite the right way to say it because SIP isn't explicitly
>  negotiating
>  the modality.  Better would be
>
>     ... the language (and by implication the media modality) would be
>     negotiated using SIP, and then the specific media (which
>  inherently
>     include the modalities and formats) would be negotiated at a
>     different level ...

This section has been deleted.

>
>  [END]


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
I make a fortune from criticizing the policy of the government, and
then hand it over to the government in taxes to keep it going.
                                              --George Bernard Shaw


From nobody Wed Feb 22 01:09:16 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C362129457; Wed, 22 Feb 2017 01:09:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xibN_aVW40m; Wed, 22 Feb 2017 01:09:13 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2C231293DF; Wed, 22 Feb 2017 01:09:12 -0800 (PST)
Received: from unescapeable.local (2.204-14-84.ripe.coltfrance.com [84.14.204.2]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1M997Y9022800 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 22 Feb 2017 03:09:09 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 2.204-14-84.ripe.coltfrance.com [84.14.204.2] claimed to be unescapeable.local
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com> <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
Date: Wed, 22 Feb 2017 10:09:01 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4BA9FE9488D2E8686F0044F9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/pfjZ9UcscrdJuwdfrwJR6JutM0Q>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 09:09:15 -0000

This is a multi-part message in MIME format.
--------------4BA9FE9488D2E8686F0044F9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

I would simply delete "To ensure precise accuracy in time determination" 
and start the sentence at "These actions"

RjS


On 2/15/17 9:40 PM, Greg Mirsky wrote:
> Hi Robert,
> safe travel and here's another version for your consideration. The 
> point I'm trying to convey is that the jitter is real but must be 
> accounted not as part of propagation delay but as residence time. Hope 
> I'm getting close.
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface.
>     To ensure precise accuracy in time determination these actions should
>     be done as close to the physical layer as possible at the same point
>     of packet processing striving to avoid introducing the appearance of
>     jitter in propogation delay whereas it should be accounted as
>     residence time.
> Regards,
> Greg
>
> On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>
>
>     On 2/15/17 11:20 AM, Greg Mirsky wrote:
>>     Hi Robert,
>>     yes, you've absolutely correct in your example. The importance of
>>     RTM is to exclude and quantify, as much as possible, jitter from
>>     propagation delay. I've updated the wording to reflect that.
>>     Below is new text I propose, please let me know if it makes it
>>     clearer.
>>         Each RTM-capable
>>         node on the explicit path receives an RTM packet and records the time
>>         at which it receives that packet at its ingress interface as well as
>>         the time at which it transmits that packet from its egress interface.
>>         These actions should be done as close to the physical layer as
>>         possible at the same point of packet processing striving to avoid
>>         introduction of jitter in propogation delay to ensure precise
>>         accuracy in time determination.
>     perhaps change "avoid introduction of jitter" to "avoid
>     introducing the appearance of jitter that's not really there"?
>
>     (I'm about to board a plane, so further responses will be very
>     delayed).
>>     Regards,
>>     Greg
>>
>>     On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks
>>     <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>
>>
>>
>>         On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>>         Hi Robert,
>>>         Section 5 Data Plane Theory of Operation has the following
>>>         recommendation on reading time value at ingress and egress:
>>>             Each RTM-capable
>>>             node on the explicit path receives an RTM packet and records the time
>>>             at which it receives that packet at its ingress interface as well as
>>>             the time at which it transmits that packet from its egress interface;
>>>             this should be done as close to the physical layer as possible to
>>>             ensure precise accuracy in time determination.
>>>         Do you find the text sufficient in providing guidance to an implementer of RTM?
>>         Well, no - that was point in the text from my review of -12
>>         that caused me to make comment in the first place.
>>
>>         What does "precise accuracy" even _MEAN_? You're waving your
>>         hands with words that don't help the reader guess what you
>>         mean at the moment. The subsequent email exchange said the
>>         important part was that you measure _precisely_ (in that the
>>         measurements are always taken the same way), but accuracy
>>         isn't that important (you've (and here by "you" I mean the
>>         set of people that have responded to the review") told me
>>         it's not important whether the reading is taken at the
>>         beginning of the bit-stream, the end, or several 1000
>>         nanoseconds after the last bit came off the physical media as
>>         long as it's done the same way for each packet). The fact
>>         that you're carrying a measurement that can talk about times
>>         smaller than the interarrival time for individual bits for
>>         some real world line speeds says that different
>>         implementations taking the measurement different ways is
>>         going to result in different residence time measurements,
>>         even if the residence time was really identical. You've told
>>         me that's not important to the protocol using the measurement
>>         as long as the an individual implementation doesn't introduce
>>         something that will look to the using protocol like jitter
>>         that's not really there.
>>
>>         The text does not say that to an implementer right now.
>>
>>         To restate that long paragraph with maybe a longer one, 
>>         assume a simplified world where everything is perfectly
>>         constant. Packets are all flowing at the same size and same
>>         rate. For reference, I assert that the time between the first
>>         bit of a packet entering the system taking the measurement
>>         and the first bit of that packet leaving the system is
>>         exactly T (every time). You are telling me that if the system
>>         returns cT for some constant T other than 1 (and not
>>         necessarily  close to 1), everything is fine. You're also
>>         telling me that if you replace the system with another that
>>         preserves T, but measures differently so that it returns c'T
>>         where c' != c, everything is fine. The important part to you
>>         is that c and c' don't change for their respective systems.
>>         (That surprises me, I can see how the way the clocks are
>>         going to use this will do the right thing, but I can't help
>>         but think someone later will look at the difference between
>>         the two systems and say something is wrong with one of them).
>>         What you've told me is not fine is that if you drop i a third
>>         system that also preserves T but reports aT where a _varies_
>>         over some range.
>>
>>         Have I heard you correctly?
>>>         Regards,
>>>         Greg
>>>
>>>         On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks
>>>         <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>>
>>>             Reviewer: Robert Sparks
>>>             Review result: Ready
>>>
>>>             I am the assigned Gen-ART reviewer for this draft. The
>>>             General Area
>>>             Review Team (Gen-ART) reviews all IETF documents being
>>>             processed
>>>             by the IESG for the IETF Chair. Please wait for
>>>             direction from your
>>>             document shepherd or AD before posting a new version of
>>>             the draft.
>>>
>>>             For more information, please see the FAQ at
>>>
>>>             <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>>>             <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>>>
>>>             Document: draft-ietf-mpls-residence-time-13
>>>             Reviewer: Robert Sparks
>>>             Review Date: 2017-02-13
>>>             IETF LC End Date: 2017-01-17
>>>             IESG Telechat date: 2017-03-02
>>>
>>>             Summary: Ready for publication as PS
>>>
>>>             Thanks for addressing my comments.
>>>             (I still think some discussion about taking arrival and
>>>             departure time
>>>             measurements would be helpful, even if it only said "do it
>>>             consistently so you don't indicate jitter that's not
>>>             really there".)
>>>
>>>
>>
>>
>
>


--------------4BA9FE9488D2E8686F0044F9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I would simply delete "To ensure precise accuracy in time
      determination" and start the sentence at "These actions"</p>
    <p>RjS<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/15/17 9:40 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>safe travel and here's another version for your
          consideration. The point I'm trying to convey is that the
          jitter is real but must be accounted not as part of
          propagation delay but as residence time. Hope I'm getting
          close.</div>
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,
          Robert Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"><span class="">
                <p><br>
                </p>
                <br>
                <div class="m_2800513769154960288moz-cite-prefix">On
                  2/15/17 11:20 AM, Greg Mirsky wrote:<br>
                </div>
              </span>
              <blockquote type="cite">
                <div dir="ltr">Hi Robert, <span class="">
                    <div>yes, you've absolutely correct in your example.
                      The importance of RTM is to exclude and quantify,
                      as much as possible, jitter from propagation
                      delay. I've updated the wording to reflect that.
                      Below is new text I propose, please let me know if
                      it makes it clearer.</div>
                    <div>
                      <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
                    </div>
                  </span></div>
              </blockquote>
              perhaps change "avoid introduction of jitter" to "avoid
              introducing the appearance of jitter that's not really
              there"?<br>
              <br>
              (I'm about to board a plane, so further responses will be
              very delayed). <br>
              <div>
                <div class="h5">
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
                        <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
                      </div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">On Wed, Feb 15, 2017 at
                        7:43 AM, Robert Sparks <span dir="ltr">&lt;<a
                            moz-do-not-send="true"
                            href="mailto:rjsparks@nostrum.com"
                            target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          <div bgcolor="#FFFFFF" text="#000000"><span>
                              <p><br>
                              </p>
                              <br>
                              <div
                                class="m_2800513769154960288m_3072934530585377958moz-cite-prefix">On
                                2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                              </div>
                              <blockquote type="cite">
                                <div dir="ltr">Hi Robert,
                                  <div>Section 5 Data Plane Theory of
                                    Operation has the following
                                    recommendation on reading time value
                                    at ingress and egress:</div>
                                  <div>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
                                  </div>
                                </div>
                              </blockquote>
                            </span> Well, no - that was point in the
                            text from my review of -12 that caused me to
                            make comment in the first place.<br>
                            <br>
                            What does "precise accuracy" even _MEAN_?
                            You're waving your hands with words that
                            don't help the reader guess what you mean at
                            the moment. The subsequent email exchange
                            said the important part was that you measure
                            _precisely_ (in that the measurements are
                            always taken the same way), but accuracy
                            isn't that important (you've (and here by
                            "you" I mean the set of people that have
                            responded to the review") told me it's not
                            important whether the reading is taken at
                            the beginning of the bit-stream, the end, or
                            several 1000 nanoseconds after the last bit
                            came off the physical media as long as it's
                            done the same way for each packet). The fact
                            that you're carrying a measurement that can
                            talk about times smaller than the
                            interarrival time for individual bits for
                            some real world line speeds says that
                            different implementations taking the
                            measurement different ways is going to
                            result in different residence time
                            measurements, even if the residence time was
                            really identical. You've told me that's not
                            important to the protocol using the
                            measurement as long as the an individual
                            implementation doesn't introduce something
                            that will look to the using protocol like
                            jitter that's not really there.<br>
                            <br>
                            The text does not say that to an implementer
                            right now.<br>
                            <br>
                            To restate that long paragraph with maybe a
                            longer one,  assume a simplified world where
                            everything is perfectly constant. Packets
                            are all flowing at the same size and same
                            rate. For reference, I assert that the time
                            between the first bit of a packet entering
                            the system taking the measurement and the
                            first bit of that packet leaving the system
                            is exactly T (every time). You are telling
                            me that if the system returns cT for some
                            constant T other than 1 (and not
                            necessarily  close to 1), everything is
                            fine. You're also telling me that if you
                            replace the system with another that
                            preserves T, but measures differently so
                            that it returns c'T where c' != c,
                            everything is fine. The important part to
                            you is that c and c' don't change for their
                            respective systems. (That surprises me, I
                            can see how the way the clocks are going to
                            use this will do the right thing, but I
                            can't help but think someone later will look
                            at the difference between the two systems
                            and say something is wrong with one of
                            them). What you've told me is not fine is
                            that if you drop i a third system that also
                            preserves T but reports aT where a _varies_
                            over some range.<br>
                            <br>
                            Have I heard you correctly?<span><br>
                              <blockquote type="cite">
                                <div dir="ltr">
                                  <div>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                                  </div>
                                </div>
                                <div class="gmail_extra"><br>
                                  <div class="gmail_quote">On Mon, Feb
                                    13, 2017 at 1:51 PM, Robert Sparks <span
                                      dir="ltr">&lt;<a
                                        moz-do-not-send="true"
                                        href="mailto:rjsparks@nostrum.com"
                                        target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                                    wrote:<br>
                                    <blockquote class="gmail_quote"
                                      style="margin:0 0 0
                                      .8ex;border-left:1px #ccc
                                      solid;padding-left:1ex">Reviewer:
                                      Robert Sparks<br>
                                      Review result: Ready<br>
                                      <br>
                                      I am the assigned Gen-ART reviewer
                                      for this draft. The General Area<br>
                                      Review Team (Gen-ART) reviews all
                                      IETF documents being processed<br>
                                      by the IESG for the IETF Chair.
                                      Please wait for direction from
                                      your<br>
                                      document shepherd or AD before
                                      posting a new version of the
                                      draft.<br>
                                      <br>
                                      For more information, please see
                                      the FAQ at<br>
                                      <br>
                                      &lt;<a moz-do-not-send="true"
                                        href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
                                        rel="noreferrer" target="_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                                      <br>
                                      Document:
                                      draft-ietf-mpls-residence-time<wbr>-13<br>
                                      Reviewer: Robert Sparks<br>
                                      Review Date: 2017-02-13<br>
                                      IETF LC End Date: 2017-01-17<br>
                                      IESG Telechat date: 2017-03-02<br>
                                      <br>
                                      Summary: Ready for publication as
                                      PS<br>
                                      <br>
                                      Thanks for addressing my comments.<br>
                                      (I still think some discussion
                                      about taking arrival and departure
                                      time<br>
                                      measurements would be helpful,
                                      even if it only said "do it<br>
                                      consistently so you don't indicate
                                      jitter that's not really there".)<br>
                                      <br>
                                    </blockquote>
                                  </div>
                                  <br>
                                </div>
                              </blockquote>
                              <br>
                            </span></div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------4BA9FE9488D2E8686F0044F9--


From nobody Wed Feb 22 02:57:51 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08B591296E1 for <gen-art@ietfa.amsl.com>; Wed, 22 Feb 2017 02:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DCpAxNO_yrZ for <gen-art@ietfa.amsl.com>; Wed, 22 Feb 2017 02:57:45 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3309F12968C for <gen-art@ietf.org>; Wed, 22 Feb 2017 02:57:45 -0800 (PST)
X-Halon-ID: b8c0bedd-f8ed-11e6-af90-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 22 Feb 2017 11:57:35 +0100 (CET)
To: Randall Gellens <rg+ietf@randy.pensive.org>, Dale Worley <worley@ariadne.com>, gen-art@ietf.org
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <p06240602d4d236a5a2dd@[99.111.97.136]>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
Date: Wed, 22 Feb 2017 11:57:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240602d4d236a5a2dd@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aX1XXKTti7ToFFSmqlZ7_0iWrVM>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
Subject: Re: [Gen-art] [Slim] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 10:57:49 -0000

A few comments inline,


Den 2017-02-22 kl. 02:44, skrev Randall Gellens:
> Hi Dale,
>
> Thank you for your review, I appreciate it.  Please see inline.
>
> At 6:32 PM -0800 2/17/17, Dale Worley wrote:
>
>>  Reviewer: Dale Worley
>>  Review result: Ready with Nits
>>
>>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>>  Review Team (Gen-ART) reviews all IETF documents being processed
>>  by the IESG for the IETF Chair.  Please treat these comments just
>>  like any other last call comments.
>>
>>  For more information, please see the FAQ at
>>  <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>  Document:  draft-ietf-slim-negotiating-human-language-06
>>  Reviewer:  Dale R. Worley
>>  Review Date:  2017-02-17
>>  IETF LC End Date:  2017-02-20
>>  IESG Telechat date:  [unknown]
>>
>>  Summary:
>>         This draft is basically ready for publication, but has nits
>>         that should be fixed before publication.
>>
>>  * Technical comments
>>
>>  A. Call failure
>>
>>  If a call fails due to no available language match, in what way(s)
>>  does it fail?  Section 5.3 says
>>
>>     If such an offer is received, the receiver MAY
>>     reject the media, ignore the language specified, or attempt to
>>     interpret the intent
>>
>>  But I suspect it's also allowed for the UAS to fail the call at the
>>  SIP level.  Whether or not that is allowed (or at least envisioned)
>>  should be described.  And what response code(s)/warn-code(s) should
>>  be
>>  used for that?
>
> The text you quote has been deleted.  The draft does not mandate if 
> the call should proceed or fail if there is no language match 
> possible, although the draft does provide an optional mechanism to 
> indicate the caller's preference that the call not fail, and the draft 
> does mention that in the emergency services case, the call will likely 
> proceed, but that's a matter of policy not protocol.
You may have a version where it is proposed that the text is deleted. We 
need to see that new text and agree if it was good to delete it.

There are more places in the draft where failing the call is mentioned, 
so the question about how it is failed is relevant anyway. A 603 Decline 
from the proxy would likely be the natural way to fail the call when it 
is because of lack of matching languages. But I do not see any natural 
way for an addressed UA to signal this.

>
>>
>>  B. Audio/Video coordination
>>
>>     5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>     Note that while signed language tags are used with a video stream
>>  to
>>     indicate sign language, a spoken language tag for a video stream
>>  in
>>     parallel with an audio stream with the same spoken language tag
>>     indicates a request for a supplemental video stream to see the
>>     speaker.
>>
>>  And there's a similar paragraph in 5.4:
>>
>>>     A spoken language tag for a video stream in conjunction with an
>>  audio
>>>     stream with the same language might indicate a request for
>>>     supplemental video to see the speaker.
>>
>>  I think this mechanism needs to be described more exactly, and in
>>  particular, it should not depend on the UA understanding which
>>  language tags are spoken language tags.  It seems to me that a
>>  workable rule is that there is an audio stream and a video stream and
>>  they specify exactly the same language tag in their respective
>>  humintlang attributes.  In that case, it is a request for a spoken
>>  language with simultaneous video of the speaker, and those requests
>>  should be considered satisfied only if both streams can be
>>  established.
>
> The text you quote has been deleted.  A media stream for supplemental 
> purposes can be negotiated without a language tag, as normal.
>
The text should not be deleted just because it is under discussion.
It is a valid and valuable alternative. At the moment we lack ways to 
indicate if languages are wanted together or seen as separate 
alternatives, and we have said that such detailing can be added in 
future versions or additional specifications if not done now. Therefore 
we had better allow this combination and let the negotiating parties 
sort out what it currently means. The specification just indicates that 
the indicated languages are alternatives, and any number may be selected 
for matching and usage in the session.
I do not think we should require very exactly matching language tags 
between spoken language in audio and corresponding view of the speaker 
in video.
>>
>>  * The following three items are adjustments to the design which I'd
>>  like to know have been considered.
>>
>>  C. "humintlang" seems long to me
>>
>>  Given the excessive length of SDP in practice, it seems to me that a
>>  shorter attribute name would be desirable.  E.g., "humlang" as was
>>  used in some previous versions.  Or is there a coordinated usage with
>>  other names in the "hum*lang" pattern?
>
> There is no intent for a coordinated pattern.  The name was chosen 
> years ago to avoid potential confusion with the 'lang' attribute. Is 
> it worth reopening the issue to potentially save three characters per 
> SDP line with a language?
>
>>
>>  D. Use the Accept-Language syntax
>>
>>  It seems to me that it would better to use the Accept-Language syntax
>>  for the attribute values.  This allows (1) specifiying the quality of
>>  language experience, allowing clear description of bilingualism, (2)
>>  a
>>  unified method of specifying whether or not arbitrary languages are
>>  acceptable, and (3) abbreviating SDP descriptions.
>>
>>  In a way, the fact that the current proposal seems to require (but
>>  does not directly specify) the coordinated absence/presence of an
>>  asterisk on all of the repetitions of humintlang-send or
>>  humintlang-recv is a warning that the syntax doesn't represent the
>>  semantics as well as it might.
>
> The group considered multiple proposals to permit specifying quality, 
> preference, q-values, etc. but decided to keep things simple for this 
> draft.  There is no intent to require the use of an asterisk (to 
> indicate a preference by the caller to not fail the call).  The 
> asterisk is a very mild mechanism with no normative effects.  It 
> merely conveys the preference of the caller, and is not binding on the 
> answerer.
I would never dare to use an sdp without an asterisk. Language matching 
is a tricky thing and human capabilities much wider than the language 
tags can express. If I get a call from a Norwegian user talking 
Norwegian and indicating Norwegian in the humintlang attributes, I want 
to get the call accepted by my device with setting for spoken Swedish, 
because Swedes and Norwegians usually can communicate quite well 
speaking their own languages. I would anyway not have imagined making a 
setting for Norwegian language as a preference in my device.
It will however be an excellent help for me to see the indication of the 
Norwegian, when I get the call, so I can tune my listening.
By setting the asterisk somewhere among the Humintlang attributes, I 
will make sure that I do not lose calls that I could handle.

>
>>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>
>>  Note that all examples are bidirectionally symmetric, and the text
>>  says that requests and responses SHOULD be bidirectionally symmetric.
>>  So it would be a very useful abbreviation to define
>>  "humintlang=<value>" to be equivalent to the combination of
>>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>>
>>  Combining proposals C, D, and E, the examples become
>>
>>        m=audio 49170 RTP/AVP 0
>>        a=humlang:en
>>
>>        m=video 51372 RTP/AVP 31 32
>>        a=humlang:ase,*;q=0.1
>>
>>        m=audio 49250 RTP/AVP 20
>>        a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>>
>>        m=text 45020 RTP/AVP 103 104
>>        a=humlang:gr
>>
>>  which requires about half as many characters as they have now.
>
> A third attribute without the "-send" or "-recv" to indicate 
> bidirectionality would reduce the characters in the SDP block, at the 
> cost of some added complexity (e.g., what if all three appear).  I 
> don't believe this has been discussed in the group.
>
>>  * Editorial comments and nits
>>
>>  Abstract
>>
>>     This document describes the need and a solution using new SDP
>>  stream
>>     attributes.
>>
>>  I don't think the term "stream attribute" is used in RFC 4566.
>>  Instead, it uses "media attribute".
>
> Fixed.
>
>>  1.  Introduction
>>
>>     caller and callee know each other or there is contextual or out of
>>     band information from which the language(s) and media modalities
>>  can
>>
>>  I think this context, it's preferred to hyphenate "out-of-band" to
>>  make it clearly be an adjective.
>
>>  OK.
>
>
>>     This approach has a number of benefits, including that it is
>>  generic
>>     (applies to all interactive communications negotiated using SDP)
>>  and
>>     not limited to emergency calls.
>>
>>  I think s/and not limited to/and is not limited to/ reads more
>>  smoothly.
>
> There's no harm in the extra "is" so I'm happy to add it.
>
>>     But it is clearly useful in many other cases.  For
>>     example, someone calling a company call center or a Public Safety
>>     Answering Point (PSAP) should be able to indicate if one or more
>>     specific signed, written, and/or spoken languages are preferred,
>>  the
>>     callee should be able to indicate its capabilities in this area,
>>  and
>>     the call proceed using in-common language(s) and media forms.
>>
>>  I think s/preferred, the callee/preferred; the callee/ because the
>>  sentence is the concatenation of two sentences.
>
> I reworded the sentence to flow better:
>
>    For example, it is helpful that someone calling a company call center
>    or a Public Safety Answering Point (PSAP) be able to indicate
>    preferred signed, written, and/or spoken languages, the callee be
>    able to indicate its capabilities in this area, and the call proceed
>    using the language(s) and media forms supported by both.
>
>>  Perhaps s/in-common/shared/.
>
> Fixed in the rewording above.
>
>>
>>     Including the user's human (natural) language preferences in the
>>     session establishment negotiation is independent of the use of a
>>     relay service and is transparent to a voice service provider.
>>
>>  I think it's even broader than "transparent to a voice service
>>  provider" -- it's transparent to any serivice provider, assuming that
>>  the media are language-neutral.
>
> I changed it to read "voice or other service provider".
>
>>
>>     In the case of a call to e.g., an airline, the call could be
>>     automatically handled by a Spanish-speaking agent.
>>
>>  I think s/handled by/routed to/ is the usual usage.
>
> We are trying to be careful in the draft to not imply that it is 
> discussing call routing.  I'd rather keep the more generic "handled by".
>
>>
>>  3.  Desired Semantics
>>
>>     The desired solution is a media attribute (preferably per
>>  direction)
>>     that may be used within an offer to indicate the preferred
>>  language
>>     of each (direction of a) media stream, and within an answer to
>>     indicate the accepted language.
>>
>>  In this one instance, I think you want to use "language(s)" to drive
>>  home that that multiple languages can be specified:  "within an offer
>>  to indicate the preferred language(s)".
>>
>>     (Negotiating multiple simultaneous languages within a media stream
>>  is
>>     out of scope, as the complexity of doing so outweighs the
>>     usefulness.)
>>
>>  You might want to say instead "(Negotiating multiple simultaneous
>>  languages within a media stream is out of scope for this document.)"
>>  to ensure that nobody decides to argue whether "the complexity of
>>  doing so outweighs the usefulness".
>
> I agree and deleted "the complexity of doing so outweighs the 
> usefulness".
>
>>
>>  4.  The existing 'lang' attribute
>>
>>     RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>     similar to what is needed here, but is not sufficiently detailed
>>  for
>>     use here.
>>
>>  "for use here" isn't quite right.  Maybe "is not sufficiently
>>  specific
>>  or flexible to satisfy the requirements".
>>
>>     In addition, it is not mentioned in [RFC3264]
>>
>>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>  attribute".
>
> OK, accepted both changes.
>
>>
>>  5.  Proposed Solution
>>
>>  Perhaps /Proposed Solution/Solution/, since once this draft is
>>  approved, it becomes the solution.
>
> OK.
>
>>
>>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>        a=humintlang-send:<language tag>
>>        a=humintlang-recv:<language tag>
>>
>>  This is presented as the generic form of the attributes, but there is
>>  no indication of the posible asterisk.
>
> The syntax has been deleted from 5.2 since it's now in 6.
I think it should not be deleted, but instead Dale's comment satisfied.  
That would be more in line with the stye of rfc4566bis.
5.2 shows the complete attributes, and that is good. Chapter 6 only 
shows the syntax of the value.
>
>>
>>     The values constitute a list of languages
>>     in preference order (first is most preferred).
>>
>>  "The values" isn't very clear, because the values are in successive
>>  attributes.  You want to say something like "The sequence of values
>>  in
>>  the occurrences of one of these attributes constitutes ...".
>>  However,
>>  see the technical comments above.
>
> The text was reworded to read:
>
>    The values from all
>    instances of the attribute constitute a list of languages in
>    preference order (first is most preferred).
>
>
>>
>>     When placing an emergency call, and in any other case where the
>>     language cannot be assumed from context, each media stream in an
>>     offer primarily intended for human language communication SHOULD
>>     specify both (or in some cases, one of) the 'humintlang-send' and
>>     'humintlang-recv' attributes.
>>
>>  Probably s/assumed/inferred/.
>
> I agree.
>
>>
>>  Could you be more accurate by
>>  s/or in some cases/or for unidirectional streams/?
>
> I agree.
>
>>
>>  5.3.  Advisory vs Required
>>
>>     The mechanism for indicating this preference is that, in an offer,
>>  if
>>     the last character of any of the 'humintlang-recv' or 'humintlang-
>>     send' values is an asterisk, this indicates a request to not fail
>>  the
>>     call (similar to SIP Accept-Language syntax).  Either way, the
>>  called
>>     party MAY ignore this, e.g., for the emergency services use case,
>>  a
>>     PSAP will likely not fail the call.
>>
>>  The construction of this paragraph isn't quite complete.  It says
>>  that
>>  if an asterisk is present, a request shouldn't fail, but it doesn't
>>  say that if no asterisk is present, a request should fail if there is
>>  no language match.  And it's the latter condition that makes the
>>  second sentence meaningful.  So I think you want to insert between
>>  the
>>  two sentences one regarding the absence of an asterisk.
>
> I've reworded the section to read:
>
>    A consideration with the ability to negotiate language is if the call
>    proceeds or fails if the callee does not support any of the languages
>    requested by the caller.  This document does not mandate either
>    behavior, although it does provide a way for the caller to indicate a
>    preference for the call succeeding when there is no language in
>    common.  It is OPTIONAL for the callee to honor this preference.  For
>    example, a PSAP is likely to attempt the call even without an
>    indicated preference when there is no language in common, while a
>    call center might choose to fail the call.
>
>    The mechanism for indicating this preference is that, in an offer, if
>    the last character of any of the 'humintlang-recv' or 'humintlang-
>    send' values is an asterisk, this indicates a request to not fail the
>    call.  The called party MAY ignore the indication, e.g., for the
>    emergency services use case, regardless of the absence of an
>    asterisk, a PSAP will likely not fail the call; some call centers
>    might reject a call even with an asterisk.
This still does not meet Dale's comment.
Insert a sentence saying:
"A preference for getting the call denied in case of no language match 
SHOULD be indicated by no asterisk appended on any humintlang attribute 
value in the whole SDP."
>
>>  5.5.  Examples
>>
>>  Given that the combined audio/video mechanism is the only
>>  irregularity
>>  in this system, there ought to be an example of it.  E.g.,
>>
>>     An example of a supplemental video stream with a spoken language
>>     audio stream:
>>
>>        m=video 51372 RTP/AVP 31 32
>>        a=humintlang-send:en
>>        a=humintlang-recv:en
>>
>>        m=audio 49250 RTP/AVP 20
>>        a=humintlang-send:en
>>        a=humintlang-recv:en
>
> If the video stream is supplemental then it doesn't have a language 
> (the text that suggested otherwise has been deleted). But I am 
> considering adding more examples.
I provided a rich set of examples in my LC comments of Feb 13. Please 
consider them as a base even if some need revision if the proposed 
extended meaning of the asterisk is not accepted.
>
>>
>>  6.  IANA Considerations
>>
>>        humintlang-value =  Language-Tag [ asterisk ]
>>                            ; Language-Tag defined in RFC 5646
>>        asterisk         =  "*"
>>
>>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>  5646/
>>
>>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>  tracks the current version of language tags.
>
> Ok.
>
>>
>>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>>
>>     This
>>     results in a more fragile solution since the media modality and
>>     language would be negotiated using SIP, and then the specific
>>  media
>>     formats (which inherently include the modality) would be
>>  negotiated
>>     at a different level (typically SDP, especially in the emergency
>>     calling cases), making it easier to have mismatches (such as where
>>     the media modality negotiated in SIP don't match what was
>>  negotiated
>>     using SDP).
>>
>>  "the media modality and language would be negotiated using SIP" isn't
>>  quite the right way to say it because SIP isn't explicitly
>>  negotiating
>>  the modality.  Better would be
>>
>>     ... the language (and by implication the media modality) would be
>>     negotiated using SIP, and then the specific media (which
>>  inherently
>>     include the modalities and formats) would be negotiated at a
>>     different level ...
>
> This section has been deleted.
Did we agree on that?
>
>>
>>  [END]
>
>
Regards
Gunnar

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 22 04:27:40 2017
Return-Path: <kivinen@iki.fi>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 760371297B8; Wed, 22 Feb 2017 04:27:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1DIHQw5QWMP; Wed, 22 Feb 2017 04:27:37 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72C961297A8; Wed, 22 Feb 2017 04:27:37 -0800 (PST)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.2/8.15.2) with ESMTPS id v1MCRTIA014852 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 22 Feb 2017 14:27:29 +0200 (EET)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.2/8.14.8/Submit) id v1MCRTbo025365; Wed, 22 Feb 2017 14:27:29 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22701.33713.45034.548020@fireball.acr.fi>
Date: Wed, 22 Feb 2017 14:27:29 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
In-Reply-To: <201702151248.v1FCmL5E014275@givry.fdupont.fr>
References: <201702151248.v1FCmL5E014275@givry.fdupont.fr>
X-Mailer: VM 8.2.0b under 25.1.1 (x86_64--netbsd)
X-Edit-Time: 1 min
X-Total-Time: 0 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dWrq3q_YU7LTig50qlKVBuHEBfw>
Cc: draft-kivinen-802-15-ie.all@ietf.org, gen-art@ietf.org
Subject: [Gen-art] review of draft-kivinen-802-15-ie-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 12:27:38 -0000

Francis Dupont writes:
> Nits/editorial comments: 
>  - ToC page 1 and 3 page 3 (title): Benefitting -> Benefiting
> 
>  - 3 page 3 (suggest):  CoRE etc, ->  CoRE, etc,

Fixed.

>  - 4 page 3: reading the document I had a question about the "no need
>   ... to specify the internal structure" but the reason became clear
>   the next page. So I have no concern about this.

That text was rewritten to say:

   Since the 802.15.4 standard defines a list of payload IEs along with
   their structures, there is no need for this document to specify the
   internal structure inside the IETF IE.  The Payload IE format of IEEE
   802.15.4 contains the Length field.  The length of the subtype
   content can be calculated from the IEEE 802.15.4 Payload IE Length
   field of the IETF IE.
-- 
kivinen@iki.fi


From nobody Wed Feb 22 06:22:57 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D997B129986; Wed, 22 Feb 2017 06:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCYO-71jBVXs; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5959F12997F; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id s205so2135208oif.3; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XIgIgtg1qtkUPB8TWXfevsexZSXdwxv+QPqALa22ZRg=; b=eUy4JN3IxHRuelgIFTxIzJzyaNAkOrUwfCe15sY0VLrSmgpt7Z+OD/iEakyuVfbzyY GMXGw+U7saDsFmLsbC79pFRRXlBQBEfDvtX5UErsVwcjIOacmN2r1tOQbH1xniyjFWxH ZcelRg6/09GfUxgf25zgIVK72LHGHPjino2FdZpuUbn/TlU0/fwC95pOLjI2J3Vmgl7T nDDI+Hx1uwIDlMl+5yj0WDIj0HiDcl9L8e2HBXBh+DOxbrDJ6xyPBrhPrfFLGd9rexXk Huf74rw8KMMm4TlMNNNCSabfNdGWIvFnNXggzbUWg5uGDdyBqIIFx/jCEvpgbgz5YpJg cTKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XIgIgtg1qtkUPB8TWXfevsexZSXdwxv+QPqALa22ZRg=; b=r+LYy1CggyaM+G+TZ036N38AEpVcM5Ql5QBq7ldVHTXjRbe1Y36CacxBpDn2tUumY2 7i/coWwO6etH8k9DzLlUSg6hQ3bw3D/f0KTyyjawxRiadVMEnNNcuArAGs2aNuWx/ZIs cPotmM6j+ZdE37IAox6VRN5gOD6Qs/TCf75oVqkV0JtTFHKicnlvavVH5CYnHLu10XxL X2O9R55epHdpaV6zdDPyjZersW+UQyuUa64kT/bEOgzrG8nOO/HfED7JXtHoNj4opMI6 KcpUzTrgU1SjSgXuDXIKRzrfuzh8YzjFWJRBk/KNTz0eTSHnMHPSmzIY0ych/i5y7e+2 7sVg==
X-Gm-Message-State: AMke39lnd+Pr2gg7apyjvGBRy7BVDKb570RHYKWfFRWIwDSsZl/vV+7eAKycZ94WmklQIe5an1SdQ4pOhZvfNA==
X-Received: by 10.202.239.2 with SMTP id n2mr18668278oih.157.1487773368653; Wed, 22 Feb 2017 06:22:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.38.211 with HTTP; Wed, 22 Feb 2017 06:22:48 -0800 (PST)
In-Reply-To: <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com> <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com> <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 22 Feb 2017 06:22:48 -0800
Message-ID: <CA+RyBmV=fCrv7NfbAXZ7VPj2ngX0h-6eO6EwY7h4CiWV8PgrAQ@mail.gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=94eb2c0931da251a7b05491f3b6d
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Gg6ezrZqkZ-D0pjMZjHn8edjkag>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:22:52 -0000

--94eb2c0931da251a7b05491f3b6d
Content-Type: text/plain; charset=UTF-8

Hi Robert,
agreed. Thank you for your thorough review and the most helpful comments.
I'll upload the update shortly.

Regards,
Greg

On Wed, Feb 22, 2017 at 1:09 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

> I would simply delete "To ensure precise accuracy in time determination"
> and start the sentence at "These actions"
>
> RjS
>
> On 2/15/17 9:40 PM, Greg Mirsky wrote:
>
> Hi Robert,
> safe travel and here's another version for your consideration. The point
> I'm trying to convey is that the jitter is real but must be accounted not
> as part of propagation delay but as residence time. Hope I'm getting close.
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface.
>    To ensure precise accuracy in time determination these actions should
>    be done as close to the physical layer as possible at the same point
>    of packet processing striving to avoid introducing the appearance of
>    jitter in propogation delay whereas it should be accounted as
>    residence time.
>
> Regards,
>
> Greg
>
>
> On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> On 2/15/17 11:20 AM, Greg Mirsky wrote:
>>
>> Hi Robert,
>> yes, you've absolutely correct in your example. The importance of RTM is
>> to exclude and quantify, as much as possible, jitter from propagation
>> delay. I've updated the wording to reflect that. Below is new text I
>> propose, please let me know if it makes it clearer.
>>
>>    Each RTM-capable
>>    node on the explicit path receives an RTM packet and records the time
>>    at which it receives that packet at its ingress interface as well as
>>    the time at which it transmits that packet from its egress interface.
>>    These actions should be done as close to the physical layer as
>>    possible at the same point of packet processing striving to avoid
>>    introduction of jitter in propogation delay to ensure precise
>>    accuracy in time determination.
>>
>> perhaps change "avoid introduction of jitter" to "avoid introducing the
>> appearance of jitter that's not really there"?
>>
>> (I'm about to board a plane, so further responses will be very delayed).
>>
>> Regards,
>>
>> Greg
>>
>>
>> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>
>>>
>>>
>>> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>>
>>> Hi Robert,
>>> Section 5 Data Plane Theory of Operation has the following
>>> recommendation on reading time value at ingress and egress:
>>>
>>>    Each RTM-capable
>>>    node on the explicit path receives an RTM packet and records the time
>>>    at which it receives that packet at its ingress interface as well as
>>>    the time at which it transmits that packet from its egress interface;
>>>    this should be done as close to the physical layer as possible to
>>>    ensure precise accuracy in time determination.
>>>
>>> Do you find the text sufficient in providing guidance to an implementer of RTM?
>>>
>>> Well, no - that was point in the text from my review of -12 that caused
>>> me to make comment in the first place.
>>>
>>> What does "precise accuracy" even _MEAN_? You're waving your hands with
>>> words that don't help the reader guess what you mean at the moment. The
>>> subsequent email exchange said the important part was that you measure
>>> _precisely_ (in that the measurements are always taken the same way), but
>>> accuracy isn't that important (you've (and here by "you" I mean the set of
>>> people that have responded to the review") told me it's not important
>>> whether the reading is taken at the beginning of the bit-stream, the end,
>>> or several 1000 nanoseconds after the last bit came off the physical media
>>> as long as it's done the same way for each packet). The fact that you're
>>> carrying a measurement that can talk about times smaller than the
>>> interarrival time for individual bits for some real world line speeds says
>>> that different implementations taking the measurement different ways is
>>> going to result in different residence time measurements, even if the
>>> residence time was really identical. You've told me that's not important to
>>> the protocol using the measurement as long as the an individual
>>> implementation doesn't introduce something that will look to the using
>>> protocol like jitter that's not really there.
>>>
>>> The text does not say that to an implementer right now.
>>>
>>> To restate that long paragraph with maybe a longer one,  assume a
>>> simplified world where everything is perfectly constant. Packets are all
>>> flowing at the same size and same rate. For reference, I assert that the
>>> time between the first bit of a packet entering the system taking the
>>> measurement and the first bit of that packet leaving the system is exactly
>>> T (every time). You are telling me that if the system returns cT for some
>>> constant T other than 1 (and not necessarily  close to 1), everything is
>>> fine. You're also telling me that if you replace the system with another
>>> that preserves T, but measures differently so that it returns c'T where c'
>>> != c, everything is fine. The important part to you is that c and c' don't
>>> change for their respective systems. (That surprises me, I can see how the
>>> way the clocks are going to use this will do the right thing, but I can't
>>> help but think someone later will look at the difference between the two
>>> systems and say something is wrong with one of them). What you've told me
>>> is not fine is that if you drop i a third system that also preserves T but
>>> reports aT where a _varies_ over some range.
>>>
>>> Have I heard you correctly?
>>>
>>> Regards,
>>>
>>> Greg
>>>
>>>
>>> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
>>> wrote:
>>>
>>>> Reviewer: Robert Sparks
>>>> Review result: Ready
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>>> by the IESG for the IETF Chair. Please wait for direction from your
>>>> document shepherd or AD before posting a new version of the draft.
>>>>
>>>> For more information, please see the FAQ at
>>>>
>>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>>
>>>> Document: draft-ietf-mpls-residence-time-13
>>>> Reviewer: Robert Sparks
>>>> Review Date: 2017-02-13
>>>> IETF LC End Date: 2017-01-17
>>>> IESG Telechat date: 2017-03-02
>>>>
>>>> Summary: Ready for publication as PS
>>>>
>>>> Thanks for addressing my comments.
>>>> (I still think some discussion about taking arrival and departure time
>>>> measurements would be helpful, even if it only said "do it
>>>> consistently so you don't indicate jitter that's not really there".)
>>>>
>>>>
>>>
>>>
>>
>>
>
>

--94eb2c0931da251a7b05491f3b6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>agreed. Thank you for your thorough review =
and the most helpful comments. I&#39;ll upload the update shortly.</div><di=
v><br></div><div>Regards,</div><div>Greg</div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, Feb 22, 2017 at 1:09 AM, Robert =
Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=
=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>I would simply delete &quot;To ensure precise accuracy in time
      determination&quot; and start the sentence at &quot;These actions&quo=
t;</p>
    <p>RjS<br>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_-8072473529522433651moz-cite-prefix">On 2/15/17 9:40 PM=
, Greg Mirsky wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <div>safe travel and here&#39;s another version for your
          consideration. The point I&#39;m trying to convey is that the
          jitter is real but must be accounted not as part of
          propagation delay but as residence time. Hope I&#39;m getting
          close.</div>
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Regards,</pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,
          Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@no=
strum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                <p><br>
                </p>
                <br>
                <div class=3D"m_-8072473529522433651m_2800513769154960288mo=
z-cite-prefix">On
                  2/15/17 11:20 AM, Greg Mirsky wrote:<br>
                </div>
              </span>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">Hi Robert, <span>
                    <div>yes, you&#39;ve absolutely correct in your example=
.
                      The importance of RTM is to exclude and quantify,
                      as much as possible, jitter from propagation
                      delay. I&#39;ve updated the wording to reflect that.
                      Below is new text I propose, please let me know if
                      it makes it clearer.</div>
                    <div>
                      <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;w=
hite-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
                    </div>
                  </span></div>
              </blockquote>
              perhaps change &quot;avoid introduction of jitter&quot; to &q=
uot;avoid
              introducing the appearance of jitter that&#39;s not really
              there&quot;?<br>
              <br>
              (I&#39;m about to board a plane, so further responses will be
              very delayed). <br>
              <div>
                <div class=3D"m_-8072473529522433651h5">
                  <blockquote type=3D"cite">
                    <div dir=3D"ltr">
                      <div>
                        <pre style=3D"color:rgb(0,0,0);word-wrap:break-word=
;white-space:pre-wrap">Regards,</pre>
                        <pre style=3D"color:rgb(0,0,0);word-wrap:break-word=
;white-space:pre-wrap">Greg</pre>
                      </div>
                    </div>
                    <div class=3D"gmail_extra"><br>
                      <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at
                        7:43 AM, Robert Sparks <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a=
>&gt;</span>
                        wrote:<br>
                        <blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                          <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                              <p><br>
                              </p>
                              <br>
                              <div class=3D"m_-8072473529522433651m_2800513=
769154960288m_3072934530585377958moz-cite-prefix">On
                                2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                              </div>
                              <blockquote type=3D"cite">
                                <div dir=3D"ltr">Hi Robert,
                                  <div>Section 5 Data Plane Theory of
                                    Operation has the following
                                    recommendation on reading time value
                                    at ingress and egress:</div>
                                  <div>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capa=
ble
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the =
text sufficient in providing guidance to an implementer of RTM?</pre>
                                  </div>
                                </div>
                              </blockquote>
                            </span> Well, no - that was point in the
                            text from my review of -12 that caused me to
                            make comment in the first place.<br>
                            <br>
                            What does &quot;precise accuracy&quot; even _ME=
AN_?
                            You&#39;re waving your hands with words that
                            don&#39;t help the reader guess what you mean a=
t
                            the moment. The subsequent email exchange
                            said the important part was that you measure
                            _precisely_ (in that the measurements are
                            always taken the same way), but accuracy
                            isn&#39;t that important (you&#39;ve (and here =
by
                            &quot;you&quot; I mean the set of people that h=
ave
                            responded to the review&quot;) told me it&#39;s=
 not
                            important whether the reading is taken at
                            the beginning of the bit-stream, the end, or
                            several 1000 nanoseconds after the last bit
                            came off the physical media as long as it&#39;s
                            done the same way for each packet). The fact
                            that you&#39;re carrying a measurement that can
                            talk about times smaller than the
                            interarrival time for individual bits for
                            some real world line speeds says that
                            different implementations taking the
                            measurement different ways is going to
                            result in different residence time
                            measurements, even if the residence time was
                            really identical. You&#39;ve told me that&#39;s=
 not
                            important to the protocol using the
                            measurement as long as the an individual
                            implementation doesn&#39;t introduce something
                            that will look to the using protocol like
                            jitter that&#39;s not really there.<br>
                            <br>
                            The text does not say that to an implementer
                            right now.<br>
                            <br>
                            To restate that long paragraph with maybe a
                            longer one,=C2=A0 assume a simplified world whe=
re
                            everything is perfectly constant. Packets
                            are all flowing at the same size and same
                            rate. For reference, I assert that the time
                            between the first bit of a packet entering
                            the system taking the measurement and the
                            first bit of that packet leaving the system
                            is exactly T (every time). You are telling
                            me that if the system returns cT for some
                            constant T other than 1 (and not
                            necessarily=C2=A0 close to 1), everything is
                            fine. You&#39;re also telling me that if you
                            replace the system with another that
                            preserves T, but measures differently so
                            that it returns c&#39;T where c&#39; !=3D c,
                            everything is fine. The important part to
                            you is that c and c&#39; don&#39;t change for t=
heir
                            respective systems. (That surprises me, I
                            can see how the way the clocks are going to
                            use this will do the right thing, but I
                            can&#39;t help but think someone later will loo=
k
                            at the difference between the two systems
                            and say something is wrong with one of
                            them). What you&#39;ve told me is not fine is
                            that if you drop i a third system that also
                            preserves T but reports aT where a _varies_
                            over some range.<br>
                            <br>
                            Have I heard you correctly?<span><br>
                              <blockquote type=3D"cite">
                                <div dir=3D"ltr">
                                  <div>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                                  </div>
                                </div>
                                <div class=3D"gmail_extra"><br>
                                  <div class=3D"gmail_quote">On Mon, Feb
                                    13, 2017 at 1:51 PM, Robert Sparks <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank"=
>rjsparks@nostrum.com</a>&gt;</span>
                                    wrote:<br>
                                    <blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer=
:
                                      Robert Sparks<br>
                                      Review result: Ready<br>
                                      <br>
                                      I am the assigned Gen-ART reviewer
                                      for this draft. The General Area<br>
                                      Review Team (Gen-ART) reviews all
                                      IETF documents being processed<br>
                                      by the IESG for the IETF Chair.
                                      Please wait for direction from
                                      your<br>
                                      document shepherd or AD before
                                      posting a new version of the
                                      draft.<br>
                                      <br>
                                      For more information, please see
                                      the FAQ at<br>
                                      <br>
                                      &lt;<a href=3D"https://trac.ietf.org/=
trac/gen/wiki/GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.=
ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                                      <br>
                                      Document:
                                      draft-ietf-mpls-residence-time<wbr>-1=
3<br>
                                      Reviewer: Robert Sparks<br>
                                      Review Date: 2017-02-13<br>
                                      IETF LC End Date: 2017-01-17<br>
                                      IESG Telechat date: 2017-03-02<br>
                                      <br>
                                      Summary: Ready for publication as
                                      PS<br>
                                      <br>
                                      Thanks for addressing my comments.<br=
>
                                      (I still think some discussion
                                      about taking arrival and departure
                                      time<br>
                                      measurements would be helpful,
                                      even if it only said &quot;do it<br>
                                      consistently so you don&#39;t indicat=
e
                                      jitter that&#39;s not really there&qu=
ot;.)<br>
                                      <br>
                                    </blockquote>
                                  </div>
                                  <br>
                                </div>
                              </blockquote>
                              <br>
                            </span></div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div>

--94eb2c0931da251a7b05491f3b6d--


From nobody Wed Feb 22 11:10:24 2017
Return-Path: <vainshtein.alex@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11F4129979; Wed, 22 Feb 2017 06:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjGIyMYviCCH; Wed, 22 Feb 2017 06:29:04 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EAF0129971; Wed, 22 Feb 2017 06:29:04 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id 203so2375212ith.0; Wed, 22 Feb 2017 06:29:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QQoFTq3bM1daZ4ZftKifk9CtG9JK72p3PZ/XWrG2YJw=; b=PJNL6w7MO3RT7+p5466enyH9baTjcbJTzV/l/UhonuJDzSGMeEK+F9KgGiUv8K4Oc0 HHXuEO8bpdFlThC/15abpr8eMQ/y2S+SgxUWOi5KSgE0sP/7Hg2QVSgiPX78sRX5I3cq vDHPDe3KX3zBGaHcyiVrZfUHpka0GrS6LybrDAw5XpQnwDS8AUrGIJoV6EM7j6XgqkvK HKuwwksSOUKlgjUSqw0ZG1tvqpBjrdbvNAQWbsXT6S9IFRC+aoNtsiPYXh/UiZfVrwQ2 VRLlp+VOzo48e5nICsR6A3pvy3pylWPxYNGtIlrLafkMyA2y8n0eiPoSlS+elIAjQdFa TlNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QQoFTq3bM1daZ4ZftKifk9CtG9JK72p3PZ/XWrG2YJw=; b=PVGWkGExKchpsV+BjqipyGn/u0Kf3Y0lFQLoXd492VAOz26IXuGuN6OMcpW2CZ2a4M FN5xgn966eTYyiuOnsWfqtsJ6fOe7TSLox4DhI4ddCY6gZwfciKe6rdB5ksxaxJTI9a0 bUWuVkSc5OptQV0e07bp/X+yWaCxErkvAMHv53OPdEaZY6B15GZENO3VsewyTjkOMtgs SYjYUiaDGVMvXyyuEOKCGW/WfXTK+oTE7w3CTGSvgT/SKVjTqTiCCySfeKgrJTZTI66g giEQ+oTeZXsrUpPUkalxr7y12U576o+9rCHQg/ce2PQetQuoRQrvhNqaq/K0zXeAWrNz 1Huw==
X-Gm-Message-State: AMke39nCU3/bINyhttUuMGdemY2/aAIaWObK3C9YM/GaAbA6E2HRvSYpwMHc3+gerpPQmPeadf7aIU1Xupa/UQ==
X-Received: by 10.36.111.82 with SMTP id x79mr2207924itb.1.1487773743547; Wed, 22 Feb 2017 06:29:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.24.199 with HTTP; Wed, 22 Feb 2017 06:29:02 -0800 (PST)
Received: by 10.79.24.199 with HTTP; Wed, 22 Feb 2017 06:29:02 -0800 (PST)
In-Reply-To: <CA+RyBmV=fCrv7NfbAXZ7VPj2ngX0h-6eO6EwY7h4CiWV8PgrAQ@mail.gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com> <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com> <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com> <CA+RyBmV=fCrv7NfbAXZ7VPj2ngX0h-6eO6EwY7h4CiWV8PgrAQ@mail.gmail.com>
From: Alexander Vainshtein <vainshtein.alex@gmail.com>
Date: Wed, 22 Feb 2017 16:29:02 +0200
Message-ID: <CAA+i7Sts9XEPayyXvcV0jstX_zUohuFUdpDVSh8+gTBY_-59Tw@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Content-Type: multipart/alternative; boundary=001a11444e527d8c2505491f5107
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/IWe3dfjQ4kFzmxofwZB2fQmvBT0>
X-Mailman-Approved-At: Wed, 22 Feb 2017 11:10:23 -0800
Cc: mpls@ietf.org, gen-art@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-mpls-residence-time-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:29:06 -0000

--001a11444e527d8c2505491f5107
Content-Type: text/plain; charset=UTF-8

My thanks as well - to Robert for a most careful review and to Greg for
handling the draft for all these years.

Regards,
Sasha

On Feb 22, 2017 16:22, "Greg Mirsky" <gregimirsky@gmail.com> wrote:

> Hi Robert,
> agreed. Thank you for your thorough review and the most helpful comments.
> I'll upload the update shortly.
>
> Regards,
> Greg
>
> On Wed, Feb 22, 2017 at 1:09 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>> I would simply delete "To ensure precise accuracy in time determination"
>> and start the sentence at "These actions"
>>
>> RjS
>>
>> On 2/15/17 9:40 PM, Greg Mirsky wrote:
>>
>> Hi Robert,
>> safe travel and here's another version for your consideration. The point
>> I'm trying to convey is that the jitter is real but must be accounted not
>> as part of propagation delay but as residence time. Hope I'm getting close.
>>
>>    Each RTM-capable
>>    node on the explicit path receives an RTM packet and records the time
>>    at which it receives that packet at its ingress interface as well as
>>    the time at which it transmits that packet from its egress interface.
>>    To ensure precise accuracy in time determination these actions should
>>    be done as close to the physical layer as possible at the same point
>>    of packet processing striving to avoid introducing the appearance of
>>    jitter in propogation delay whereas it should be accounted as
>>    residence time.
>>
>> Regards,
>>
>> Greg
>>
>>
>> On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>
>>>
>>>
>>> On 2/15/17 11:20 AM, Greg Mirsky wrote:
>>>
>>> Hi Robert,
>>> yes, you've absolutely correct in your example
>>>
>>>

--001a11444e527d8c2505491f5107
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">My thanks as well - to Robert for a most careful review a=
nd to Greg for handling the draft for all these years.<div dir=3D"auto"><br=
></div><div dir=3D"auto">Regards,</div><div dir=3D"auto">Sasha</div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Feb 22, 2017 16=
:22, &quot;Greg Mirsky&quot; &lt;<a href=3D"mailto:gregimirsky@gmail.com">g=
regimirsky@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"ltr">Hi Robert,<div>agreed. Thank you for your =
thorough review and the most helpful comments. I&#39;ll upload the update s=
hortly.</div><div><br></div><div>Regards,</div><div>Greg</div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 22, 2017 at =
1:09 AM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nos=
trum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>I would simply delete &quot;To ensure precise accuracy in time
      determination&quot; and start the sentence at &quot;These actions&quo=
t;</p>
    <p>RjS<br>
    </p><div><div class=3D"m_557604467699402152h5">
    <br>
    <div class=3D"m_557604467699402152m_-8072473529522433651moz-cite-prefix=
">On 2/15/17 9:40 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <div>safe travel and here&#39;s another version for your
          consideration. The point I&#39;m trying to convey is that the
          jitter is real but must be accounted not as part of
          propagation delay but as residence time. Hope I&#39;m getting
          close.</div>
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Regards,</pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,
          Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@no=
strum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                <p><br>
                </p>
                <br>
                <div class=3D"m_557604467699402152m_-8072473529522433651m_2=
800513769154960288moz-cite-prefix">On
                  2/15/17 11:20 AM, Greg Mirsky wrote:<br>
                </div>
              </span>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">Hi Robert, <span>
                    <div>yes, you&#39;ve absolutely correct in your example=
</div></span></div></blockquote></div></blockquote></div></div></blockquote=
></div></div></div></blockquote></div></div></blockquote></div></div>

--001a11444e527d8c2505491f5107--


From nobody Wed Feb 22 11:43:31 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8843129A9C; Wed, 22 Feb 2017 11:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQO_8e2Z3MiO; Wed, 22 Feb 2017 11:43:28 -0800 (PST)
Received: from mail-qt0-x241.google.com (mail-qt0-x241.google.com [IPv6:2607:f8b0:400d:c0d::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0879129A8C; Wed, 22 Feb 2017 11:43:27 -0800 (PST)
Received: by mail-qt0-x241.google.com with SMTP id n37so1734129qtb.3; Wed, 22 Feb 2017 11:43:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ucg93RuzextUSplVXVB3LOWk8nxf4CxGOJSZI35ZurA=; b=Z73qHvT56BSVBe7TsZE/fef9yk1zjzSb6ediyq+62xafU4rbxkU7bLMWcExt95xY5F 5HEMIoIRDAXeVoCWrSFiUHrGjGYwdVq50R7N1T9QbtX0jYeNmZX7FYTp4R3wz2bP1pts v3T8A3aZYY6sl9URFdOgLAteLIenkOslNyddKeRnfX5WeuO8s0YM3fWtC9bJ6SIIaBoW xLWbZhzKPIl+1GXwCMiYcj9kWTOfg+BvbXMdby6WOQHEsH2s8qpQE/H3EueIi3n5BIu8 BSjM974bT4UAlDyzPuf2UZNChp4m40G3sh5Z+UQFssnIMtFN6GZMHY1+eJwjY0IaSUD0 yJFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ucg93RuzextUSplVXVB3LOWk8nxf4CxGOJSZI35ZurA=; b=k4N0v4MmdaccLPyOUEs2SEEvK6LviXCeZwC5FdEdYT5BKwAu3DgIBHx3YfTNIoqdE8 LwgPVLiOFKCaqodWHOdgviMR+W8q2cHVvwAzR6MIlrwTAPLxsJYeAEEIc8ayFFe8NAku 6Mp1EhZ309wmVfSAIli0BzhOv895VNtlWiLQvFOWZ1nf5DGyVriIKwA50Kdys9YBG0/n QSSjYFhhrDcQpQESmNZ4D6gkV6FgkfaiNZg/RmDtObGVf5UUqNskyTfawvQyAXS4UzWy ///VsGQXcvkAQxAJ9M3KdyV5cIzllMVumyqYIBCdPGaoEuqE1AtMfK1jp16AwpXF/Byw 10tQ==
X-Gm-Message-State: AMke39npZYz8y8eOT5vtDX1thcxSacCOudaq7IqsoJkl/kUn8vL68EslHOHn4PWXMZHRyg==
X-Received: by 10.200.41.98 with SMTP id z31mr15910476qtz.116.1487792606756; Wed, 22 Feb 2017 11:43:26 -0800 (PST)
Received: from [192.168.89.94] ([216.31.219.19]) by smtp.gmail.com with ESMTPSA id g54sm452308qta.30.2017.02.22.11.43.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2017 11:43:25 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: "jouni.nospam" <jouni.nospam@gmail.com>
In-Reply-To: <1540716911.2617277.1487700770759@mail.yahoo.com>
Date: Wed, 22 Feb 2017 11:43:23 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB8B626F-9AF1-47D8-B118-991F28BD00C8@gmail.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com> <100465536.2630141.1487699983875@mail.yahoo.com> <685542803.2622890.1487700213971@mail.yahoo.com> <1540716911.2617277.1487700770759@mail.yahoo.com>
To: nalini.elkins@insidethestack.com
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/q1duldZG01uAAZD-COHAbjV_pfA>
Cc: Robert Hamilton <rhamilton@cas.org>, "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "MORTON ALFRED C \(AL\)" <acmorton@att.com>, Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 19:43:31 -0000

Hi,

I=E2=80=99ll have a review of the changes shortly. Just wanted to =
acknowledge I=E2=80=99ve seen this mail ;)

Thanks,
	Jouni



> On Feb 21, 2017, at 10:12 AM, nalini.elkins@insidethestack.com wrote:
>=20
> I don't know why this email keeps getting cut off!
>=20
> I am attaching my response in a text file.
>=20
> Sigh.
> =20
> Thanks,
>=20
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>=20
>=20
>=20
> ----- Forwarded Message -----
> From: "nalini.elkins@insidethestack.com" =
<nalini.elkins@insidethestack.com>
> To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team =
<gen-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" =
<draft-ietf-ippm-6man-pdm-option.all@ietf.org>=20
> Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton =
<rhamilton@cas.org>; MORTON ALFRED C (AL) <acmorton@att.com>
> Sent: Tuesday, February 21, 2017 10:03 AM
> Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server =
Time
>=20
> Resending.  Somehow the last email was cut off.
> =20
> Nalini=20
>=20
> From: "nalini.elkins@insidethestack.com" =
<nalini.elkins@insidethestack.com>
> To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team =
<gen-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" =
<draft-ietf-ippm-6man-pdm-option.all@ietf.org>=20
> Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton =
<rhamilton@cas.org>; MORTON ALFRED C (AL) <acmorton@att.com>
> Sent: Tuesday, February 21, 2017 9:59 AM
> Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server =
Time
>=20
> Jouni,
>=20
> Here is the thread for your second major comment:
>=20
> Major comment #2 from you:
>=20
> >2) The PDM option relation to actual "server" time is somewhat =
confusing and the 5-tuple does not allow me to detect the real =
relationship between the >server/application action that caused the =
generation of the packet and the PDM within the packet. This is =
specifically an issue with transport/application protocols >that =
multiplex/interleave multiple application streams into one transport. I =
have no idea of the actual individual application time since the packets =
get generated >independent of the processing of a single thread. I would =
welcome some discussion around here. Section 1.4 last paragraph is going =
to this direction but is not >sufficient IMHO.
>=20
> Yes, you are, of course, correct that all traffic will flow between =
the matching ports at the two endpoints. The 5-tuples will match =
regardless of the application.
>=20
> The thing is that we never intended that PDM would distinguish between =
applications using the same 5-tuple.  That is, it is a feature, not a =
bug.
>=20
> What PDM WILL tell you is whether the problem is in the network or the =
host.    In our experience, which is primarily on networks for large =
data centers, there is a different group which is involved to =
troubleshoot the problem depending on the nature of the problem.  That =
is, do I get the application developers on the line or the team that =
deals with the routers & infrastructure.
>=20
> One of the important functions of PDM is to allow you to do quick =
triage so that you can get the right SWAT team going.   PDM does not =
tell you if the problem is in the IP stack or the application or buffer =
allocation.   PDM also does not tell you which of the network segments =
or middle boxes is at fault.  The reason for PDM is to get the right =
specialists in place who can then be dispatched to investigate their =
area.
>=20
> In our experience, valuable time is often lost at this first stage of =
triage.   Both the network group and the application group have quite a =
few specialized tools at their disposal to further investigate their own =
areas.
>=20
> I am adding some of this verbiage to section 1.4.   Please see below:
>=20
> CURRENT
> -----------
>=20
> 1.4 Rationale for defined solution=20
>=20
> The current IPv6 specification does not provide timing nor a similar=20=

> field in the IPv6 main header or in any extension header. So, we=20
> define the IPv6 Performance and Diagnostic Metrics destination option=20=

> (PDM).=20
>=20
> Advantages include:=20
>=20
> 1. Real measure of actual transactions.=20
> 2. Independence from transport layer protocols.=20
> 3. Ability to span organizational boundaries with consistent=20
> instrumentation=20
> 4. No time synchronization needed between session partners=20
> 5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
> in a uniform way=20
>=20
> The PDM provides the ability to determine quickly if the (latency)=20
> problem is in the network or in the server (application). More=20
> intermediate measurements may be needed if the host or network=20
> discrimination is not sufficient. At the client, TCP/IP stack time=20
> vs. application time may still need to be broken out by client=20
> software.=20
>=20
>=20
> NEW
> ----
>=20
> 1.4 Rationale for defined solution=20
>=20
> The current IPv6 specification does not provide timing nor a similar=20=

> field in the IPv6 main header or in any extension header. So, we=20
> define the IPv6 Performance and Diagnostic Metrics destination option=20=

> (PDM).=20
>=20
> Advantages include:=20
>=20
> 1. Real measure of actual transactions.=20
> 2. Independence from transport layer protocols.=20
> 3. Ability to span organizational boundaries with consistent=20
> instrumentation=20
> 4. No time synchronization needed between session partners=20
> 5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
> in a uniform way=20
>=20
> The PDM provides the ability to determine quickly if the (latency)=20
> problem is in the network or in the server (application).  That is,
> it is a fast way to do triage.
>=20
> One of the important functions of PDM is to allow you to do quickly =
dispatch
> the right set of diagnosticians.  Within network or server latency,
> there may be many components.  The job of the diagnostician is to rule
> each one out until the culprit is found.
>=20
> How PDM fits into this diagnostic picture is that PDM will quickly =
tell=20
> you how to escalate.  PDM will point to either the network area or the
> server area.   Within the server latency, PDM does not tell you if the =
bottleneck
> is in the IP stack or the application or buffer allocation. Within the =
network latency,=20
> PDM does not tell you which of the network segments or middle boxes is =
at fault.=20
>=20
> What PDM will tell you is whether the problem is in the network or the =
server. In our experience,=20
> there is often a different group which is involved to troubleshoot the =
problem depending on the=20
> nature of the problem.   That is, the problem may be escalated to the =
application developers
> or the team that deals with the routers and infrastructure.  Both the =
network group and the=20
> application group have quite a few specialized tools at their disposal =
to further investigate their
> own areas.   What is missing is the first step, which PDM provides.
>=20
> In our experience, valuable time is often lost at this first stage of =
triage.  PDM is expected to
> reduce this time substantially.=20
> =20
> Thanks,
>=20
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>=20
> ________________________________
>=20
> From: jouni korhonen <jouni.nospam@gmail.com>
> To: General Area Review Team <gen-art@ietf.org>; =
draft-ietf-ippm-6man-pdm-option.all@ietf.org=20
> Sent: Friday, September 23, 2016 11:14 AM
> Subject: Gen-ART review of
>=20
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-ippm-6man-pdm-option-05
> Reviewer: Jouni Korhonen
> Review Date: 9/23/2016
> IETF LC End Date: 2016-09-28
> IESG Telechat date: (if known)
>=20
> Summary: The draft needs some work.
>=20
> Major issues:
>=20
>=20
> I have two technical issues here:
>=20
>=20
> 1) There is no mention of what is the time reference plane for =
internal time stamping. All other timing and synchronization related =
documents I am aware of (at least outside IETF) describe it very clearly =
where in the processing/packet handling the time stamp is to be taken. =
Now the document gives me no idea as an implementer where that should =
take place. At least it makes it hard to calculate the *network* RTT =
precisely.
>=20
>=20
> 2) The PDM option relation to actual "server" time is somewhat =
confusing and the 5-tuple does not allow me to detect the real =
relationship between the server/application action that caused the =
generation of the packet and the PDM within the packet. This is =
specifically an issue with transport/application protocols that =
multiplex/interleave multiple application streams into one transport. I =
have no idea of the actual individual application time since the packets =
get generated independent of the processing of a single thread. I would =
welcome some discussion around here. Section 1.4 last paragraph is going =
to this direction but is not sufficient IMHO.
>=20
>=20
> Minor issues:
>=20
>=20
> 1) This is a larger editorial issue. The document is far too long with =
a lot of repetition considering it describes only one IPv6 destination =
option. It is a writing style issue and I am fully aware of that. I have =
proposals how to cut text in the editorial comments section.
>=20
>=20
> 2) Section 1.2 3rd paragraph talks about IoT and that speed matters =
there. I find this too generalized statement. There are many other =
things that matter in this application domain and speed might not be =
that important as being able to send/receive that one to two bytes of =
data in a given time window. I suggest removing this paragraph.
>=20
>=20
> Nits/editorial comments:
>=20
>=20
> 1) Section 1.4 numbered list: add missing full stops.
>=20
>=20
> 2) Section 3.2: remove
>   "The 5-tuple consists of
>    the source and destination IP addresses, the source and destination
>    ports, and the upper layer protocol (ex. TCP, ICMP, etc)."
>=20
> since this is unnecessary repetition.
>=20
> 3) Section 3.2: remove
>   "Operating systems MUST NOT implement a single
>    counter for all connections."
>=20
> Seems again like unnecessary repetition to previous sentence.
>=20
>=20
> 4) Section 3.2 again unnecessary repetition of IPv6 basics that can be =
read from RFC2460. Suggest strongly to remove:
>   "This indicates the
>    following processing requirements:
>=20
>    00 - skip over this option and continue processing the header.
>=20
>    RFC2460 [RFC2460] defines other values for the Option Type field.
>    These MUST NOT be used in the PDM."
>=20
>=20
> and
>=20
>   "The
>    possible values are as follows:
>=20
>    0 - Option Data does not change en-route
>=20
>    1 - Option Data may change en-route
>=20
>    The three high-order bits described above are to be treated as part
>    of the Option Type, not independent of the Option Type.  That is, a
>    particular option is identified by a full 8-bit Option Type, not =
just
>    the low-order 5 bits of an Option Type."
>=20
>=20
> 5) Section 3.3 same as in comment 4). Suggest strongly removing:
>   "This follows the order defined in RFC2460 [RFC2460]
>                  IPv6 header
>=20
>                  Hop-by-Hop Options header
>=20
>                  Destination Options header  <--------
>=20
>                  Routing header
>=20
>                  Fragment header
>=20
>                  Authentication header
>=20
>                  Encapsulating Security Payload header
>=20
>                  Destination Options header <------------
>=20
>                  upper-layer header"
>=20
>=20
> 6) Suggest removing entire Section 3.4 and moving the following text =
to Section 3.3:
>   "PDM MUST be placed before the ESP header in
>    order to work.  If placed before the ESP header, the PDM header =
will
>    flow in the clear over the network thus allowing gathering of
>    performance and diagnostic data without sacrificing security."
>=20
>=20
> 7) Section 3.6 suggest removing the following text. I see no value it =
would add to what has already been said:
>   "As with all other destination options extension headers, the PDM is
>    for destination nodes only. As specified above, intermediate =
devices
>    MUST neither set nor modify this field."
>=20
>=20
> 8) Section 3.6 suggest removing the following 5-tuple text as it has =
already been described earlier in Section 2:
>   "The 5-tuple is:
>=20
>    SADDR : IP address of the sender SPORT : Port for sender DADDR : IP
>    address of the destination DPORT : Port for destination PROTC :
>    Protocol for upper layer (ex. TCP, UDP, ICMP)"
>=20
>=20
> 9) Sections 4.2 and 4.3 suggest removing them entirely. I see what =
value these sections add. I acknowledge they are good to know =
information of timer hardware implementation difference but do not =
really add value on the on-wire encoding of the PDM option.
>=20
>=20
> 10) Section 4.4 suggest removing the entire section. Time Base was =
already described in detail enough in Section 3.2.
>=20
>=20
> 11) Section 4.5 time base for picoseconds is 11 not 00.
>=20
>=20
> 12) Section 4.5 suggest removing the following text, since it does not =
add any more clarity to what has already been said in my opinion. This =
is because all the examples follow nice nybble increment in scaling:
>   "Sample binary values (high order 16 bits taken)
>=20
>    1 psec            1                                              =
0001
>    1 nsec          3E8                                    0011 1110 =
1000
>    1 usec        F4240                          1111 0100 0010 0100 =
0000
>    1 msec     3B9ACA00           0011 1011 1001 1010 1100 1010 0000 =
0000
>    1 sec    E8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 =
0000"
>=20
>=20
> 12) Section 4.6 I do not understand why this section is here. I =
strongly suggest removing it. Sections 4.5 and 3.2 already describe how =
I would encode the delta time using scaling as a separate fields not =
embedded (option fields ScaleDTLR and ScaleDTLS). Did I misunderstand =
something here?
>=20
>=20
> 13) Section 5 suggest removing the following text because of it =
repeating what has already been said earlier:
>   "Each packet, in addition to the PDM contains information on the
>    sender and receiver. As discussed before, a 5-tuple consists of:
>=20
>       SADDR : IP address of the sender
>       SPORT : Port for sender
>       DADDR : IP address of the destination
>       DPORT : Port for destination
>       PROTC : Protocol for upper layer (ex. TCP, UDP, ICMP)
>=20
>    It should be understood that the packet identification information =
is
>    in each packet. We will not repeat that in each of the following
>    steps."
>=20
>=20
> 14) Section 5.3 suggest merging the following text into one example =
and do necessary rewording. There is no need to do the same calculation =
twice on almost adjacent lines:
>=20
>   "Sending time : packet 2 - receive time : packet 1
>=20
>    We will call the result of this calculation: Delta Time Last =
Received
>    (DELTATLR)
>=20
>    That is:
>=20
>    Delta Time Last Received =3D (Sending time: packet 2 - receive =
time:
>    packet 1)"
>=20
>=20
> 15) Expand RTT and PSN on their first use.
>=20
>=20
> Phew.. after all this I found the document good reading and most =
likely a useful tool to be used.
>=20
>=20
> Regards,
>=20
>    Jouni
>=20
>=20
>=20
>=20
> <serverTimeComments.txt>


From nobody Wed Feb 22 12:03:51 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D370E129AC7 for <gen-art@ietfa.amsl.com>; Wed, 22 Feb 2017 12:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WNGKZPo3-iZ for <gen-art@ietfa.amsl.com>; Wed, 22 Feb 2017 12:03:40 -0800 (PST)
Received: from nm5-vm10.bullet.mail.gq1.yahoo.com (nm5-vm10.bullet.mail.gq1.yahoo.com [98.136.218.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FA37129ADB for <gen-art@ietf.org>; Wed, 22 Feb 2017 12:03:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487793820; bh=B7KhyD9fwZVw+y4MKQRLmbvFJqsgBgvt+jxir7Jn9Fo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=YxorUb4GzBoMsw2J5Ds+/FqrzMVn6c2RWxh5XslAZvmI5zZgVAuZk/aZBjtGJCJw/sALVnMtJa0PkdTqW0SOyXvE3K+4+RvnZqF0X1e/Qc+fnJRJvBVRz0C2DO5PczlNJV5zg6NfDQSB4nzw2liXxDmhy+NF/jUIF4CamZORuz7P7DBBmMc4BXPdkcdEZmomYAhe9ZQaRS3/SQcuLXfMaZ3uhkWM/yAUOLElknmVf2OC+YT+kLARXLIhVzBlDxwRq+rnKYgWNA0r9fe5pr46DIKIphPcYycAePaokus501ihY0XeWh9slfIE42W8RET+vYaiYFiWJlUsvI5oPY6n8g==
Received: from [216.39.60.180] by nm5.bullet.mail.gq1.yahoo.com with NNFMP; 22 Feb 2017 20:03:40 -0000
Received: from [98.137.12.204] by tm16.bullet.mail.gq1.yahoo.com with NNFMP; 22 Feb 2017 20:03:39 -0000
Received: from [127.0.0.1] by omp1012.mail.gq1.yahoo.com with NNFMP; 22 Feb 2017 20:03:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 842170.85625.bm@omp1012.mail.gq1.yahoo.com
X-YMail-OSG: kxh34fEVM1k_a_7jOe7VU1cfLBiqpS02np..r1EPoEJpOre7jfB.C1S0nDLivWf S9NXnYWx6NcgKO22PnFrHF9Pa3.uOArYSFIog48mDdhXLIBFRwM5n2Mb3EJCe23nVloGdM9zGP6A kcsWr6kD3Ccj90y1Es6DP6oNnZNT39ujZL7g9gtfKlGSJd0AQhQZDz3XfvKkvnKo5nCUvlWRYcPi Sy7F00V351nw132cWQnHFPgZ.vkQVOQ7iFzEdBZ8lkhHWMh4HhCEGXix8gZ3jnS7.ItnZoYVkn85 og3yiUrzI5Lg2m0GhpTSVAOGBXuThbh7bBO5Kf9ye8sFGvDK_xOV0_F4chUMhAEzRUb4Vz32.AyX LcL2cFmAZICDEKTE0lZ7NLf25EfMYd7bP0k7YAKR0MjmWutY5kIfWOmbZdUidA0lDo543jT325nO aTE8CJG2PI_IvH_nf7DoChZmh6EPL4NqPthxsgfXAwurfxNk.Uj6AF2vWAAq2Km25xzZStMV2dx5 1nYOzKhVdkji0O2ZT0K1OZrwiFkQdSHAx7L3_84yCpoG.J87QTUo-
Received: from jws300072.mail.gq1.yahoo.com by sendmailws138.mail.gq1.yahoo.com; Wed, 22 Feb 2017 20:03:38 +0000; 1487793818.876
Date: Wed, 22 Feb 2017 20:03:34 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: "jouni.nospam" <jouni.nospam@gmail.com>
Message-ID: <1879525019.3881740.1487793814509@mail.yahoo.com>
In-Reply-To: <BB8B626F-9AF1-47D8-B118-991F28BD00C8@gmail.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com> <100465536.2630141.1487699983875@mail.yahoo.com> <685542803.2622890.1487700213971@mail.yahoo.com> <1540716911.2617277.1487700770759@mail.yahoo.com> <BB8B626F-9AF1-47D8-B118-991F28BD00C8@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Fm3haM2f6HSzU3anXtNwaDbjEL4>
Cc: Robert Hamilton <rhamilton@cas.org>, "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "MORTON ALFRED C \(AL\)" <acmorton@att.com>, Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:03:43 -0000

Thanks!

There is one before this for the other major question.

Also, I am working on the minor changes & "wordiness" of the document.  Spe=
ncer had a great idea to move some more things into an Appendix.  So, have =
done that.

Should have that cleaned up in a day or two.

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


----- Original Message -----
From: jouni.nospam <jouni.nospam@gmail.com>
To: nalini.elkins@insidethestack.com
Cc: General Area Review Team <gen-art@ietf.org>; "draft-ietf-ippm-6man-pdm-=
option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>; Michae=
l Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@cas.org>; MO=
RTON ALFRED C (AL) <acmorton@att.com>
Sent: Wednesday, February 22, 2017 11:43 AM
Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option:  Server Tim=
e

Hi,

I=E2=80=99ll have a review of the changes shortly. Just wanted to acknowled=
ge I=E2=80=99ve seen this mail ;)

Thanks,
    Jouni



> On Feb 21, 2017, at 10:12 AM, nalini.elkins@insidethestack.com wrote:
>=20
> I don't know why this email keeps getting cut off!
>=20
> I am attaching my response in a text file.
>=20
> Sigh.
> =20
> Thanks,
>=20
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>=20
>=20
>=20
> ----- Forwarded Message -----
> From: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.co=
m>
> To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team <ge=
n-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf=
-ippm-6man-pdm-option.all@ietf.org>=20
> Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@=
cas.org>; MORTON ALFRED C (AL) <acmorton@att.com>
> Sent: Tuesday, February 21, 2017 10:03 AM
> Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Ti=
me
>=20
> Resending.  Somehow the last email was cut off.
> =20
> Nalini=20
>=20
> From: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.co=
m>
> To: jouni korhonen <jouni.nospam@gmail.com>; General Area Review Team <ge=
n-art@ietf.org>; "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf=
-ippm-6man-pdm-option.all@ietf.org>=20
> Cc: Michael Ackermann <mackermann@bcbsm.com>; Robert Hamilton <rhamilton@=
cas.org>; MORTON ALFRED C (AL) <acmorton@att.com>
> Sent: Tuesday, February 21, 2017 9:59 AM
> Subject: Re: Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Ti=
me
>=20
> Jouni,
>=20
> Here is the thread for your second major comment:
>=20
> Major comment #2 from you:
>=20
> >2) The PDM option relation to actual "server" time is somewhat confusing=
 and the 5-tuple does not allow me to detect the real relationship between =
the >server/application action that caused the generation of the packet and=
 the PDM within the packet. This is specifically an issue with transport/ap=
plication protocols >that multiplex/interleave multiple application streams=
 into one transport. I have no idea of the actual individual application ti=
me since the packets get generated >independent of the processing of a sing=
le thread. I would welcome some discussion around here. Section 1.4 last pa=
ragraph is going to this direction but is not >sufficient IMHO.
>=20
> Yes, you are, of course, correct that all traffic will flow between the m=
atching ports at the two endpoints. The 5-tuples will match regardless of t=
he application.
>=20
> The thing is that we never intended that PDM would distinguish between ap=
plications using the same 5-tuple.  That is, it is a feature, not a bug.
>=20
> What PDM WILL tell you is whether the problem is in the network or the ho=
st.    In our experience, which is primarily on networks for large data cen=
ters, there is a different group which is involved to troubleshoot the prob=
lem depending on the nature of the problem.  That is, do I get the applicat=
ion developers on the line or the team that deals with the routers & infras=
tructure.
>=20
> One of the important functions of PDM is to allow you to do quick triage =
so that you can get the right SWAT team going.   PDM does not tell you if t=
he problem is in the IP stack or the application or buffer allocation.   PD=
M also does not tell you which of the network segments or middle boxes is a=
t fault.  The reason for PDM is to get the right specialists in place who c=
an then be dispatched to investigate their area.
>=20
> In our experience, valuable time is often lost at this first stage of tri=
age.   Both the network group and the application group have quite a few sp=
ecialized tools at their disposal to further investigate their own areas.
>=20
> I am adding some of this verbiage to section 1.4.   Please see below:
>=20
> CURRENT
> -----------
>=20
> 1.4 Rationale for defined solution=20
>=20
> The current IPv6 specification does not provide timing nor a similar=20
> field in the IPv6 main header or in any extension header. So, we=20
> define the IPv6 Performance and Diagnostic Metrics destination option=20
> (PDM).=20
>=20
> Advantages include:=20
>=20
> 1. Real measure of actual transactions.=20
> 2. Independence from transport layer protocols.=20
> 3. Ability to span organizational boundaries with consistent=20
> instrumentation=20
> 4. No time synchronization needed between session partners=20
> 5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
> in a uniform way=20
>=20
> The PDM provides the ability to determine quickly if the (latency)=20
> problem is in the network or in the server (application). More=20
> intermediate measurements may be needed if the host or network=20
> discrimination is not sufficient. At the client, TCP/IP stack time=20
> vs. application time may still need to be broken out by client=20
> software.=20
>=20
>=20
> NEW
> ----
>=20
> 1.4 Rationale for defined solution=20
>=20
> The current IPv6 specification does not provide timing nor a similar=20
> field in the IPv6 main header or in any extension header. So, we=20
> define the IPv6 Performance and Diagnostic Metrics destination option=20
> (PDM).=20
>=20
> Advantages include:=20
>=20
> 1. Real measure of actual transactions.=20
> 2. Independence from transport layer protocols.=20
> 3. Ability to span organizational boundaries with consistent=20
> instrumentation=20
> 4. No time synchronization needed between session partners=20
> 5. Ability to handle all transport protocols (TCP, UDP, SCTP, etc)=20
> in a uniform way=20
>=20
> The PDM provides the ability to determine quickly if the (latency)=20
> problem is in the network or in the server (application).  That is,
> it is a fast way to do triage.
>=20
> One of the important functions of PDM is to allow you to do quickly dispa=
tch
> the right set of diagnosticians.  Within network or server latency,
> there may be many components.  The job of the diagnostician is to rule
> each one out until the culprit is found.
>=20
> How PDM fits into this diagnostic picture is that PDM will quickly tell=
=20
> you how to escalate.  PDM will point to either the network area or the
> server area.   Within the server latency, PDM does not tell you if the bo=
ttleneck
> is in the IP stack or the application or buffer allocation. Within the ne=
twork latency,=20
> PDM does not tell you which of the network segments or middle boxes is at=
 fault.=20
>=20
> What PDM will tell you is whether the problem is in the network or the se=
rver. In our experience,=20
> there is often a different group which is involved to troubleshoot the pr=
oblem depending on the=20
> nature of the problem.   That is, the problem may be escalated to the app=
lication developers
> or the team that deals with the routers and infrastructure.  Both the net=
work group and the=20
> application group have quite a few specialized tools at their disposal to=
 further investigate their
> own areas.   What is missing is the first step, which PDM provides.
>=20
> In our experience, valuable time is often lost at this first stage of tri=
age.  PDM is expected to
> reduce this time substantially.=20
> =20
> Thanks,
>=20
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>=20
> ________________________________
>=20
> From: jouni korhonen <jouni.nospam@gmail.com>
> To: General Area Review Team <gen-art@ietf.org>; draft-ietf-ippm-6man-pdm=
-option.all@ietf.org=20
> Sent: Friday, September 23, 2016 11:14 AM
> Subject: Gen-ART review of
>=20
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/ar ea/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-ippm-6man-pdm-option-05
> Reviewer: Jouni Korhonen
> Review Date: 9/23/2016
> IETF LC End Date: 2016-09-28
> IESG Telechat date: (if known)
>=20
> Summary: The draft needs some work.
>=20
> Major issues:
>=20
>=20
> I have two technical issues here:
>=20
>=20
> 1) There is no mention of what is the time reference plane for internal t=
ime stamping. All other timing and synchronization related documents I am a=
ware of (at least outside IETF) describe it very clearly where in the proce=
ssing/packet handling the time stamp is to be taken. Now the document gives=
 me no idea as an implementer where that should take place. At least it mak=
es it hard to calculate the *network* RTT precisely.
>=20
>=20
> 2) The PDM option relation to actual "server" time is somewhat confusing =
and the 5-tuple does not allow me to detect the real relationship between t=
he server/application action that caused the generation of the packet and t=
he PDM within the packet. This is specifically an issue with transport/appl=
ication protocols that multiplex/interleave multiple application streams in=
to one transport. I have no idea of the actual individual application time =
since the packets get generated independent of the processing of a single t=
hread. I would welcome some discussion around here. Section 1.4 last paragr=
aph is going to this direction but is not sufficient IMHO.
>=20
>=20
> Minor issues:
>=20
>=20
> 1) This is a larger editorial issue. The document is far too long with a =
lot of repetition considering it describes only one IPv6 destination option=
. It is a writing style issue and I am fully aware of that. I have proposal=
s how to cut text in the editorial comments section.
>=20
>=20
> 2) Section 1.2 3rd paragraph talks about IoT and that speed matters there=
. I find this too generalized statement. There are many other things that m=
atter in this application domain and speed might not be that important as b=
eing able to send/receive that one to two bytes of data in a given time win=
dow. I suggest removing this paragraph.
>=20
>=20
> Nits/editorial comments:
>=20
>=20
> 1) Section 1.4 numbered list: add missing full stops.
>=20
>=20
> 2) Section 3.2: remove
>   "The 5-tuple consists of
>    the source and destination IP addresses, the source and destination
>    ports, and the upper layer protocol (ex. TCP, ICMP, etc)."
>=20
> since this is unnecessary repetition.
>=20
> 3) Section 3.2: remove
>   "Operating systems MUST NOT implement a single
>    counter for all connections."
>=20
> Seems again like unnecessary repetition to previous sentence.
>=20
>=20
> 4) Section 3.2 again unnecessary repetition of IPv6 basics that can be re=
ad from RFC2460. Suggest strongly to remove:
>   "This indicates the
>    following processing requirements:
>=20
>    00 - skip over this option and continue processing the header.
>=20
>    RFC2460 [RFC2460] defines other values for the Option Type field.
>    These MUST NOT be used in the PDM."
>=20
>=20
> and
>=20
>   "The
>    possible values are as follows:
>=20
>    0 - Option Data does not change en-route
>=20
>    1 - Option Data may change en-route
>=20
>    The three high-order bits described above are to be treated as part
>    of the Option Type, not independent of the Option Type.  That is, a
>    particular option is identified by a full 8-bit Option Type, not just
>    the low-order 5 bits of an Option Type."
>=20
>=20
> 5) Section 3.3 same as in comment 4). Suggest strongly removing:
>   "This follows the order defined in RFC2460 [RFC2460]
>                  IPv6 header
>=20
>                  Hop-by-Hop Options header
>=20
>                  Destination Options header  <--------
>=20
>                  Routing header
>=20
>                  Fragment header
>=20
>                  Authentication header
>=20
>                  Encapsulating Security Payload header
>=20
>                  Destination Options header <------------
>=20
>                  upper-layer header"
>=20
>=20
> 6) Suggest removing entire Section 3.4 and moving the following text to S=
ection 3.3:
>   "PDM MUST be placed before the ESP header in
>    order to work.  If placed before the ESP header, the PDM header will
>    flow in the clear over the network thus allowing gathering of
>    performance and diagnostic data without sacrificing security."
>=20
>=20
> 7) Section 3.6 suggest removing the following text. I see no value it wou=
ld add to what has already been said:
>   "As with all other destination options extension headers, the PDM is
>    for destination nodes only. As specified above, intermediate devices
>    MUST neither set nor modify this field."
>=20
>=20
> 8) Section 3.6 suggest removing the following 5-tuple text as it has alre=
ady been described earlier in Section 2:
>   "The 5-tuple is:
>=20
>    SADDR : IP address of the sender SPORT : Port for sender DADDR : IP
>    address of the destination DPORT : Port for destination PROTC :
>    Protocol for upper layer (ex. TCP, UDP, ICMP)"
>=20
>=20
> 9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value =
these sections add. I acknowledge they are good to know information of time=
r hardware implementation difference but do not really add value on the on-=
wire encoding of the PDM option.
>=20
>=20
> 10) Section 4.4 suggest removing the entire section. Time Base was alread=
y described in detail enough in Section 3.2.
>=20
>=20
> 11) Section 4.5 time base for picoseconds is 11 not 00.
>=20
>=20
> 12) Section 4.5 suggest removing the following text, since it does not ad=
d any more clarity to what has already been said in my opinion. This is bec=
ause all the examples follow nice nybble increment in scaling:
>   "Sample binary values (high order 16 bits taken)
>=20
>    1 psec            1                                              0001
>    1 nsec          3E8                                    0011 1110 1000
>    1 usec        F4240                          1111 0100 0010 0100 0000
>    1 msec     3B9ACA00           0011 1011 1001 1010 1100 1010 0000 0000
>    1 sec    E8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000"
>=20
>=20
> 12) Section 4.6 I do not understand why this section is here. I strongly =
suggest removing it. Sections 4.5 and 3.2 already describe how I would enco=
de the delta time using scaling as a separate fields not embedded (option f=
ields ScaleDTLR and ScaleDTLS). Did I misunderstand something here?
>=20
>=20
> 13) Section 5 suggest removing the following text because of it repeating=
 what has already been said earlier:
>   "Each packet, in addition to the PDM contains information on the
>    sender and receiver. As discussed before, a 5-tuple consists of:
>=20
>       SADDR : IP address of the sender
>       SPORT : Port for sender
>       DADDR : IP address of the destination
>       DPORT : Port for destination
>       PROTC : Protocol for upper layer (ex. TCP, UDP, ICMP)
>=20
>    It should be understood that the packet identification information is
>    in each packet. We will not repeat that in each of the following
>    steps."
>=20
>=20
> 14) Section 5.3 suggest merging the following text into one example and d=
o necessary rewording. There is no need to do the same calculation twice on=
 almost adjacent lines:
>=20
>   "Sending time : packet 2 - receive time : packet 1
>=20
>    We will call the result of this calculation: Delta Time Last Received
>    (DELTATLR)
>=20
>    That is:
>=20
>    Delta Time Last Received =3D (Sending time: packet 2 - receive time:
>    packet 1)"
>=20
>=20
> 15) Expand RTT and PSN on their first use.
>=20
>=20
> Phew.. after all this I found the document good reading and most likely a=
 useful tool to be used.
>=20
>=20
> Regards,

>=20
>    Jouni
>=20
>=20
>=20
>=20
> <serverTimeComments.txt>


From nobody Wed Feb 22 12:05:18 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB44129AD9; Wed, 22 Feb 2017 12:05:15 -0800 (PST)
X-Quarantine-ID: <CF_QuydnYirC>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CF_QuydnYirC; Wed, 22 Feb 2017 12:05:13 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id BFD0A129A70; Wed, 22 Feb 2017 12:05:12 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 22 Feb 2017 11:55:50 -0800
Mime-Version: 1.0
Message-Id: <p06240603d4d39d70bb08@[99.111.97.136]>
In-Reply-To: <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <p06240602d4d236a5a2dd@[99.111.97.136]> <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Wed, 22 Feb 2017 12:05:09 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Dale Worley <worley@ariadne.com>, gen-art@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/651Lfa5WHlIhw1HyJe1DKobWDT4>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
Subject: Re: [Gen-art] [Slim] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:05:15 -0000

At 11:57 AM +0100 2/22/17, Gunnar Hellstr=F6m wrote:

>  A few comments inline,
>
>
>  Den 2017-02-22 kl. 02:44, skrev Randall Gellens:
>>  Hi Dale,
>>
>>  Thank you for your review, I appreciate it.  Please see inline.
>>
>>  At 6:32 PM -0800 2/17/17, Dale Worley wrote:
>>
>>>   Reviewer: Dale Worley
>>>   Review result: Ready with Nits
>>>
>>>   I am the assigned Gen-ART reviewer for this draft.  The General Area
>>>   Review Team (Gen-ART) reviews all IETF documents being processed
>>>   by the IESG for the IETF Chair.  Please treat these comments just
>>>   like any other last call comments.
>>>
>>>   For more information, please see the FAQ at
>>>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>>   Document:  draft-ietf-slim-negotiating-human-language-06
>>>   Reviewer:  Dale R. Worley
>>>   Review Date:  2017-02-17
>>>   IETF LC End Date:  2017-02-20
>>>   IESG Telechat date:  [unknown]
>>>
>>>   Summary:
>>>          This draft is basically ready for publication, but has nits
>>>          that should be fixed before publication.
>>>
>>>   * Technical comments
>>>
>>>   A. Call failure
>>>
>>>   If a call fails due to no available language match, in what way(s)
>>>   does it fail?  Section 5.3 says
>>>
>>>      If such an offer is received, the receiver MAY
>>>      reject the media, ignore the language specified, or attempt to
>>>      interpret the intent
>>>
>>>   But I suspect it's also allowed for the UAS to fail the call at the
>>>   SIP level.  Whether or not that is allowed (or at least envisioned)
>>>   should be described.  And what response code(s)/warn-code(s) should
>>>   be
>>>   used for that?
>>
>>  The text you quote has been deleted.  The=20
>> draft does not mandate if the call should=20
>> proceed or fail if there is no language match=20
>> possible, although the draft does provide an=20
>> optional mechanism to indicate the caller's=20
>> preference that the call not fail, and the=20
>> draft does mention that in the emergency=20
>> services case, the call will likely proceed,=20
>> but that's a matter of policy not protocol.
>  You may have a version where it is proposed=20
> that the text is deleted. We need to see that=20
> new text and agree if it was good to delete it.

I will be uploading the updated draft shortly.=20
The only question is if I upload it before or=20
after adding any extra examples.

>
>  There are more places in the draft where=20
> failing the call is mentioned, so the question=20
> about how it is failed is relevant anyway. A=20
> 603 Decline from the proxy would likely be the=20
> natural way to fail the call when it is because=20
> of lack of matching languages. But I do not see=20
> any natural way for an addressed UA to signal=20
> this.

I do not believe the draft needs to mandate how a call is rejected.

>
>>
>>>
>>>   B. Audio/Video coordination
>>>
>>>      5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>>
>>>      Note that while signed language tags are used with a video stream
>>>   to
>>>      indicate sign language, a spoken language tag for a video stream
>>>   in
>>>      parallel with an audio stream with the same spoken language tag
>>>      indicates a request for a supplemental video stream to see the
>>>      speaker.
>>>
>>>   And there's a similar paragraph in 5.4:
>>>
>>>>      A spoken language tag for a video stream in conjunction with an
>>>   audio
>>>>      stream with the same language might indicate a request for
>>>>      supplemental video to see the speaker.
>>>
>>>   I think this mechanism needs to be described more exactly, and in
>>>   particular, it should not depend on the UA understanding which
>>>   language tags are spoken language tags.  It seems to me that a
>>>   workable rule is that there is an audio stream and a video stream and
>>>   they specify exactly the same language tag in their respective
>>>   humintlang attributes.  In that case, it is a request for a spoken
>>>   language with simultaneous video of the speaker, and those requests
>>>   should be considered satisfied only if both streams can be
>>>   established.
>>
>>  The text you quote has been deleted.  A media=20
>> stream for supplemental purposes can be=20
>> negotiated without a language tag, as normal.
>>
>  The text should not be deleted just because it is under discussion.

It was controversial and not needed, hence it was=20
deleted.  The WG expressed a goal of publishing a=20
simple document to have something that can be=20
deployed.

>  It is a valid and valuable alternative. At the=20
> moment we lack ways to indicate if languages=20
> are wanted together or seen as separate=20
> alternatives, and we have said that such=20
> detailing can be added in future versions or=20
> additional specifications if not done now.=20
> Therefore we had better allow this combination=20
> and let the negotiating parties sort out what=20
> it currently means. The specification just=20
> indicates that the indicated languages are=20
> alternatives, and any number may be selected=20
> for matching and usage in the session.
>  I do not think we should require very exactly=20
> matching language tags between spoken language=20
> in audio and corresponding view of the speaker=20
> in video.

We are not requiring this.  On the contrary, a=20
video stream without a language attribute=20
indicates it is used for supplemental purposes,=20
not interactive language.  If we need more=20
capabilities, this can be done in the future.

>>>
>>>   * The following three items are adjustments to the design which I'd
>>>   like to know have been considered.
>>>
>>>   C. "humintlang" seems long to me
>>>
>>>   Given the excessive length of SDP in practice, it seems to me that a
>>>   shorter attribute name would be desirable.  E.g., "humlang" as was
>>>   used in some previous versions.  Or is there a coordinated usage with
>>>   other names in the "hum*lang" pattern?
>>
>>  There is no intent for a coordinated pattern.=20
>> The name was chosen years ago to avoid=20
>> potential confusion with the 'lang' attribute.=20
>> Is it worth reopening the issue to potentially=20
>> save three characters per SDP line with a=20
>> language?
>>
>>>
>>>   D. Use the Accept-Language syntax
>>>
>>>   It seems to me that it would better to use the Accept-Language syntax
>>>   for the attribute values.  This allows (1) specifiying the quality of
>>>   language experience, allowing clear description of bilingualism, (2)
>>>   a
>>>   unified method of specifying whether or not arbitrary languages are
>>>   acceptable, and (3) abbreviating SDP descriptions.
>>>
>>>   In a way, the fact that the current proposal seems to require (but
>>>   does not directly specify) the coordinated absence/presence of an
>>>   asterisk on all of the repetitions of humintlang-send or
>>>   humintlang-recv is a warning that the syntax doesn't represent the
>>>   semantics as well as it might.
>>
>>  The group considered multiple proposals to=20
>> permit specifying quality, preference,=20
>> q-values, etc. but decided to keep things=20
>> simple for this draft.  There is no intent to=20
>> require the use of an asterisk (to indicate a=20
>> preference by the caller to not fail the=20
>> call).  The asterisk is a very mild mechanism=20
>> with no normative effects.  It merely conveys=20
>> the preference of the caller, and is not=20
>> binding on the answerer.
>  I would never dare to use an sdp without an=20
> asterisk. Language matching is a tricky thing=20
> and human capabilities much wider than the=20
> language tags can express. If I get a call from=20
> a Norwegian user talking Norwegian and=20
> indicating Norwegian in the humintlang=20
> attributes, I want to get the call accepted by=20
> my device with setting for spoken Swedish,=20
> because Swedes and Norwegians usually can=20
> communicate quite well speaking their own=20
> languages. I would anyway not have imagined=20
> making a setting for Norwegian language as a=20
> preference in my device.
>  It will however be an excellent help for me to=20
> see the indication of the Norwegian, when I get=20
> the call, so I can tune my listening.
>  By setting the asterisk somewhere among the=20
> Humintlang attributes, I will make sure that I=20
> do not lose calls that I could handle.
>
>>
>>>   E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>>
>>>   Note that all examples are bidirectionally symmetric, and the text
>>>   says that requests and responses SHOULD be bidirectionally symmetric.
>>>   So it would be a very useful abbreviation to define
>>>   "humintlang=3D<value>" to be equivalent to the combination of
>>>   "humintlang-send=3D<value>" and "humintlang-recv=3D<value>".
>>>
>>>   Combining proposals C, D, and E, the examples become
>>>
>>>         m=3Daudio 49170 RTP/AVP 0
>>>         a=3Dhumlang:en
>>>
>>>         m=3Dvideo 51372 RTP/AVP 31 32
>>>         a=3Dhumlang:ase,*;q=3D0.1
>>>
>>>         m=3Daudio 49250 RTP/AVP 20
>>>         a=3Dhumlang:es,eu;q=3D0.9,en;q=3D0.8,*;q=3D0.1
>>>
>>>         m=3Dtext 45020 RTP/AVP 103 104
>>>         a=3Dhumlang:gr
>>>
>>>   which requires about half as many characters as they have now.
>>
>>  A third attribute without the "-send" or=20
>> "-recv" to indicate bidirectionality would=20
>> reduce the characters in the SDP block, at the=20
>> cost of some added complexity (e.g., what if=20
>> all three appear).  I don't believe this has=20
>> been discussed in the group.
>>
>>>   * Editorial comments and nits
>>>
>>>   Abstract
>>>
>>>      This document describes the need and a solution using new SDP
>>>   stream
>>>      attributes.
>>>
>>>   I don't think the term "stream attribute" is used in RFC 4566.
>>>   Instead, it uses "media attribute".
>>
>>  Fixed.
>>
>>>   1.  Introduction
>>>
>>>      caller and callee know each other or there is contextual or out of
>>>      band information from which the language(s) and media modalities
>>>   can
>>>
>>>   I think this context, it's preferred to hyphenate "out-of-band" to
>>>   make it clearly be an adjective.
>>
>>>   OK.
>>
>>
>>>      This approach has a number of benefits, including that it is
>>>   generic
>>>      (applies to all interactive communications negotiated using SDP)
>>>   and
>>>      not limited to emergency calls.
>>>
>>>   I think s/and not limited to/and is not limited to/ reads more
>>>   smoothly.
>>
>>  There's no harm in the extra "is" so I'm happy to add it.
>>
>>>      But it is clearly useful in many other cases.  For
>>>      example, someone calling a company call center or a Public Safety
>>>      Answering Point (PSAP) should be able to indicate if one or more
>>>      specific signed, written, and/or spoken languages are preferred,
>>>   the
>>>      callee should be able to indicate its capabilities in this area,
>>>   and
>>>      the call proceed using in-common language(s) and media forms.
>>>
>>>   I think s/preferred, the callee/preferred; the callee/ because the
>>>   sentence is the concatenation of two sentences.
>>
>>  I reworded the sentence to flow better:
>>
>>     For example, it is helpful that someone calling a company call center
>>     or a Public Safety Answering Point (PSAP) be able to indicate
>>     preferred signed, written, and/or spoken languages, the callee be
>>     able to indicate its capabilities in this area, and the call proceed
>>     using the language(s) and media forms supported by both.
>>
>>>   Perhaps s/in-common/shared/.
>>
>>  Fixed in the rewording above.
>>
>>>
>>>      Including the user's human (natural) language preferences in the
>>>      session establishment negotiation is independent of the use of a
>>>      relay service and is transparent to a voice service provider.
>>>
>>>   I think it's even broader than "transparent to a voice service
>>>   provider" -- it's transparent to any serivice provider, assuming that
>>>   the media are language-neutral.
>>
>>  I changed it to read "voice or other service provider".
>>
>>>
>>>      In the case of a call to e.g., an airline, the call could be
>>>      automatically handled by a Spanish-speaking agent.
>>>
>>>   I think s/handled by/routed to/ is the usual usage.
>>
>>  We are trying to be careful in the draft to=20
>> not imply that it is discussing call routing.=20
>> I'd rather keep the more generic "handled by".
>>
>>>
>>>   3.  Desired Semantics
>>>
>>>      The desired solution is a media attribute (preferably per
>>>   direction)
>>>      that may be used within an offer to indicate the preferred
>>>   language
>>>      of each (direction of a) media stream, and within an answer to
>>>      indicate the accepted language.
>>>
>>>   In this one instance, I think you want to use "language(s)" to drive
>>>   home that that multiple languages can be specified:  "within an offer
>>>   to indicate the preferred language(s)".
>>>
>>>      (Negotiating multiple simultaneous languages within a media stream
>>>   is
>>>      out of scope, as the complexity of doing so outweighs the
>>>      usefulness.)
>>>
>>>   You might want to say instead "(Negotiating multiple simultaneous
>>>   languages within a media stream is out of scope for this document.)"
>>>   to ensure that nobody decides to argue whether "the complexity of
>>>   doing so outweighs the usefulness".
>>
>>  I agree and deleted "the complexity of doing so outweighs the usefulness=
".
>>
>>>
>>>   4.  The existing 'lang' attribute
>>>
>>>      RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>>      similar to what is needed here, but is not sufficiently detailed
>>>   for
>>>      use here.
>>>
>>>   "for use here" isn't quite right.  Maybe "is not sufficiently
>>>   specific
>>>   or flexible to satisfy the requirements".
>>>
>>>      In addition, it is not mentioned in [RFC3264]
>>>
>>>   "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>>   attribute".
>>
>>  OK, accepted both changes.
>>
>>>
>>>   5.  Proposed Solution
>>>
>>>   Perhaps /Proposed Solution/Solution/, since once this draft is
>>>   approved, it becomes the solution.
>>
>>  OK.
>>
>>>
>>>   5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>>
>>>         a=3Dhumintlang-send:<language tag>
>>>         a=3Dhumintlang-recv:<language tag>
>>>
>>>   This is presented as the generic form of the attributes, but there is
>>>   no indication of the posible asterisk.
>>
>>  The syntax has been deleted from 5.2 since it's now in 6.
>  I think it should not be deleted, but instead=20
> Dale's comment satisfied.  That would be more=20
> in line with the stye of rfc4566bis.
>  5.2 shows the complete attributes, and that is=20
> good. Chapter 6 only shows the syntax of the=20
> value.

Having the syntax in two places is a stylistic matter.

>>
>>>
>>>      The values constitute a list of languages
>>>      in preference order (first is most preferred).
>>>
>>>   "The values" isn't very clear, because the values are in successive
>>>   attributes.  You want to say something like "The sequence of values
>>>   in
>>>   the occurrences of one of these attributes constitutes ...".
>>>   However,
>>>   see the technical comments above.
>>
>>  The text was reworded to read:
>>
>>     The values from all
>>     instances of the attribute constitute a list of languages in
>>     preference order (first is most preferred).
>>
>>>
>>>      When placing an emergency call, and in any other case where the
>>>      language cannot be assumed from context, each media stream in an
>>>      offer primarily intended for human language communication SHOULD
>>>      specify both (or in some cases, one of) the 'humintlang-send' and
>>>      'humintlang-recv' attributes.
>>>
>>>   Probably s/assumed/inferred/.
>>
>>  I agree.
>>
>>>
>>>   Could you be more accurate by
>>>   s/or in some cases/or for unidirectional streams/?
>>
>>  I agree.
>>
>>>
>>>   5.3.  Advisory vs Required
>>>
>>>      The mechanism for indicating this preference is that, in an offer,
>>>   if
>>>      the last character of any of the 'humintlang-recv' or 'humintlang-
>>>      send' values is an asterisk, this indicates a request to not fail
>>>   the
>>>      call (similar to SIP Accept-Language syntax).  Either way, the
>>>   called
>>>      party MAY ignore this, e.g., for the emergency services use case,
>>>   a
>>>      PSAP will likely not fail the call.
>>>
>>>   The construction of this paragraph isn't quite complete.  It says
>>>   that
>>>   if an asterisk is present, a request shouldn't fail, but it doesn't
>>>   say that if no asterisk is present, a request should fail if there is
>>>   no language match.  And it's the latter condition that makes the
>>>   second sentence meaningful.  So I think you want to insert between
>>>   the
>>>   two sentences one regarding the absence of an asterisk.
>>
>>  I've reworded the section to read:
>>
>>     A consideration with the ability to negotiate language is if the call
>>     proceeds or fails if the callee does not support any of the languages
>>     requested by the caller.  This document does not mandate either
>>     behavior, although it does provide a way for the caller to indicate a
>>     preference for the call succeeding when there is no language in
>>     common.  It is OPTIONAL for the callee to honor this preference.  For
>>     example, a PSAP is likely to attempt the call even without an
>>     indicated preference when there is no language in common, while a
>>     call center might choose to fail the call.
>>
>>     The mechanism for indicating this preference is that, in an offer, if
>>     the last character of any of the 'humintlang-recv' or 'humintlang-
>>     send' values is an asterisk, this indicates a request to not fail the
>>     call.  The called party MAY ignore the indication, e.g., for the
>>     emergency services use case, regardless of the absence of an
>>     asterisk, a PSAP will likely not fail the call; some call centers
>>     might reject a call even with an asterisk.
>  This still does not meet Dale's comment.
>  Insert a sentence saying:
>  "A preference for getting the call denied in=20
> case of no language match SHOULD be indicated=20
> by no asterisk appended on any humintlang=20
> attribute value in the whole SDP."

I don't think that's needed, and it's a strangely=20
constructed normative directive.  How can a=20
preference have a SHOULD?

>>
>>>   5.5.  Examples
>>>
>>>   Given that the combined audio/video mechanism is the only
>>>   irregularity
>>>   in this system, there ought to be an example of it.  E.g.,
>>>
>>>      An example of a supplemental video stream with a spoken language
>>>      audio stream:
>>>
>>>         m=3Dvideo 51372 RTP/AVP 31 32
>>>         a=3Dhumintlang-send:en
>>>         a=3Dhumintlang-recv:en
>>>
>>>         m=3Daudio 49250 RTP/AVP 20
>>>         a=3Dhumintlang-send:en
>>>         a=3Dhumintlang-recv:en
>>
>>  If the video stream is supplemental then it=20
>> doesn't have a language (the text that=20
>> suggested otherwise has been deleted). But I=20
>> am considering adding more examples.
>  I provided a rich set of examples in my LC=20
> comments of Feb 13. Please consider them as a=20
> base even if some need revision if the proposed=20
> extended meaning of the asterisk is not=20
> accepted.

Thank you for submitting them; I am considering them.

>>
>>>
>>>   6.  IANA Considerations
>>>
>>>         humintlang-value =3D  Language-Tag [ asterisk ]
>>>                             ; Language-Tag defined in RFC 5646
>>>         asterisk         =3D  "*"
>>>
>>>   s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>>   5646/
>>>
>>>   But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>>   tracks the current version of language tags.
>>
>>  Ok.
>>
>>>
>>>   Appendix A.  Historic Alternative Proposal: Caller-prefs
>>>
>>>      This
>>>      results in a more fragile solution since the media modality and
>>>      language would be negotiated using SIP, and then the specific
>>>   media
>>>      formats (which inherently include the modality) would be
>>>   negotiated
>>>      at a different level (typically SDP, especially in the emergency
>>>      calling cases), making it easier to have mismatches (such as where
>>>      the media modality negotiated in SIP don't match what was
>>>   negotiated
>>>      using SDP).
>>>
>>>   "the media modality and language would be negotiated using SIP" isn't
>>>   quite the right way to say it because SIP isn't explicitly
>>>   negotiating
>>>   the modality.  Better would be
>>>
>>>      ... the language (and by implication the media modality) would be
>>>      negotiated using SIP, and then the specific media (which
>>>   inherently
>>>      include the modalities and formats) would be negotiated at a
>>>      different level ...
>>
>>  This section has been deleted.
>  Did we agree on that?

It was suggested in earlier comments to delete it=20
as it is clearly not needed (it's an informative=20
appendix detailing a historical alternative that=20
was not pursued).


>>
>>>
>>>   [END]
>>
>>
>  Regards
>  Gunnar
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
    The highlight of the annual Computer Bowl occurred when Bill Gates,
who was a judge, posed the following question to the contestants:
    "What contest, held via Usenet, is dedicated to examples of weird,
obscure, bizarre, and really bad programming?"
    After a moment of silence, Jean-Louis Gassee (ex-honcho at Apple)
hit his buzzer and answered "Windows."
                                          --Recounted by Adam C. Engst


From nobody Wed Feb 22 12:11:00 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1393B129ABE; Wed, 22 Feb 2017 12:10:43 -0800 (PST)
X-Quarantine-ID: <1YyZcYODmjIa>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1YyZcYODmjIa; Wed, 22 Feb 2017 12:10:41 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id C5F9D129A98; Wed, 22 Feb 2017 12:10:41 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 22 Feb 2017 12:01:20 -0800
Mime-Version: 1.0
Message-Id: <p06240604d4d3a0175a34@[99.111.97.136]>
In-Reply-To: <87h93mut8q.fsf@hobgoblin.ariadne.com>
References: <87h93mut8q.fsf@hobgoblin.ariadne.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 22 Feb 2017 12:10:38 -0800
To: worley@ariadne.com (Dale R. Worley), Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, slim@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/dV65iaOF-VG-ZzSVenTHXvRGskE>
Cc: gen-art@ietf.org, rg+ietf@randy.pensive.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
Subject: Re: [Gen-art] [Slim] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:10:43 -0000

At 10:42 AM -0500 2/22/17, Dale R. Worley wrote:

>  Gunnar Hellstr=F6m <gunnar.hellstrom@omnitor.se> writes:
>>>>   A. Call failure
>>>>
>>>>   If a call fails due to no available language match, in what way(s)
>>>>   does it fail?  Section 5.3 says
>>>>
>>>>      If such an offer is received, the receiver MAY
>>>>      reject the media, ignore the language specified, or attempt to
>>>>      interpret the intent
>>>>
>>>>   But I suspect it's also allowed for the UAS to fail the call at the
>>>>   SIP level.  Whether or not that is allowed (or at least envisioned)
>>>>   should be described.  And what response code(s)/warn-code(s) should
>>>>   be used for that?
>>>
>>>  The text you quote has been deleted.  The draft does not mandate if
>>>  the call should proceed or fail if there is no language match
>>>  possible, although the draft does provide an optional mechanism to
>>>  indicate the caller's preference that the call not fail, and the draft
>>>  does mention that in the emergency services case, the call will likely
>>>  proceed, but that's a matter of policy not protocol.
>>
>>  You may have a version where it is proposed that the text is deleted. We
>>  need to see that new text and agree if it was good to delete it.
>>
>>  There are more places in the draft where failing the call is mentioned,
>>  so the question about how it is failed is relevant anyway. A 603 Decline
>>  from the proxy would likely be the natural way to fail the call when it
>>  is because of lack of matching languages. But I do not see any natural
>>  way for an addressed UA to signal this.
>
>  I would argue strongly against using a 6xx response, as the defined
>  effect of those is to make the call fail all the way back to the
>  caller, rather than allowing alternative forks of the call to possibly
>  succeed.  The way to handle a call that *this* proxy can't route due to
>  language incompatibility is a 4xx response.
>
>  My question wasn't for the draft to be prescriptive on this issue (and
>  that seems to align with what the WG/authors intend), but to provide
>  implementation advice, best practices as it were -- There are a lot 4xx
>  responses available, and if you don't read their descriptions carefully,
>  it can be easy to choose one with the wrong semantics.  E.g., a 415
>  response is "Unsupported Media Type", but it's not for unsupported media
>  in the *session* (i.e., the SDP), it's for unsupported media in the
>  *INVITE body* (i.e., you can't process application/sdp).
>
>  OK, here it is:  RFC 3261 section 13.3.1.3:
>
>     A UAS rejecting an offer contained in an INVITE SHOULD return a 488
>     (Not Acceptable Here) response.  Such a response SHOULD include a
>     Warning header field value explaining why the offer was rejected.
>
>  section 21.4.26:
>
>  21.4.26 488 Not Acceptable Here
>
>     The response has the same meaning as 606 (Not Acceptable), but only
>     applies to the specific resource addressed by the Request-URI and the
>     request may succeed elsewhere.
>
>     A message body containing a description of media capabilities MAY be
>     present in the response, which is formatted according to the Accept
>     header field in the INVITE (or application/sdp if not present), the
>     same as a message body in a 200 (OK) response to an OPTIONS request.
>
>  and section 21.6.4:
>
>  21.6.4 606 Not Acceptable
>
>     The user's agent was contacted successfully but some aspects of the
>     session description such as the requested media, bandwidth, or
>     addressing style were not acceptable.
>
>     A 606 (Not Acceptable) response means that the user wishes to
>     communicate, but cannot adequately support the session described.
>     The 606 (Not Acceptable) response MAY contain a list of reasons in a
>     Warning header field describing why the session described cannot be
>     supported.  Warning reason codes are listed in Section 20.43.
>
>  And my memory was correct; a Warning header is appropriate in a 488
>  response.  Section 20.43 gives the details; it looks like a warn-code in
>  the range 390-398 is appropriate, or perhaps 300-329.  It seems like the
>  choice should be either 308 or 390, the first available codes in those
>  ranges.  And the ideal message text would contain the list of compatible
>  languages:
>
>      Warning: 308 proxy.example.com "Supported languages are: es, en"
>
>  The registration would be something like:
>
>      308 Incompatible language specification:  No requested      [this RFC=
]
>          language is supported and offerer requested failure.
>          The text should include the list of supported languages.

Thanks, Dale.  It seems that it would be useful=20
for the draft to suggest (not require) that a=20
session rejected due to lack of=20
mutually-supported languages use 488 or 606, and=20
also include a Warning header field with the=20
suggested 308 code that the draft would register.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
We are what we repeatedly do. Excellence, then, is not an act but a habit.
                                --Aristotle


From nobody Wed Feb 22 13:59:20 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3EC129BF3; Wed, 22 Feb 2017 13:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43JhWEWaeT9q; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DF54129BF0; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
Received: by mail-oi0-x22f.google.com with SMTP id s205so8813569oif.3; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mOOUYf2NZ+i3gfMTVySGw6jYt0lmGd0UZsTpLt6kPqE=; b=OQZePFmv4mwlEyhtwWti7GbyAct/XZzQGp23Yofoypvd6AHmPibb6nSHvWiypxK7Bk G0xftgqCqNXey5l9VIvXuyD/f4i15YOCiIJNvmQ8hHF0QFINZCI6eJXZktaaWfXzBBeR 4NpvJAVqL/8ChJv+HicPZWQmjtNLTDSd7kUVds9kKuihgO7v5BzDFzKt8DZJU8ZF7F33 8kMAc0hatW8GhFYuqVH2Sa9/hzf6ssvOHC8T8pzHCfuyYi7NRXwma72Gd7jNRs47zZLL U93U69uDN9WnGEhBCj32mOLJoukdIPIaTsULZU34pcPae9XF4vakCWqY4gmLJCPT3uFd 57Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mOOUYf2NZ+i3gfMTVySGw6jYt0lmGd0UZsTpLt6kPqE=; b=OPNUi56NbD4fu2RLRG7LwwkFIpndmN4vjhM6phsByETKSZLQxxsi61TMc7UK9fN0lL LiKQeDpDpsv/VR2ZmECCy/iWaZhINZc1rtrBV9yTFVM7hhTT/LwxJv1TJUXGFMveoVRI dyFvlAykPRbEmtiGlHU3OsJ+SFgumIpdIlneoTprucLJxUahJ3Cx4Rf9D+9Q4xLEwbkd MclHBHODHB8goDP27AZNbTcTXn5fNxx6z4ocoOJm738Vap5kMtfKr4OinwJIAhr4pskQ 0aPoRHS8lBXinbgl0mBEZKnMOeMbPJoQlQIa3n3m5VrYBxjsXdBRatlNfw9mkjjmiGz0 PghA==
X-Gm-Message-State: AMke39kczSwPxPrGs3Y8KUzO6UaYjonPXhkvj7blj4DSBdmjKlE+31FHpY7aTwK3Fwor7K+VSYelHG6ynVEl8g==
X-Received: by 10.202.72.2 with SMTP id v2mr5435370oia.179.1487800752356; Wed, 22 Feb 2017 13:59:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Wed, 22 Feb 2017 13:58:42 -0800 (PST)
In-Reply-To: <148559843419.17936.4314684504467085961.idtracker@ietfa.amsl.com>
References: <148559843419.17936.4314684504467085961.idtracker@ietfa.amsl.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 22 Feb 2017 13:58:42 -0800
Message-ID: <CA+9kkMBb93qg9NccNkNpn2=sJdfgqE8=MccVz6zWf4MNccGfvQ@mail.gmail.com>
To: Stewart Bryant <stewart@g3ysx.org.uk>
Content-Type: multipart/alternative; boundary=001a113e4eac57444a0549259b84
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/26chanJyLJ8G8-A-owpR8jtq-f4>
Cc: gen-art@ietf.org, IETF <ietf@ietf.org>, draft-hardie-privsec-metadata-insertion.all@ietf.org
Subject: Re: [Gen-art] Review of draft-hardie-privsec-metadata-insertion-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 21:59:15 -0000

--001a113e4eac57444a0549259b84
Content-Type: text/plain; charset=UTF-8

Hi Stewart,

Thanks for the review.  I've updated the abstract, removed the vestigial
reference, added a reference for EDNS0 and clarified how it is used in the
design I describe.

Thanks again for your attention to it,

Ted

On Sat, Jan 28, 2017 at 2:13 AM, Stewart Bryant <stewart@g3ysx.org.uk>
wrote:

> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-hardie-privsec-metadata-insertion-??
> Reviewer: Stewart Bryant
> Review Date: 2017-01-28
> IETF LC End Date: 2017-02-21
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: This is a well written document with a couple of nits. It
> would be helpful to the reader interested in the concept, but
> unfamiliar with DNS if there was some minor additional clarification
> regarding  EDNS0.
>
> Major issues: None
>
> Minor issues:
>
> RFC4301 is an unused reference. Is it missing from the text?
>
> =====
>
>    By negotiating an EDNS0
>    option which allowed them to self-populate this data,.....
>
> SB> Calling up EDNS0 (which really needs expanding) comes out of the
> SB> blue and could use a reference and sentence of explanation
> SB> at least for those not familiar with the detail of DNS.
>
> Nits/editorial comments:
>
> [RFC7624] in the Abstract should be changed to RFC7624
>
> =========
>
> 1.  Introduction
> ....
>    exploited in the attacks document in [RFC7258] and the threats
> s/document/documented/
>
>
>

--001a113e4eac57444a0549259b84
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Stewart,<br><br></div>Thanks for the rev=
iew.=C2=A0 I&#39;ve updated the abstract, removed the vestigial reference, =
added a reference for EDNS0 and clarified how it is used in the design I de=
scribe.=C2=A0 <br><br></div>Thanks again for your attention to it,<br><br><=
/div>Ted<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Sat, Jan 28, 2017 at 2:13 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:stewart@g3ysx.org.uk" target=3D"_blank">stewart@g3ysx.org.uk<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Stewart B=
ryant<br>
Review result: Ready with Nits<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-hardie-privsec-metadata-<wbr>insertion-??<br>
Reviewer: Stewart Bryant<br>
Review Date: 2017-01-28<br>
IETF LC End Date: 2017-02-21<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary: This is a well written document with a couple of nits. It<br>
would be helpful to the reader interested in the concept, but<br>
unfamiliar with DNS if there was some minor additional clarification<br>
regarding=C2=A0 EDNS0.<br>
<br>
Major issues: None<br>
<br>
Minor issues:<br>
<br>
RFC4301 is an unused reference. Is it missing from the text?<br>
<br>
=3D=3D=3D=3D=3D<br>
<br>
=C2=A0 =C2=A0By negotiating an EDNS0<br>
=C2=A0 =C2=A0option which allowed them to self-populate this data,.....<br>
<br>
SB&gt; Calling up EDNS0 (which really needs expanding) comes out of the<br>
SB&gt; blue and could use a reference and sentence of explanation<br>
SB&gt; at least for those not familiar with the detail of DNS.<br>
<br>
Nits/editorial comments:<br>
<br>
[RFC7624] in the Abstract should be changed to RFC7624<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
1.=C2=A0 Introduction<br>
....<br>
=C2=A0 =C2=A0exploited in the attacks document in [RFC7258] and the threats=
<br>
s/document/documented/<br>
<br>
<br>
</blockquote></div><br></div>

--001a113e4eac57444a0549259b84--


From nobody Thu Feb 23 01:01:49 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21767129CF9; Thu, 23 Feb 2017 01:01:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148784049413.20240.15876379956092850264.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 01:01:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/B2cL_WvLx0QVathqw5aqkOyazXM>
Cc: draft-ietf-dime-load.all@ietf.org, dime@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-dime-load-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:01:34 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dime-load-07
Reviewer: Roni Even
Review Date: 2017-02-23
IETF LC End Date: 2017-02-27
IESG Telechat date: 2017-03-16

Summary: This draft is almost ready for publication as a standard
track RFC

Major issues:

Minor issues:

I understand that each node can calculate the load differently , the
example in figure 8 demonstrate that the agent selection may be
different if the agent aggregates load from the servers to calculate
its load or just conveys his load, possibly even that each one of the
agents will use different method. Why not mandate load calculation
using aggregated weighted loads? 

Nits/editorial comments: 
1. In section 5 paragraph 9 "The load report includes a value
indicating the load of the sending
   node relative load of the sending node, " should be just "The load
report includes a value indicating the relative load of the sending
node,"
2. In section 6.2 "weigth "
3. in the security consideration what about an endpoint in the middle
changing the host load value causing a change in the routing
decisions. 





From nobody Thu Feb 23 03:46:48 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A14412A16C; Thu, 23 Feb 2017 03:46:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 03:46:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XxmypvsuH6AJo2eUS5f18hX9XzA>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-httpbis-rfc5987bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:46:42 -0000

Reviewer: Stewart Bryant
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-httpbis-rfc5987bis-??
Reviewer: Stewart Bryant
Review Date: 2017-02-23
IETF LC End Date: 2017-02-20
IESG Telechat date: 2017-03-02

Summary: 

Thus is ready for publication. There are two minor nits, but these can
be delegated to the RFC Editor.

Major issues: None

Minor issues: None

Nits/editorial comments: 

Should say

Obsoletes: RFC5987 (if approved) ("RFC" missing)

Extended notation, using the Unicode characters U+00A3 ("£", POUND
SIGN) and U+20AC ("€", EURO SIGN):

My European computer can display £ and €, but not sure if all can or
whether the RFC series supports these symbols. There symbols were not
present in RFC5987, they were just named.

FYI
Nits complains about obsoleting RFC2231 can be ignored
The nits complaint about RFC2616 can be ignored
The nits complaint about RFC2978 cab be ignored



From nobody Thu Feb 23 03:51:01 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEFF812A179; Thu, 23 Feb 2017 03:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.986
X-Spam-Level: 
X-Spam-Status: No, score=-3.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Xgwjh097oo9; Thu, 23 Feb 2017 03:50:54 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AEF012A167; Thu, 23 Feb 2017 03:50:54 -0800 (PST)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ldspr-1byUpN0Ip1-00j4zC; Thu, 23 Feb 2017 12:50:50 +0100
To: Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <486e7aed-93dc-c942-13c1-d59bbefc6a99@gmx.de>
Date: Thu, 23 Feb 2017 12:50:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:K8mDooFqBPoOH2VhrrdiiMhEXxx3fZdlf/sfb/QswCrbslaX4Dm Rza34bhjN4Ic+92cX92BoW6VX8cq1zP5t6XwUEIiqO92VjF2ak2iLj4RzO9Y8+8XPJjHNR9 4Qn62b8KQTULcRaXKvFNyiWXmSDjQ2drZj/XFOePPKX8d27/KOVLmlBZ4xehMu19B6X0pLt mJE8YdtEBXkSfF2nZKniQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:tiR0wmaq4cA=:/5B6czKWCEqLJetqdcCQrw 6vpKZ/01ZjVr3/mbn8uwEmkKSuRL6B+v1hZTqpyGq7dB71V7+S5XK0WJ/fxEFvHxxKM640uiH URGUcJ56JqCECu+/Wy8l7DXUzeYPZI/m3T94PQ1SuoLpEwe5j8cQziR4+pdpTE2TVnJUibob8 L8vcbdmYc7zjKD5wLbF8uYGgKs4lpk6OyOnbKwYv6jMRh0jyRiCGWWPP3pdj0L6Pe7yesv8W4 gskyj5tilL3qvNYvq0nzNCyHFck7kjA53JOIk7JFX7XDqjL6di2U2Z6H8H+x8nuwi+EawN3EB GnMRCgxQ7S3qqa3u5WzfU5H2SvPSsdcB5QELjKaEWi6fBbv42+NIgoK4bvOVNHALVf6rJLa1k iUzGDjHzcn2ooromm3zrBAVEslYXCBDGcPcoqte6PyVk2bdY4/Pg77KukaaFhAcu9N3RdjGSX FY/gTlkTIgrjjd6X1LYJCcoD9gNsfgiOrKyXw98P81W2rlNKS58rMiJNj6qqHfm6qAvS0keP7 yboEob9Cnquwu9lqVLkNxM/64XynIAV1PLIl5L34Ih0iMz0ljMvJtkaOlWe3x05v7OGIAhZ3u cw/vVJq/lDtbQZ6Y0HMxF48hfpc6uxeidhRrEdyx/ONwkNACW1qe29TLyqw9L71UY8WoGtHMO zsglc6TipCABAm7IJny7YuaMxFcJCzHqFJ0ng1wXSvnIR89a/AiUHNFBhEZ5h2UIHXTMmU9v+ fAV60NdVOtejS1FbMF7ooTeVPu8ue6MFiPVNBxElAEZw+/9Qi7hlBkzmgfDIfmOYKDBiL6fuU Dz3RHgh
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VNTpsaGqNCKtsZHw8ihO2sZIriQ>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-httpbis-rfc5987bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:50:56 -0000

Hi Stewart,

thanks a lot.

 > ...
> Nits/editorial comments:
>
> Should say
>
> Obsoletes: RFC5987 (if approved) ("RFC" missing)

No. See <https://tools.ietf.org/html/rfc7322#section-4.1.4>.

> Extended notation, using the Unicode characters U+00A3 ("£", POUND
> SIGN) and U+20AC ("€", EURO SIGN):
>
> My European computer can display £ and €, but not sure if all can or
> whether the RFC series supports these symbols. There symbols were not
> present in RFC5987, they were just named.

Yes, that's intentional.

The new RFC format (see RFC 7990 etc) allows the use of non-ASCII 
characters for things like I18N related examples and contact 
information, and that's exactly how it is used here.

Best regards, Julian


From nobody Thu Feb 23 04:51:04 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48B912A160 for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2017 04:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id appQ6LXqpsho for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2017 04:51:01 -0800 (PST)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ED35129D10 for <gen-art@ietf.org>; Thu, 23 Feb 2017 04:51:01 -0800 (PST)
Received: by mail-wr0-x230.google.com with SMTP id 89so21084157wrr.3 for <gen-art@ietf.org>; Thu, 23 Feb 2017 04:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=DlzW1OXNk23bKcOc6D4QhnYLW1EI1WrmjBmrlNT/iKM=; b=EUJ0JjKlmrQi8wAYrItkYgz0qkECGomaI6FBGFVlRYnkJ+BfC1FQdYysKR9YjDD4di N2KoND95TpaXJQn5k95h9+3eLa7XVKKdMlzOGOLLNm9LZwvhzkOz96g/HhxSUeF49i8/ 8ote+pdegBZXeUuyFGpCo8tKKDOD85YKzGVOpMYFq1Wh+Bd7COYAZ/mgawv/7Hn2ei+l iwpOiSTt1+lxtfSrBVn5qMw4ij4eRlQHZeeIczcc53TTkXXV2nD5DQmYK4Vxv/d7MlVu 2q22LY32J4HLqgE+1VxYS5LE9FMy34+suyFsZt/YSXjJhlZ4KLrwxEDfnwzYghxH8OO0 AfMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=DlzW1OXNk23bKcOc6D4QhnYLW1EI1WrmjBmrlNT/iKM=; b=GL8LRbyJfTta/6F7e77T+myJgiLouYAIKfG6aRsJIqbImJ6RUfDzYQRteX03ncVgAP fg2m4617v0j70BwtE9fxgIXtyF5F/Zyr7hL0diGr6U6wvFtHrZ7seSD0h3T5RrJxH9t7 ssGfznG1eNdUT8DbY7pbjExaZnkfuztcKKC1KgBWJS6VY6SHxJtoBKpXx2sP8BOE2v7N K9LkXBEOolyKj7OkQZXptIWg3JFZfosgT8cEwKUio5M3Xdi+OW4fMcp7hxt9zZgvBaZK d+txJOOiglOogGwuww5VREF50/HoSYqSHynTutOnmlgOeNXx+NO55XtG/VzpH172Tm1v uZkA==
X-Gm-Message-State: AMke39nj/4vXZG6OCLv7QSXClCNYyBIr5VMekxzvj1BfQcLJCBwASMFeQP3Sq3Lw7eOjNA==
X-Received: by 10.223.161.202 with SMTP id v10mr6680579wrv.140.1487854259369;  Thu, 23 Feb 2017 04:50:59 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id d29sm6262550wmi.19.2017.02.23.04.50.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Feb 2017 04:50:58 -0800 (PST)
To: julian.reschke@gmx.de
References: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com> <486e7aed-93dc-c942-13c1-d59bbefc6a99@gmx.de>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <40690de2-cac7-34df-e1b0-4fc3bda91494@gmail.com>
Date: Thu, 23 Feb 2017 12:50:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <486e7aed-93dc-c942-13c1-d59bbefc6a99@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/S-TkVEadtDJqZruhlZz4NPZPbRY>
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-httpbis-rfc5987bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 12:51:03 -0000

>>
>> Obsoletes: RFC5987 (if approved) ("RFC" missing)
>
> No. See <https://tools.ietf.org/html/rfc7322#section-4.1.4>.
>

I beg your pardon :(

In all these years of reading RFCs I had not noticed that and always 
assumed it was the other way about.

Says something about my cognitive process.

BR

Stewart


From nobody Thu Feb 23 09:38:23 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D1A1294CF; Thu, 23 Feb 2017 09:38:07 -0800 (PST)
X-Quarantine-ID: <86We3dWaumE3>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86We3dWaumE3; Thu, 23 Feb 2017 09:38:05 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 86AFB12A202; Thu, 23 Feb 2017 09:38:05 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 23 Feb 2017 09:28:32 -0800
Mime-Version: 1.0
Message-Id: <p06240601d4d4cd1fe887@[99.111.97.136]>
In-Reply-To: <87fuj4syy6.fsf@hobgoblin.ariadne.com>
References: <87fuj4syy6.fsf@hobgoblin.ariadne.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 23 Feb 2017 09:35:19 -0800
To: worley@ariadne.com (Dale R. Worley)
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PQ-LCc7OVZzdT5p1MLbjOZXwEic>
Cc: slim@ietf.org, ietf@ietf.org, gen-art@ietf.org, gunnar.hellstrom@omnitor.se, draft-ietf-slim-negotiating-human-language.all@ietf.org, rg+ietf@randy.pensive.org
Subject: Re: [Gen-art] [Slim] Review of draft-ietf-slim-negotiating-human-language-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 17:38:07 -0000

At 10:34 AM -0500 2/23/17, Dale R. Worley wrote:

>  Randall Gellens <rg+ietf@randy.pensive.org> writes:
>>  Thanks, Dale.  It seems that it would be useful
>>  for the draft to suggest (not require) that a
>>  session rejected due to lack of
>>  mutually-supported languages use 488 or 606, and
>>  also include a Warning header field with the
>>  suggested 308 code that the draft would register.
>
>  It seems to me that specifying how to reject the call is one of those
>  "SHOULD" things.  Of course, the document would have to register 308 as
>  a warn-code.

The update I posted yesterday does register a new warn-code.  I'm not 
sure we need to use SHOULD instead of explicit advice for the SIP 
response code.  I doubt implementers would ignore the explicit advice 
yet would honor a SHOULD.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
An elephant is a mouse with an operating system.


From nobody Thu Feb 23 15:17:32 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D231C129BE3 for <gen-art@ietf.org>; Thu, 23 Feb 2017 15:17:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148789185083.21088.11395162738381493567.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 15:17:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ithJtEfwCjKQeXGZbkifUgIr9Dg>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: mahoney@nostrum.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 23:17:31 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-03-02

Reviewer               Type      LC end     Draft
Ralph Droms            Telechat  2017-02-07 draft-ietf-nfsv4-rfc5666bis-10 *
Francis Dupont         Last Call 2017-02-24 draft-kivinen-802-15-ie-05 *
Fernando Gont          Last Call 2017-02-27 draft-ietf-urnbis-rfc2141bis-urn-20
Orit Levin             Last Call 2017-01-31 draft-ietf-sidr-delta-protocol-07
Meral Shirazipour      Telechat  2017-02-07 draft-ietf-nfsv4-rpcrdma-bidirection-07 *
Meral Shirazipour      Telechat  2017-02-10 draft-ietf-dmm-hnprenum-06 *
Robert Sparks          Telechat  2017-01-17 draft-ietf-mpls-residence-time-14 *
Peter Yee              Last Call 2017-03-01 draft-ietf-6man-rfc2460bis-08

For telechat 2017-03-16

Reviewer               Type      LC end     Draft
Stewart Bryant         Telechat  2017-01-30 draft-ietf-lamps-eai-addresses-06 *
Stewart Bryant         Last Call 2017-03-03 draft-ietf-mpls-tp-temporal-hitless-psm-12
Brian Carpenter        Last Call 2017-03-06 draft-ietf-httpbis-http2-encryption-10
Elwyn Davies           Last Call 2017-03-07 draft-ietf-jsonbis-rfc7159bis-03
Roni Even              Last Call 2017-03-01 draft-ietf-pce-inter-layer-ext-12
Fernando Gont          Last Call 2017-01-23 draft-ietf-dime-agent-overload-09
Vijay Gurbani          Last Call 2017-03-08 draft-ietf-lmap-yang-11
Christer Holmberg      Last Call 2017-02-28 draft-ietf-pce-stateful-sync-optimizations-08
Russ Housley           Last Call 2017-03-08 draft-ietf-lmap-information-model-17
Paul Kyzivat           Last Call 2017-03-10 draft-bchv-rfc6890bis-04
Matthew Miller         Last Call 2017-03-13 draft-mm-wg-effect-encrypt-07
Dale Worley            Last Call 2017-03-03 draft-ietf-dane-smime-15
Lucy Yong              Last Call 2017-03-03 draft-ietf-tls-rfc4492bis-12

Last calls:

Reviewer               Type      LC end     Draft
Francis Dupont         Last Call 2017-02-24 draft-ietf-dmm-lma-controlled-mag-params-03
Joel Halpern           Last Call 2017-03-02 draft-ietf-anima-grasp-09
Orit Levin             Last Call 2017-03-02 draft-ietf-dprive-dtls-and-tls-profiles-08
Lucy Yong              Last Call 2017-01-30 draft-ietf-sidr-rpki-rtr-rfc6810-bis-09

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Joel Halpern
  Christer Holmberg
  Russ Housley
  Jouni Korhonen
  Paul Kyzivat
  Orit Levin
  Matthew Miller
  Pete Resnick
  Dan Romascanu
  Meral Shirazipour

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Feb 23 16:48:10 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A2D1293DA; Thu, 23 Feb 2017 16:48:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms.ietf@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148789728925.21052.5219361429368790695.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 16:48:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/i0_lrV5-YaOy1qchE6BGPoKhqjk>
Cc: ietf@ietf.org, draft-ietf-nfsv4-rfc5666bis.all@ietf.org, nfsv4@ietf.org
Subject: [Gen-art] Review of draft-ietf-nfsv4-rfc5666bis-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 00:48:09 -0000

Reviewer: Ralph Droms
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-rfc5666bis-10
Reviewer: Ralph Droms
Review Date: 2017-02-23
IETF LC End Date: 2017-02-07
IESG Telechat date: 2017-03-02

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: None



From nobody Fri Feb 24 16:33:39 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04D71295FF for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2017 16:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ec8G-CY3cd81 for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2017 16:33:36 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6B9312952F for <gen-art@ietf.org>; Fri, 24 Feb 2017 16:33:36 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-d0-58b08a885d87
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id DE.B0.02566.88A80B85; Fri, 24 Feb 2017 20:33:31 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Fri, 24 Feb 2017 19:33:31 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org" <draft-ietf-nfsv4-rpcrdma-bidirection.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-nfsv4-rpcrdma-bidirection-07
Thread-Index: AdKO/sG193Bd+jbKRXmGWu+OryUVCw==
Date: Sat, 25 Feb 2017 00:33:30 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E896E40@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E40eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXRPrG5314YIgxdH1Sym7F3LZnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSujZd9R5oKZyhVnr99lbWCcIN/FyMkhIWAi sfT/IsYuRi4OIYH1jBKXu1cxQTjLGSXO3NjEClLFJmAhsf33c1aQhIjAIkaJ5Zf/sIMkhAWC JLZenczWxcgBlAiXmPWjGCQsIqAn8XDhLrBeFgFViU2THzGClPAK+ErselkKEmYUEJP4fmoN E4jNLCAucevJfCaIgwQkluw5zwxhi0q8fPyPFcJWlNjXP50doj5f4vmRjWBxXgFBiZMzn7BM YBSchWTULCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWMHKXFBTm56UaGmxiB QX9Mgs1xB+PeXs9DjAIcjEo8vAZCGyKEWBPLiitzDzFKcDArifBqLgcK8aYkVlalFuXHF5Xm pBYfYpTmYFES570ecj9cSCA9sSQ1OzW1ILUIJsvEwSnVwBgXZvHI471YURGX3mferz0PdrEf C5JkKn9SzyMXYLNs6eGFM6ukNeKcr13cGGyX/bZtUkLgxzUK8xIa97Xl/OWM5hI5ZPGmaT73 531X+D258kWMI1ZUT7Ax/qF8697PsGrJtER/w5DLDI6WHY+OGM59/jxHZIFrv7wVa67Wh45V +uprg1YuVmIpzkg01GIuKk4EAIHKCTp2AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1B-lzGEHjnhyy99TZ72pc2ZSBlc>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-nfsv4-rpcrdma-bidirection-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 00:33:38 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E40eusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair. Please wait for direction from your document shepherd or AD =
before posting a new version of the draft.

For more information, please see the FAQ at <http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-rpcrdma-bidirection-07
Reviewer: Meral Shirazipour
Review Date: 2017-02-24
IETF LC End Date: 2017-02-07
IESG Telechat date:2017-02-28

Summary: This draft is ready to be published as Standards RFC.

Major issues:
Minor issues:
Nits/editorial comments:


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E40eusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair. Please wait for direction from your d=
ocument shepherd or AD before posting
 a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-nfsv4-rpcrdma-bidirection-07<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-02-24<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2017-02-07&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date:2017-02-28<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E40eusaamb107erics_--


From nobody Fri Feb 24 16:37:36 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECD8129600 for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2017 16:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AlkPHq6ZmRQ for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2017 16:37:34 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6684212952F for <gen-art@ietf.org>; Fri, 24 Feb 2017 16:37:34 -0800 (PST)
X-AuditID: c618062d-d73ff700000009d8-56-58b0e2266753
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by  (Symantec Mail Security) with SMTP id EC.B3.02520.622E0B85; Sat, 25 Feb 2017 02:47:22 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0319.002; Fri, 24 Feb 2017 19:37:27 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-dmm-hnprenum.all@tools.ietf.org" <draft-ietf-dmm-hnprenum.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-dmm-hnprenum-06
Thread-Index: AdKO/1FlXKR8vLLFS+KFivwZ9zjytA==
Date: Sat, 25 Feb 2017 00:37:27 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4E896E5A@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E5Aeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXSPt67Wow0RBku3c1ucP9/LbHH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj8aKjbAVLlStON85lbmCcJd/FyMEhIWAi 8fNhahcjF4eQwHpGiVnNN5khnOWMEjsm/WTsYuTkYBOwkNj++zkrSEJEoINRovfbbnaQhLCA s0TP3NVMILaIgIfE3e0fWSBsPYnjT3+B1bAIqEqsPnAAzOYV8JXYfuoHWD2jgJjE91NrwGxm AXGJW0/mg9kSAgISS/acZ4awRSVePv7HCmErSuzrn84OUZ8v0f58FjPETEGJkzOfsExgFJyF ZNQsJGWzkJRBxHUkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYwcpcUFObnpRgabGIFhf0yC TXcH4/3pnocYBTgYlXh4NzRtiBBiTSwrrsw9xCjBwawkwqu5HCjEm5JYWZValB9fVJqTWnyI UZqDRUmcN271/XAhgfTEktTs1NSC1CKYLBMHp1QD42GrLcLnvvI5fvOOzZByY5H1lk6btJ7x EdsCv6KpKubCG0z7LvtsKHqbOP9kI3PDkyWKjyc3TzHfJCvcsYtPexmz85Pjma2X+41k1Kys BHeEMhZ48y8InMp8cbG5196f1xj4p1YfZ5ZPy2JuP/qdf3+FiPjaB7qG3BuvTtzKHKu0c5Oc 3OM1SizFGYmGWsxFxYkAH6/JW3cCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/AMdIMIFziu8mJ1SUe9AlOJ8exZw>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-dmm-hnprenum-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 00:37:36 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E5Aeusaamb107erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair. Please wait for direction from your document shepherd or AD =
before posting a new version of the draft.

For more information, please see the FAQ at <http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-dmm-hnprenum-06
Reviewer: Meral Shirazipour
Review Date: 2017-02-24
IETF LC End Date: 2017-02-10
IESG Telechat date:2017-02-28

Summary: This draft is ready to be published as Standards RFC.

Major issues:
Minor issues:
Nits/editorial comments:


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com


--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E5Aeusaamb107erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair. Please wait for direction from your d=
ocument shepherd or AD before posting
 a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For more information, please see the FAQ at &lt;http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-dmm-hnprenum-06<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-02-24<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2017-02-10<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date:2017-02-28<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4E896E5Aeusaamb107erics_--


From nobody Sat Feb 25 11:41:31 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 506DF1294A6; Sat, 25 Feb 2017 11:41:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
Date: Sat, 25 Feb 2017 11:41:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/d3D_RIyoMNDEULkmnYruV2qJVOY>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: [Gen-art] Review of draft-ietf-anima-grasp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 19:41:15 -0000

Reviewer: Joel Halpern
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-anima-grasp-??
Reviewer: Joel Halpern
Review Date: 2017-02-25
IETF LC End Date: 2017-03-02
IESG Telechat date: Not scheduled for a telechat

Summary:

Major issues:

Minor issues:
     Section 2.2 states that routing protocols mainly consider link
up/down and that "all nodes need a consistent view of the network
topology".  the first seems an over-generalization, since all routing
protocols have metrics, and almost all modern routing protocols carry
significant additional information about the links and nodes.  The
second statement about consistency is true for some protocols, but is
not true for external use of BGP nor, as I understand it, for Babel. 
So it seems again too strong a characterization.  The following
sentence about information not normally used also seems to be at odds
with current practice.

    Bullet 1 under SN7 in section 2.2  talks about the potential for
circular dependence, and then says that this protocol will not provide
any assistance for that.  given that such dependence may be complex. 
In particular, given that these dependencies result in separate
negotiations, the chain of efforts would continue even if the initial
impetus has timed out.  If a single negotiation causes two dependent
negotiations, this would seem to have the potential to cause a work
explosion.

    It is probably considered obvious, but I did not see text
indicating that GRASP messages with unknown MESSAGE_TYPE should be
silently ignored.  Or any other definition of the expected behavior
(should be logged?)

Nits/editorial comments: 
    In section 3.1 in the definition of Technical Objective the text
starts by saying that it is a configurable parameter or set of
parameters.   Most further text refers to a single value, with
indications that the value may be a complex structure.  Hence, in the
first part of the definition, the same construction should be used,
rather than referring to a set of values.  This gets slightly confused
when section 3.10.4 goes back to talking about multiple parameters for
an objective.  Consistency please?

    The first paragraph of 3.5.4.1 states that upon receiving a
discovery request, a recipient will respond, either with the data or
with a divert.  While this is eventually true, it is misleading.  As
3.5.4.2 states, the recipient, if it does not have an answer, will
relay the request in order to get an answer.  Some mention of this in
3.5.4.1 would seem helpful.

    Should the first line of 3.5.5 on negotiation include "(using
M_REQ_NEG)"?



From nobody Sat Feb 25 14:37:47 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAA9912A08F; Sat, 25 Feb 2017 14:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e05Ol11yTEA4; Sat, 25 Feb 2017 14:37:44 -0800 (PST)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AAB712A308; Sat, 25 Feb 2017 14:37:44 -0800 (PST)
Received: by mail-pg0-x22f.google.com with SMTP id s67so26794199pgb.3; Sat, 25 Feb 2017 14:37:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qR50Od4WBLw9m72qD9O064RsAUQBHrI2b7DSJl20pgo=; b=Yjghr2uSo/aqiZgZZcOQUFGqOlSXB+k83/5rUe9EizijXZhmHJKdwCH9xRfZjAPv0Y aTK57mCpKYul3RYhYPKD0OeY1OA1lgOKvkrLUe6lkL31zvAxXpKaFWd2Jvcc7a/9DlLn B1mTb0ObzR/EGtA9VtHfxWRqSs6lAnqyR15dNzLK9Kghy1Q4/sH5aj0+fJsDUZoqLQ8Z hwk7jBnSFPDsd5wmqfN3hv1JNP3+oyC4eAjE2lxBW9CByYOchiyZWpbAS+FT63P/gqAs VEtHcVKraeskLHOzutOJFiF8eWpEM4utXuVxRfU04kYSN+LWTpUNqsEIu46h+lEHEpOi 2t1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=qR50Od4WBLw9m72qD9O064RsAUQBHrI2b7DSJl20pgo=; b=Q7mNUieSbN1URogbwJjZLir7eju+Ryyl/iblFjZbPAC3TcFjVO+zCiTF7qXSwWRm79 pMv2a19x3QJ7lwPnXC4ohVXDfvRFz7kJum+EaNlyIpaaVZn6ZJLBc1qUchX1H/GRjZa/ kB6OoXVi0aoFIHgc7Bnt1Yv3HPETAGW+GSwCbDaqn8X2pRxNS69RCG0DiESnLvaiTWl/ bVAYWEg3dplshh0Y5zWowLESEDb1vbRJ1FqNJTPDHGKvTCouonc9kfl4B8i7Pw1Ammy6 E+RMFI6gIg/GyErKtY+p0ri957rgum9dfpjs94/WnmLWVxguUjDwPjproFyCIPRNl2Qx cO6g==
X-Gm-Message-State: AMke39mrX4aVKJMhFm8ru3bESayaSdLzHsmg9u6jzHBF+yLjOM7nqCF+9FjW6ivCYwvplA==
X-Received: by 10.99.106.199 with SMTP id f190mr12020534pgc.110.1488062263881;  Sat, 25 Feb 2017 14:37:43 -0800 (PST)
Received: from [192.168.178.21] ([118.148.65.110]) by smtp.gmail.com with ESMTPSA id 80sm933874pgd.39.2017.02.25.14.37.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Feb 2017 14:37:43 -0800 (PST)
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
References: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6ecf7784-ffdb-4115-6f02-32d509384b95@gmail.com>
Date: Sun, 26 Feb 2017 11:37:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/RJ4EiO13EhIlVMNLxuMDjGzRRGU>
Cc: draft-ietf-anima-grasp.all@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-anima-grasp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 22:37:46 -0000

CCs trimmed.

Thanks Joel. Good comments, we will deal with all of them. We have some basic
questions to answer first, raised by Charlie Perkins' review*, so it will take
a little while.

Regards
   Brian

* https://mailarchive.ietf.org/arch/msg/ietf/PlJ9SgdwT5mdOPqF2fDDIfAeHMQ

On 26/02/2017 08:41, Joel Halpern wrote:
> Reviewer: Joel Halpern
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-anima-grasp-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-25
> IETF LC End Date: 2017-03-02
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary:
> 
> Major issues:
> 
> Minor issues:
>      Section 2.2 states that routing protocols mainly consider link
> up/down and that "all nodes need a consistent view of the network
> topology".  the first seems an over-generalization, since all routing
> protocols have metrics, and almost all modern routing protocols carry
> significant additional information about the links and nodes.  The
> second statement about consistency is true for some protocols, but is
> not true for external use of BGP nor, as I understand it, for Babel. 
> So it seems again too strong a characterization.  The following
> sentence about information not normally used also seems to be at odds
> with current practice.
> 
>     Bullet 1 under SN7 in section 2.2  talks about the potential for
> circular dependence, and then says that this protocol will not provide
> any assistance for that.  given that such dependence may be complex. 
> In particular, given that these dependencies result in separate
> negotiations, the chain of efforts would continue even if the initial
> impetus has timed out.  If a single negotiation causes two dependent
> negotiations, this would seem to have the potential to cause a work
> explosion.
> 
>     It is probably considered obvious, but I did not see text
> indicating that GRASP messages with unknown MESSAGE_TYPE should be
> silently ignored.  Or any other definition of the expected behavior
> (should be logged?)
> 
> Nits/editorial comments: 
>     In section 3.1 in the definition of Technical Objective the text
> starts by saying that it is a configurable parameter or set of
> parameters.   Most further text refers to a single value, with
> indications that the value may be a complex structure.  Hence, in the
> first part of the definition, the same construction should be used,
> rather than referring to a set of values.  This gets slightly confused
> when section 3.10.4 goes back to talking about multiple parameters for
> an objective.  Consistency please?
> 
>     The first paragraph of 3.5.4.1 states that upon receiving a
> discovery request, a recipient will respond, either with the data or
> with a divert.  While this is eventually true, it is misleading.  As
> 3.5.4.2 states, the recipient, if it does not have an answer, will
> relay the request in order to get an answer.  Some mention of this in
> 3.5.4.1 would seem helpful.
> 
>     Should the first line of 3.5.5 on negotiation include "(using
> M_REQ_NEG)"?
> 
> 
> 


From nobody Sat Feb 25 17:20:15 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 752501295D3; Sat, 25 Feb 2017 17:20:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148807201447.969.8886471079003742158.idtracker@ietfa.amsl.com>
Date: Sat, 25 Feb 2017 17:20:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/J3AtLhwZ2VOjOXt_DnXiDXIS9Ag>
Cc: draft-ietf-httpbis-http2-encryption.all@ietf.org, ietf-http-wg@w3.org
Subject: [Gen-art] Review of draft-ietf-httpbis-http2-encryption-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 01:20:14 -0000

Reviewer: Brian Carpenter
Review result: Ready with Issues

Gen-ART Last Call review of draft-ietf-httpbis-http2-encryption-10

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-httpbis-http2-encryption-10.txt
Reviewer: Brian Carpenter
Review Date: 2017-02-26
IETF LC End Date: 2017-03-06
IESG Telechat date: 2017-03-16 

Summary: Ready with issues
--------

Comments:
---------

Note: Category is Experimental.

Quoting the writeup:

'The primary concern voiced by dissenters has been that widespread
deployment might provide a false sense of security, slowing the
adoption of "real" HTTPS or confusing users."'

FWIW, I share that concern, even with the tag 'Experimental.'

Major issue: 
------------

The Abstract should definitely state the above concern. At the
moment,
it could easily mislead the reader about the value of the solution.
I'd like to see the phrase "it is vulnerable to active attacks" in
the Abstract.

Minor issue:
------------

> 4.4.  Confusion Regarding Request Scheme
...
> Therefore, servers need to carefully examine the use of such
signals
> before deploying this specification.

What does "servers" really mean here? I think it means "implementers
of server code", or maybe "operators of servers"?

Nits:
-----

> 4.1.  Security Indicators
>
>   User Agents MUST NOT provide any special security indicia when an

'Indicia' is a real word, but I think it's unknown to at least 99% of
English speakers. Why not 'indicators' again?





From nobody Sun Feb 26 01:49:04 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D548129464; Sun, 26 Feb 2017 01:49:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148810254318.12511.13035845809455980126.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 01:49:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ICIQEwJIOwz17N2EdidfYCt8ZFk>
Cc: draft-ietf-pce-inter-layer-ext.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-pce-inter-layer-ext-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 09:49:03 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-inter-layer-ext-12
Reviewer: Roni Even
Review Date: 2017-02-26
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-03-16

Summary: This draft is  ready for publication as a standard track
RFC.

Major issues:

Minor issues:

Nits/editorial comments: 

In section 2 "Those TE links exist at the layer/region boarder
normally" should be "border"




From nobody Sun Feb 26 06:10:49 2017
Return-Path: <worley@ariadne.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBFC129960; Sun, 26 Feb 2017 06:10:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 06:10:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/r9LWJCx5lvysiAR87mKMNtlnZZA>
Cc: draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
Subject: [Gen-art] Review of draft-ietf-dane-smime-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 14:10:48 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-dane-smime-15
Reviewer:  Dale R. Worley
Review Date:  2017-02-26
IETF LC End Date:  2017-03-03
IESG Telechat date: 2017-03-16

Summary:  This draft is basically ready for publication, but has nits
that should be fixed before publication.

* Technical points

1. I assume that in parallel with RFC 6698, DNAME records must be
followed during SMIMEA resolution.  It's not clear to me whether
CNAME
records must also be followed or how, given that SNAMEA records are
not for host names, but their grandparent node is a host name.

2. Presumably it was deliberate not to have the first label for an
SNAMEA record be the canonical UTF-8 string for the local-part, even
though the DNS architecture (RFC 1035) seems to admit binary labels.

3. Presumably it was deliberate to hash using SHA2-256 truncated to
224
bits rather than use SHA-224.

4. Is it worth suggesting that some mechanism might be devised for
annotating an e-mail message with the canonical form of the sender's
local-part that is intended to be used to authenticate the message?
The last sentence of the 1st paragraph of section 1 suggests that
this
is deliberately out of scope for this document, but it might be worth
suggesting experimentation regarding this in section 4, which seems
to
be entirely about further experimentation.

* Editorial/Nits

Should there be an explicit statement that the resolver must follow
CNAME and DNAME records?  That seems to be required by RFC 6698
section A.2.1, but that requirement is buried rather deeply.  Also,
is
CNAME following required?  My vague understanding is that CNAME can
only be used to alias host names, and SMIMEA records are not for host
names (contrasting with the DANE records for TLS) -- though the
grandparent node of any SNAMEA is a host name.

Also, some adjustments of the resolution process of RFC 6698 re CNAME
records were made in RFC 7671, but this draft only mentions 7671 in
passing, in the introduction.  It seems that it should be noted that
7671 contains a lot of operational information about DANE.

1.  Introduction

   There are other requirements on the MUA, such as
   associating the identity in the certificate with that of the
message,
   that are out of scope for this document.

"that of the message" isn't quite right, as "that" is parallel to
"the
identity", and the message doesn't itself have an identity.  More
accurate would be "the purported sender of the message", as was used
in 3rd sentence of the paragraph.

2.  The SMIMEA Resource Record

   ... the semantics are also the same except
   where RFC 6698 talks about TLS at the target protocol for the
   certificate information.

s/TLS at/TLS as/

3.  Location of the SMIMEA Record

   The DNS does not allow the use of all characters that are
supported
   in the "local-part" of email addresses as defined in [RFC5322] and
   [RFC6530].

I don't have the full background on this.  My memory ends at RFC
1035:

    Although labels can contain any 8 bit values in octets that make
up a
    label, it is strongly recommended that labels follow the
preferred
    syntax described elsewhere in this memo, which is compatible with
    existing host naming conventions.

I suspect there is by now a defined way to have "UTF-8 labels". 
Given
that this draft doesn't use such a mechanism, there's probably a
discussion out there why just using a UTF-8 string as a label doesn't
work.  It would be helpful to put a reference to that discussion
here,
because the mechanism in the draft is doing a lot of work to avoid
the
seemingly obvious mechanism.

   2.  The local-part is first canonicalized using the following
rules.
       If the local-part is unquoted, any whitespace (CFWS) around
dots
       (".") is removed.  Any enclosing double quotes are removed. 
Any
       literal quoting is removed.

I think this could be more exactly expressed along the following
lines.  Given the costs of not having this implemented exactly the
same way in all implementations, it's probably worth the extra words.

   2.  The local-part is first canonicalized using the following
       rules.  If the local-part is unquoted, any whitespace (CFWS)
       around dots (".") is removed.  If the local-part is quoted,
the
       enclosing double quotes, contained FWS, and the initial
       backslashes of quoted-pairs are removed.  (The obsolete
       local-part format obs-local-part is canonicalized similarly:
       CFWS around dots is removed and any word component that is a
       quoted-string is canonicalized as if it was a separate
       local-part.)

--

   4.  The local-part is hashed using the SHA2-256 [RFC5754]
algorithm,
       with the hash truncated to 28 octets and represented in its
       hexadecimal representation, to become the left-most label in
the
       prepared domain name.

Why use "SHA2-256 [RFC5754] algorithm, with the hash truncated to 28
octets" rather than "SHA2-224 [RFC5754]"?  (The two aren't the same,
because SHA-224 has a different IV than SHA2-256, but they seem to
have the same security properties.)  Is this because implementations
will already implement SHA2-256 (for matching type 1)?

You probably want to specify hexadecimal case here.  DNS is
considered
to be case-insensitive, but it's probably unwise to depend on that
fact.  (Or is this known not to be a problem in DNS?)

7.  Certificate Size and DNS

   The algorithm type and key
   size of certificates should not be modified to accommodate this
   section.

The term "algorithm type" is not defined; what is meant here?  Also,
"of certificates" seems awkward; the encryption/signing algorithms
and
keys exist prior to the certificate which vouches for them.  Perhaps:

   A user's S/MIME encryption/signing algorithms and keys should not
   be changed solely to reduce DNS RR sizes.

9.  Security Considerations

   If an obtained S/MIME certificate is revoked or expired, that
   certificate MUST NOT be used, even if that would result in sending
a
   message in plaintext.

Shouldn't this be moved to section 6?  This seems to be a
specification, but it is not contained in the definition of the
semantics.  The "security considerations" section is where you would
see the explanation of the reason for this specification.

[END]



From nobody Sun Feb 26 13:09:56 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B64B812940D; Sun, 26 Feb 2017 13:09:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 13:09:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/TavFJgdmgLzN3izJFR5hXy5gRos>
Cc: draft-ietf-lmap-information-model.all@ietf.org, ietf@ietf.org, lmap@ietf.org
Subject: [Gen-art] Review of draft-ietf-lmap-information-model-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 21:09:51 -0000

Reviewer: Russ Housley
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-lmap-information-model-17
Reviewer: Russ Housley
Review Date: 2017-02-26
IETF LC End Date: 2017-03-08
IESG Telechat date: Unknown

Summary: Ready

Major Concerns:

Section 3.1 says that the pre-configuration information contains
the certificate of the Controller or the certificate of the CA
which issued the certificate for the Controller.  Section 3.1.1
includes ma-preconfig-credentials.  Are these the same?

Section 6 says that secure communication channels are needed.  This
means
that some components of this system (at least the Controller) must
have
secret keys or private keys.  I think that Section 6 should talk
about
which components of this system have keys and the consequences if the
keys are not well protected.

Minor Concerns:

The Introduction in RFC 7594 says: "There is a desire to be able
to coordinate the execution of broadband measurements and the
collection of measurement results across a large scale set of
Measurement Agents (MAs)."  The Fact that LMAP is about broadband
measurements should be stated in the first paragraph of the
Introduction of this document.

Nits:

In Section 3, the reason for the 6 categories should probably be
placed before the list instead of several paragraphs later.

In 3.1: s/If the MA ID is not provided at this stage then/
         /If the MA ID is not provided at this stage, then/



From nobody Sun Feb 26 17:22:55 2017
Return-Path: <mnot@mnot.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73551129A5D for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 17:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdAhykpgKn6x for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 17:22:51 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2917129A41 for <gen-art@ietf.org>; Sun, 26 Feb 2017 17:22:50 -0800 (PST)
Received: from [192.168.3.104] (unknown [124.189.98.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9BB3C22E1F3; Sun, 26 Feb 2017 20:22:37 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <148807201447.969.8886471079003742158.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2017 12:22:34 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD581639-035F-4C57-9DBC-9254658374D1@mnot.net>
References: <148807201447.969.8886471079003742158.idtracker@ietfa.amsl.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Il1EefELlg04hZgd5--bGeGADvw>
Cc: gen-art@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: [Gen-art] Review of draft-ietf-httpbis-http2-encryption-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 01:22:53 -0000

[ editor hat ]

That all seems reasonable to me; see:

  https://github.com/httpwg/http-extensions/commit/ca56fd8365
  https://github.com/httpwg/http-extensions/commit/31c11b4683

Will incorporate into the next draft when we issue.

Thanks!


> On 26 Feb 2017, at 12:20 pm, Brian Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> Reviewer: Brian Carpenter
> Review result: Ready with Issues
>=20
> Gen-ART Last Call review of draft-ietf-httpbis-http2-encryption-10
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-httpbis-http2-encryption-10.txt
> Reviewer: Brian Carpenter
> Review Date: 2017-02-26
> IETF LC End Date: 2017-03-06
> IESG Telechat date: 2017-03-16=20
>=20
> Summary: Ready with issues
> --------
>=20
> Comments:
> ---------
>=20
> Note: Category is Experimental.
>=20
> Quoting the writeup:
>=20
> 'The primary concern voiced by dissenters has been that widespread
> deployment might provide a false sense of security, slowing the
> adoption of "real" HTTPS or confusing users."'
>=20
> FWIW, I share that concern, even with the tag 'Experimental.'
>=20
> Major issue:=20
> ------------
>=20
> The Abstract should definitely state the above concern. At the
> moment,
> it could easily mislead the reader about the value of the solution.
> I'd like to see the phrase "it is vulnerable to active attacks" in
> the Abstract.
>=20
> Minor issue:
> ------------
>=20
>> 4.4.  Confusion Regarding Request Scheme
> ...
>> Therefore, servers need to carefully examine the use of such
> signals
>> before deploying this specification.
>=20
> What does "servers" really mean here? I think it means "implementers
> of server code", or maybe "operators of servers"?
>=20
> Nits:
> -----
>=20
>> 4.1.  Security Indicators
>>=20
>>  User Agents MUST NOT provide any special security indicia when an
>=20
> 'Indicia' is a real word, but I think it's unknown to at least 99% of
> English speakers. Why not 'indicators' again?
>=20
>=20
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Sun Feb 26 17:53:10 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C911129A82 for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 17:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ToMFNN-qi97d for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 17:53:08 -0800 (PST)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7482129A7F for <gen-art@ietf.org>; Sun, 26 Feb 2017 17:53:07 -0800 (PST)
Received: by mail-pf0-x22f.google.com with SMTP id 89so1730123pfi.3 for <gen-art@ietf.org>; Sun, 26 Feb 2017 17:53:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=p2LJOM+UCCrn2rALYAKRhTDFX5EO/k8PwX/T8vujqgU=; b=aLmvWswcg9yJCcITdnQIGmbqiIxqLM9oPlzgGXbq1ev38Aad204fGup6UrHSVDwkk0 wtzJr2Xis1STbsIyY4Z4jf6kw3Zyj+4v24vG18CPr43N+LHqq6VQWLTosxSXqqvkmwHE sVj+a2QJ4i/5BKrQzmAny+VVpKAbZc75wIUQcUkZQQg7xuIX7qKCiZAQtY1zJuQfBmeV TfZMA+ZYpGNZZXNibf/4g/TUlNRaklJfkMdjU+i/6LRuB3tq0zvFv5zrHnbuc0waBXsP mjezvBmQ0NIl3zQFv8BS9MyNuAlnxN4++2zo0mBGH+ftCxYC4BW1NRVBK4jtH4Mr+PI/ 84Ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=p2LJOM+UCCrn2rALYAKRhTDFX5EO/k8PwX/T8vujqgU=; b=kHiQco6FqUf7CyVDaVwhCDe/bNp9K1Y7ZNHni6hXirnRbRjm0xvmqCfcb0t/quOVPa clHuY6RhunDZI0l5Jia45jh/r2rllIyyhhk/bHtwmhhhPusmAVgtnSQqaHizad/Ab+hL 2UKDjo9CBQd7ZbcMlRzD+Wrh5zVBPz4/zoYrwjNyLIaw727Pmnrq0/uGTkS6falvh5XV qvN9saQYBJfJNEuVwg00oumSkavangZ7b8uT6hSYKnUmfbshFG4RgXnuUMGlQ/c/2LEd CxfUOQtBJPlEn9zagXZiECTFHcCnf72paEJ+qeGhMdjnBCyeE/9LyghxGOioM5g3Hbma xYrw==
X-Gm-Message-State: AMke39l30ZtLxWOpC/J8DxwbiwdubwZHTxk+EVMlStIAY385XOg1cyzp7X+YI8htae/51A==
X-Received: by 10.98.210.133 with SMTP id c127mr17459191pfg.83.1488160387508;  Sun, 26 Feb 2017 17:53:07 -0800 (PST)
Received: from ?IPv6:2406:e007:521c:1:28cc:dc4c:9703:6781? ([2406:e007:521c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 143sm26694057pgb.66.2017.02.26.17.53.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Feb 2017 17:53:06 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>
References: <148807201447.969.8886471079003742158.idtracker@ietfa.amsl.com> <DD581639-035F-4C57-9DBC-9254658374D1@mnot.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3e2da9c8-5aa4-ce90-32ae-ff3846e0cbe4@gmail.com>
Date: Mon, 27 Feb 2017 14:53:02 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <DD581639-035F-4C57-9DBC-9254658374D1@mnot.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/a1-62g7GTdCENmQurMO1QjJ_Ig8>
Cc: gen-art@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: [Gen-art] Review of draft-ietf-httpbis-http2-encryption-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 01:53:09 -0000

Looks good to me, thanks.

Regards
   Brian

On 27/02/2017 14:22, Mark Nottingham wrote:
> [ editor hat ]
> 
> That all seems reasonable to me; see:
> 
>   https://github.com/httpwg/http-extensions/commit/ca56fd8365
>   https://github.com/httpwg/http-extensions/commit/31c11b4683
> 
> Will incorporate into the next draft when we issue.
> 
> Thanks!
> 
> 
>> On 26 Feb 2017, at 12:20 pm, Brian Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> Reviewer: Brian Carpenter
>> Review result: Ready with Issues
>>
>> Gen-ART Last Call review of draft-ietf-httpbis-http2-encryption-10
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-httpbis-http2-encryption-10.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2017-02-26
>> IETF LC End Date: 2017-03-06
>> IESG Telechat date: 2017-03-16 
>>
>> Summary: Ready with issues
>> --------
>>
>> Comments:
>> ---------
>>
>> Note: Category is Experimental.
>>
>> Quoting the writeup:
>>
>> 'The primary concern voiced by dissenters has been that widespread
>> deployment might provide a false sense of security, slowing the
>> adoption of "real" HTTPS or confusing users."'
>>
>> FWIW, I share that concern, even with the tag 'Experimental.'
>>
>> Major issue: 
>> ------------
>>
>> The Abstract should definitely state the above concern. At the
>> moment,
>> it could easily mislead the reader about the value of the solution.
>> I'd like to see the phrase "it is vulnerable to active attacks" in
>> the Abstract.
>>
>> Minor issue:
>> ------------
>>
>>> 4.4.  Confusion Regarding Request Scheme
>> ...
>>> Therefore, servers need to carefully examine the use of such
>> signals
>>> before deploying this specification.
>>
>> What does "servers" really mean here? I think it means "implementers
>> of server code", or maybe "operators of servers"?
>>
>> Nits:
>> -----
>>
>>> 4.1.  Security Indicators
>>>
>>>  User Agents MUST NOT provide any special security indicia when an
>>
>> 'Indicia' is a real word, but I think it's unknown to at least 99% of
>> English speakers. Why not 'indicators' again?
>>
>>
>>
>>
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> 


From nobody Mon Feb 27 03:41:17 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCF1129E08; Mon, 27 Feb 2017 03:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-wHbPWzm6pp; Mon, 27 Feb 2017 03:41:14 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990C1129E09; Mon, 27 Feb 2017 03:41:14 -0800 (PST)
Received: from givry.fdupont.fr (localhost [IPv6:::1]) by givry.fdupont.fr (8.14.7/8.14.7) with ESMTP id v1RBUZaY065404; Mon, 27 Feb 2017 12:30:35 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201702271130.v1RBUZaY065404@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 27 Feb 2017 12:30:35 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nH9OWFCc0a-L7qKxA4qoNBbaQq0>
Cc: draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org
Subject: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 11:41:16 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dmm-lma-controlled-mag-params-03.txt
Reviewer: Francis Dupont
Review Date: 20170217
IETF LC End Date: 20170224
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: 
 - ToC page 2 and 9 (title) page 8: Acknowledgements -> Acknowledgments

 - 1 page 2: you must expand the abbrevs at first use in the body of
  the document: the abstract is not a part of the body.

 - 1 page 2: singaling -> signaling

 - 3 page 3: suboptions -> sub-options
  (because the dash was at all other uses)

 - 3 page 4: the wording "The sub-options are optional" is ambiguous:
  it can mean that there is no mandatory sub-options or that the
  field can be empty. Obviously it is the first according to the
  section 3 intro "MUST contain one or more".

 - 3.1 page 4: Binding Refresh Control Sub-Option ->
  Binding Re-registration Control Sub-Option
  (it is the official name of the option cf section 6)

 - authors' addresses page 12: China -> P.R. China or ISO 3166 CN
  BTW I have a question about the "Kansas": I can understand
  to put only the state for California or Texas but Kansas? (:-)

Regars

Francis.Dupont@fdupont.fr


From nobody Mon Feb 27 10:09:53 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0767C12A285; Mon, 27 Feb 2017 10:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRr8EP-hJT4K; Mon, 27 Feb 2017 10:09:50 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 940FC12A2B7; Mon, 27 Feb 2017 10:09:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1913; q=dns/txt; s=iport; t=1488218990; x=1489428590; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=agMN42CGsMGNFyeFonzdj0qcsZdIlflcXnzwbIBzYkc=; b=SMd7pSv0QMnTgk629qhFiyPVYraX6m63Wwfn5qF2YzF+k6yUmSgUv4Ph ZlL+OS0cUH9mIxm8/hVYrV+qaz0h7yCZXn7MQxmxL2IMu4ecIyCB5+Ehd e3DhR2OkNU7XhAayS+1dj9e3FFnw0KRkmwy8RLhLMijoQt/wRf2exKT7G s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAQDVarRY/40NJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1BhgQkHjVyRYZU1gg0qhXgCgiI/GAECAQEBAQEBAWIohHEGJxM?= =?us-ascii?q?/EAIBCBAEIhAyJQIEAQ0FiXQOskI6iycBAQEBAQEBAQEBAQEBAQEBAQEBAQEYB?= =?us-ascii?q?YZMhG+FDIUtAQSPUYYchjEBhnOLM4F7hSCJfZMwAR84gQFUFRiGc3WJDYENAQE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.35,215,1484006400"; d="scan'208";a="390378674"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Feb 2017 18:09:49 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v1RI9nfY004028 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 27 Feb 2017 18:09:49 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 27 Feb 2017 12:09:49 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Mon, 27 Feb 2017 12:09:49 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
Thread-Index: AQHSkO5qat2SkL7umkCHWACoOXHlo6F9BfYA
Date: Mon, 27 Feb 2017 18:09:48 +0000
Message-ID: <D4D9AAD0.25EB24%sgundave@cisco.com>
References: <201702271130.v1RBUZaY065404@givry.fdupont.fr>
In-Reply-To: <201702271130.v1RBUZaY065404@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6FA9B119058DE247BF5F0D1D3A925840@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1_AfarqIJBQ5Tl5o5fUP42Z11R0>
Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" <draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 18:09:52 -0000

Thanks Francis.

On 2/27/17, 3:30 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>I am the assigned Gen-ART reviewer for this draft. The General Area
>Review Team (Gen-ART) reviews all IETF documents being processed
>by the IESG for the IETF Chair.  Please treat these comments just
>like any other last call comments.
>
>For more information, please see the FAQ at
>
><https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
>Document: draft-ietf-dmm-lma-controlled-mag-params-03.txt
>Reviewer: Francis Dupont
>Review Date: 20170217
>IETF LC End Date: 20170224
>IESG Telechat date: unknown
>
>Summary: Ready
>
>Major issues: None
>
>Minor issues: None
>
>Nits/editorial comments:
> - ToC page 2 and 9 (title) page 8: Acknowledgements -> Acknowledgments
>
> - 1 page 2: you must expand the abbrevs at first use in the body of
>  the document: the abstract is not a part of the body.
>
> - 1 page 2: singaling -> signaling
>
> - 3 page 3: suboptions -> sub-options
>  (because the dash was at all other uses)
>
> - 3 page 4: the wording "The sub-options are optional" is ambiguous:
>  it can mean that there is no mandatory sub-options or that the
>  field can be empty. Obviously it is the first according to the
>  section 3 intro "MUST contain one or more".


This container is for carrying one or more sub-options, but inclusion of
any specific sub-option is optional.
DJ can reword this to clarify this more clearly.

Ack to other comments.


Sri

>
> - 3.1 page 4: Binding Refresh Control Sub-Option ->
>  Binding Re-registration Control Sub-Option
>  (it is the official name of the option cf section 6)
>
> - authors' addresses page 12: China -> P.R. China or ISO 3166 CN
>  BTW I have a question about the "Kansas": I can understand
>  to put only the state for California or Texas but Kansas? (:-)
>
>Regars
>
>Francis.Dupont@fdupont.fr


From nobody Mon Feb 27 10:25:59 2017
Return-Path: <dhpatki@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5334312A285; Mon, 27 Feb 2017 10:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-03OlTp_GsC; Mon, 27 Feb 2017 10:25:56 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FD8312999E; Mon, 27 Feb 2017 10:25:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6382; q=dns/txt; s=iport; t=1488219956; x=1489429556; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HMXT6q26TsgaLIAG2CerSIlZYSmjdWUk8ERl36nLC1U=; b=kBfyVpxzARYIBBg4qQy7QnL9RnIoq2U9o4YU9FJ46QmMjALi1MSvANeR aRroD8QokRH+kzGU95gmW0lIq0FNXdWTnccG1OtlTvxQUTnOyQd1T3Ola 748PcxczugtbVq3WBVbgBYM2FsWba9lQMI+BDoTBxraT3Ks1RD5HGkM1d M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AWAQCdbrRY/4kNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm5iYYEJjWORYZAJhSyCDSqFeAKCIz8YAQIBAQEBAQEBYiiEcAE?= =?us-ascii?q?BAQQnBkwQAgEIEAEDAQIKJQ8jHQgCBAENBYl0DrJHOosnAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBGAWGTIRvhFsHEhiFLQWHRYgMhhyGMQGGc4szgXuFIIl9kzABHzi?= =?us-ascii?q?BAVQVGIZzdYoaAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,215,1484006400";  d="scan'208,217";a="216713934"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Feb 2017 18:25:55 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v1RIPti1005611 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 27 Feb 2017 18:25:55 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 27 Feb 2017 13:25:54 -0500
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Mon, 27 Feb 2017 13:25:54 -0500
From: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
Thread-Index: AQHSkO5qNoBjRpEVVUiQ6zglG3QDgKF9e1EA//+wrnQ=
Date: Mon, 27 Feb 2017 18:25:54 +0000
Message-ID: <vpukbdk56w4claki8ay4n6fh.1488219948704@email.android.com>
References: <201702271130.v1RBUZaY065404@givry.fdupont.fr>, <D4D9AAD0.25EB24%sgundave@cisco.com>
In-Reply-To: <D4D9AAD0.25EB24%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_vpukbdk56w4claki8ay4n6fh1488219948704emailandroidcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/633HwO7D1Hem7JSzdrzmq_W6KdI>
Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" <draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 18:25:58 -0000

--_000_vpukbdk56w4claki8ay4n6fh1488219948704emailandroidcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Francis. We will address the comments and upload in a day or two.

Regards,
Dhananjay

Sent from Samsung Mobile

-------- Original message --------
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Date:27/02/2017 23:42 (GMT+05:30)
To: Francis Dupont <Francis.Dupont@fdupont.fr>, gen-art@ietf.org
Cc: draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org
Subject: Re: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt

Thanks Francis.

On 2/27/17, 3:30 AM, "Francis Dupont" <Francis.Dupont@fdupont.fr> wrote:

>I am the assigned Gen-ART reviewer for this draft. The General Area
>Review Team (Gen-ART) reviews all IETF documents being processed
>by the IESG for the IETF Chair.  Please treat these comments just
>like any other last call comments.
>
>For more information, please see the FAQ at
>
><https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
>Document: draft-ietf-dmm-lma-controlled-mag-params-03.txt
>Reviewer: Francis Dupont
>Review Date: 20170217
>IETF LC End Date: 20170224
>IESG Telechat date: unknown
>
>Summary: Ready
>
>Major issues: None
>
>Minor issues: None
>
>Nits/editorial comments:
> - ToC page 2 and 9 (title) page 8: Acknowledgements -> Acknowledgments
>
> - 1 page 2: you must expand the abbrevs at first use in the body of
>  the document: the abstract is not a part of the body.
>
> - 1 page 2: singaling -> signaling
>
> - 3 page 3: suboptions -> sub-options
>  (because the dash was at all other uses)
>
> - 3 page 4: the wording "The sub-options are optional" is ambiguous:
>  it can mean that there is no mandatory sub-options or that the
>  field can be empty. Obviously it is the first according to the
>  section 3 intro "MUST contain one or more".


This container is for carrying one or more sub-options, but inclusion of
any specific sub-option is optional.
DJ can reword this to clarify this more clearly.

Ack to other comments.


Sri

>
> - 3.1 page 4: Binding Refresh Control Sub-Option ->
>  Binding Re-registration Control Sub-Option
>  (it is the official name of the option cf section 6)
>
> - authors' addresses page 12: China -> P.R. China or ISO 3166 CN
>  BTW I have a question about the "Kansas": I can understand
>  to put only the state for California or Texas but Kansas? (:-)
>
>Regars
>
>Francis.Dupont@fdupont.fr


--_000_vpukbdk56w4claki8ay4n6fh1488219948704emailandroidcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Thanks Francis. We will address the comments and upload in a day or tw=
o.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Dhananjay</div>
<div><br>
</div>
Sent from Samsung Mobile<br>
<br>
<div>-------- Original message --------</div>
<div>From: &quot;Sri Gundavelli (sgundave)&quot; &lt;sgundave@cisco.com&gt;=
 </div>
<div>Date:27/02/2017 23:42 (GMT&#43;05:30) </div>
<div>To: Francis Dupont &lt;Francis.Dupont@fdupont.fr&gt;, gen-art@ietf.org=
 </div>
<div>Cc: draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org </div>
<div>Subject: Re: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt=
 </div>
<div><br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Thanks Francis.<br>
<br>
On 2/27/17, 3:30 AM, &quot;Francis Dupont&quot; &lt;Francis.Dupont@fdupont.=
fr&gt; wrote:<br>
<br>
&gt;I am the assigned Gen-ART reviewer for this draft. The General Area<br>
&gt;Review Team (Gen-ART) reviews all IETF documents being processed<br>
&gt;by the IESG for the IETF Chair.&nbsp; Please treat these comments just<=
br>
&gt;like any other last call comments.<br>
&gt;<br>
&gt;For more information, please see the FAQ at<br>
&gt;<br>
&gt;&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq">https://t=
rac.ietf.org/trac/gen/wiki/GenArtfaq</a>&gt;.<br>
&gt;<br>
&gt;Document: draft-ietf-dmm-lma-controlled-mag-params-03.txt<br>
&gt;Reviewer: Francis Dupont<br>
&gt;Review Date: 20170217<br>
&gt;IETF LC End Date: 20170224<br>
&gt;IESG Telechat date: unknown<br>
&gt;<br>
&gt;Summary: Ready<br>
&gt;<br>
&gt;Major issues: None<br>
&gt;<br>
&gt;Minor issues: None<br>
&gt;<br>
&gt;Nits/editorial comments:<br>
&gt; - ToC page 2 and 9 (title) page 8: Acknowledgements -&gt; Acknowledgme=
nts<br>
&gt;<br>
&gt; - 1 page 2: you must expand the abbrevs at first use in the body of<br=
>
&gt;&nbsp; the document: the abstract is not a part of the body.<br>
&gt;<br>
&gt; - 1 page 2: singaling -&gt; signaling<br>
&gt;<br>
&gt; - 3 page 3: suboptions -&gt; sub-options<br>
&gt;&nbsp; (because the dash was at all other uses)<br>
&gt;<br>
&gt; - 3 page 4: the wording &quot;The sub-options are optional&quot; is am=
biguous:<br>
&gt;&nbsp; it can mean that there is no mandatory sub-options or that the<b=
r>
&gt;&nbsp; field can be empty. Obviously it is the first according to the<b=
r>
&gt;&nbsp; section 3 intro &quot;MUST contain one or more&quot;.<br>
<br>
<br>
This container is for carrying one or more sub-options, but inclusion of<br=
>
any specific sub-option is optional.<br>
DJ can reword this to clarify this more clearly.<br>
<br>
Ack to other comments.<br>
<br>
<br>
Sri<br>
<br>
&gt;<br>
&gt; - 3.1 page 4: Binding Refresh Control Sub-Option -&gt;<br>
&gt;&nbsp; Binding Re-registration Control Sub-Option<br>
&gt;&nbsp; (it is the official name of the option cf section 6)<br>
&gt;<br>
&gt; - authors' addresses page 12: China -&gt; P.R. China or ISO 3166 CN<br=
>
&gt;&nbsp; BTW I have a question about the &quot;Kansas&quot;: I can unders=
tand<br>
&gt;&nbsp; to put only the state for California or Texas but Kansas? (:-)<b=
r>
&gt;<br>
&gt;Regars<br>
&gt;<br>
&gt;Francis.Dupont@fdupont.fr<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_vpukbdk56w4claki8ay4n6fh1488219948704emailandroidcom_--


From nobody Mon Feb 27 11:05:45 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149F2127071; Mon, 27 Feb 2017 11:05:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukqgTzyiy8-D; Mon, 27 Feb 2017 11:05:38 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776D0126579; Mon, 27 Feb 2017 11:05:38 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id BA36458C543; Mon, 27 Feb 2017 20:05:33 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id A5AFFB0B874; Mon, 27 Feb 2017 20:05:33 +0100 (CET)
Date: Mon, 27 Feb 2017 20:05:33 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <20170227190533.GB6222@faui40p.informatik.uni-erlangen.de>
References: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/OIc18mPrc-GOgsimAQ0P_f_TLnk>
Cc: gen-art@ietf.org, draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-anima-grasp-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:05:40 -0000

Thanks, Joel!

On Sat, Feb 25, 2017 at 11:41:15AM -0800, Joel Halpern wrote:
> Reviewer: Joel Halpern
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-anima-grasp-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-25
> IETF LC End Date: 2017-03-02
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary:
> 
> Major issues:
> 
> Minor issues:
>      Section 2.2 states that routing protocols mainly consider link
> up/down and that "all nodes need a consistent view of the network
> topology".  the first seems an over-generalization, since all routing
> protocols have metrics, and almost all modern routing protocols carry
> significant additional information about the links and nodes.  The
> second statement about consistency is true for some protocols, but is
> not true for external use of BGP nor, as I understand it, for Babel. 
> So it seems again too strong a characterization.  The following
> sentence about information not normally used also seems to be at odds
> with current practice.
> 
>     Bullet 1 under SN7 in section 2.2  talks about the potential for
> circular dependence, and then says that this protocol will not provide
> any assistance for that.  given that such dependence may be complex. 
> In particular, given that these dependencies result in separate
> negotiations, the chain of efforts would continue even if the initial
> impetus has timed out.  If a single negotiation causes two dependent
> negotiations, this would seem to have the potential to cause a work
> explosion.
> 
>     It is probably considered obvious, but I did not see text
> indicating that GRASP messages with unknown MESSAGE_TYPE should be
> silently ignored.  Or any other definition of the expected behavior
> (should be logged?)
> 
> Nits/editorial comments: 
>     In section 3.1 in the definition of Technical Objective the text
> starts by saying that it is a configurable parameter or set of
> parameters.   Most further text refers to a single value, with
> indications that the value may be a complex structure.  Hence, in the
> first part of the definition, the same construction should be used,
> rather than referring to a set of values.  This gets slightly confused
> when section 3.10.4 goes back to talking about multiple parameters for
> an objective.  Consistency please?
> 
>     The first paragraph of 3.5.4.1 states that upon receiving a
> discovery request, a recipient will respond, either with the data or
> with a divert.  While this is eventually true, it is misleading.  As
> 3.5.4.2 states, the recipient, if it does not have an answer, will
> relay the request in order to get an answer.  Some mention of this in
> 3.5.4.1 would seem helpful.
> 
>     Should the first line of 3.5.5 on negotiation include "(using
> M_REQ_NEG)"?
> 

-- 
---
tte@cs.fau.de


From worley@alum.mit.edu  Sun Feb 26 16:44:44 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02B5E129A2B for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 16:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPeOeTlXtElH for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2017 16:44:43 -0800 (PST)
Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A6A129A28 for <gen-art@ietf.org>; Sun, 26 Feb 2017 16:44:42 -0800 (PST)
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-10v.sys.comcast.net with SMTP id i9QUcntpLOhhfi9QgcRTm1; Mon, 27 Feb 2017 00:44:42 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-15v.sys.comcast.net with SMTP id i9QecmVNWPFGLi9QfcMk9q; Mon, 27 Feb 2017 00:44:42 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1R0iedr001364; Sun, 26 Feb 2017 19:44:40 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1R0idYL001361; Sun, 26 Feb 2017 19:44:39 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
In-Reply-To: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com> (worley@ariadne.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 26 Feb 2017 19:44:39 -0500
Message-ID: <87innwmphk.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfJAil5laMlQoI7AP1qZuHwqg5jLsSsUL1K2Ow0SNFoDlRfczxl73mYvnFRc/cOJfaQhysCFkoVkD/YJI/Z2KT5sg0NDFI1nWUOA/kx8dRm/MOAPe2JRL FSgRBac5rdEJDzqILr3mola625uX/msiC2/GFhkRmX66pt4O8WVRka6WSm3ZL7uC/LY7IFtn9tKlIfnFd3a95tzi2QLilR9Js1++xL1/gLLLKUoEdmo9/k7p dY/0mshlajXHLI3/LO5t5A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/fV6TLFl33diOZLnWD3LTwl8By3w>
Subject: Re: [Gen-art] Review of draft-ietf-dane-smime-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:20:36 -0000

Dale Worley <worley@ariadne.com> in his review:
> 2. Presumably it was deliberate not to have the first label for an
> SNAMEA record be the canonical UTF-8 string for the local-part, even
> though the DNS architecture (RFC 1035) seems to admit binary labels.

> 3.  Location of the SMIMEA Record
>
>    The DNS does not allow the use of all characters that are supported
>    in the "local-part" of email addresses as defined in [RFC5322] and
>    [RFC6530].
>
> I don't have the full background on this.  My memory ends at RFC
> 1035:
>
>     Although labels can contain any 8 bit values in octets that make up a
>     label, it is strongly recommended that labels follow the preferred
>     syntax described elsewhere in this memo, which is compatible with
>     existing host naming conventions.
>
> I suspect there is by now a defined way to have "UTF-8 labels". Given
> that this draft doesn't use such a mechanism, there's probably a
> discussion out there why just using a UTF-8 string as a label doesn't
> work.  It would be helpful to put a reference to that discussion here,
> because the mechanism in the draft is doing a lot of work to avoid the
> seemingly obvious mechanism.

>From draft-ietf-dane-smime-15:

> 9.2.  Email Address Information Leak
> 
>    The hashing of the local-part in this document is not a security
>    feature.  Publishing SMIMEA records will create a list of hashes of
>    valid email addresses, which could simplify obtaining a list of valid
>    email addresses for a particular domain.  It is desirable to not ease
>    the harvesting of email addresses where possible.
> 
>    The domain name part of the email address is not used as part of the
>    hash so that hashes can be used in multiple zones deployed using
>    DNAME [RFC6672].  This makes it slightly easier and cheaper to brute-
>    force the SHA2-256 hashes into common and short local-parts, as
>    single rainbow tables [Rainbow] can be re-used across domains.  This
>    can be somewhat countered by using NSEC3.

After thinking about this more, it seems to me that the draft is
suffering from conflicting requirements.  On one hand, it wants to not
have the SMIMEA records provide a complete list of local-parts for the
domain name.  On the other hand, simply hashing the local-parts does not
provide enough protection of the local-parts because one dictionary can
be used to attack every domain that uses SMIMEA.  And hashing the
local-parts with the domain name makes it impossible to present the same
set of SMIMEA records for several domain names (that are e-mail
equivalent) using DNAME records.  This, I think, leads to justifying
using hashes as labels for the RRs even though the local-parts are
encoded in UTF-8, and could be used as labels themselves.

It seems to me the way out of this conflict is to salt the hashes of the
local-parts.  That is, each domain has a salt value of e.g. 128 bits (16
octets) which is hashed with the local-part to produce the label for the
RR.  The natural way to distribute the salt is in an RR attached to the
_smimecert domain (which ensures that several domains can use DNAME to
redirect to one tree of SMIMEA records), and it seems that an easy way
to do that is to use an SMIMEA RR with another "certificate usage" value
(presumably 4) to specify that the "certificate association data" field
holds the salt value:

    $origin example.com.

    ; salt
    _smimecert IN SMIMEA 4 0 0 0f215f3ab4a8bd21b831c8316379d5b0
    ; hugh@example.com
    51dfb169b7e8f5eeb4c853bf2cc2d9481cb6e9f3bd156afeb3b1cf42._smimecert (
        IN SMIMEA 0 0 1 
        d2abde240d7cd3ee6b4b28c54df034b97983a1d16e8a410e4561cb106618e971 )

It would even be upward-compatible from the current system if we defined
that if there was no SMIMEA record for the _smimecert domain, then the
hash is unsalted.

Dale


From nobody Mon Feb 27 12:21:31 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E42212A316; Mon, 27 Feb 2017 12:21:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148822688424.13746.15775745274859586475.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2017 12:21:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0CEgmOL1dgCKnQW3-B1poLiea5A>
Cc: mpls@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-mpls-residence-time-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 20:21:24 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-residence-time-14
Reviewer: Robert Sparks
Review Date: 2017-02-27
IETF LC End Date: 2017-01-17
IESG Telechat date: 2017-03-02

Summary: (Still) Ready.

My comments have been addressed.

There were some fairly big changes for a document in IETF LC that came
in with this version
based on feedback from the call for review from several other working
groups.  The new text
looks ok to me.



From nobody Mon Feb 27 20:16:11 2017
Return-Path: <dhpatki@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6660D1293E3; Mon, 27 Feb 2017 20:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHgkM-u4DtEB; Mon, 27 Feb 2017 20:16:07 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3A3B120726; Mon, 27 Feb 2017 20:16:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29555; q=dns/txt; s=iport; t=1488255366; x=1489464966; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=beLklTvxOsqzNlJsaVdLCXnN9/k4PNEEdfzyNUB2VXk=; b=U65mGzOLaTQDmUizNfHlbKj4otprNR3JcXH0BhbqDPgSC+eVwJpjG708 6Mq8JFRMTlpCTbF8I9CS1WYJHf4jFoi+Dp+YyO8OGj2Sqdj23pvLTOQHP 5dvFLly/QCs/OLwedUJ8I73kpnpS3qjFI2e0sOT1dEzU44SiUENhNIG6s o=;
X-Files: draft-ietf-dmm-lma-controlled-mag-params-04.txt.pdf : 17791
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C9AQC0+LRY/4wNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1BhgQkHg1SKCJFCH4gMjSmCDSqFeAIaggo/GAECAQEBAQEBAWI?= =?us-ascii?q?ohHABAQEEIwQeNAwEAgEIEAEDAQIrAgICGAcRHQgCBAENBQ6JTgMVDrA2gWw6h?= =?us-ascii?q?0QNC4NdAQEBAQEBAQEBAQEBAQEBAQEBAQEBDgoFhkyCBQiCYoJRgVURASMZGIJ?= =?us-ascii?q?OLoIxBY9RiwKBEToBg3aCfYMkg26EIYF7hSCJfYpKiGYBHzgSZwhUFRg3ATgBh?= =?us-ascii?q?gJ1AYd5gSGBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,217,1484006400";  d="pdf'?scan'208";a="389593091"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Feb 2017 04:16:05 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v1S4G5d8017378 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Feb 2017 04:16:05 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 27 Feb 2017 23:16:04 -0500
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1210.000; Mon, 27 Feb 2017 23:16:04 -0500
From: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
Thread-Index: AQHSkO5qNoBjRpEVVUiQ6zglG3QDgKF+gOQA
Date: Tue, 28 Feb 2017 04:16:04 +0000
Message-ID: <11C3DA1E-287F-40FB-8900-8C74F9D6A51A@cisco.com>
References: <201702271130.v1RBUZaY065404@givry.fdupont.fr>
In-Reply-To: <201702271130.v1RBUZaY065404@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.36.150]
Content-Type: multipart/mixed; boundary="_002_11C3DA1E287F40FB89008C74F9D6A51Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/LV0AmQNMfg3xR_wgXPdm1aJn1P4>
Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" <draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 04:16:10 -0000

--_002_11C3DA1E287F40FB89008C74F9D6A51Aciscocom_
Content-Type: text/plain; charset="utf-8"
Content-ID: <AC20D8E40CE4224DB43D9F3267299074@emea.cisco.com>
Content-Transfer-Encoding: base64

SGkgRnJhbmNpcywNCg0KUGxlYXNlIHNlZSBpbmxpbmUgcmVzcG9uc2VzLiBBbHNvLCBwbGVhc2Ug
ZmluZCBhdHRhY2hlZCB2ZXJzaW9uIDA0IG9mIHRoZSBkcmFmdCBhdHRhY2hlZCB0byB0aGlzIGVt
YWlsLiBJIHdpbGwgdXBsb2FkIHRoZSBuZXcgdmVyc2lvbiBvbmNlIHlvdSBhcHByb3ZlIHRoZSBy
ZXdvcmsuIE9yIHdvdWxkIHlvdSB3YW50IHRoZSB1cGRhdGVkIGRyYWZ0IHRvIGJlIHVwbG9hZGVk
IGZpcnN0PyBMZXQgbWUga25vdyBpZiB5b3UgaGF2ZSBhbnkgZnVydGhlciBjb21tZW50cy4NCi0t
DQpUaGFua3MsDQpEaGFuYW5qYXkNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogRnJhbmNpcyBEdXBvbnQgPEZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnI+DQpEYXRlOiBNb25k
YXksIDI3IEZlYnJ1YXJ5IDIwMTcgYXQgNTowMCBQTQ0KVG86ICJnZW4tYXJ0QGlldGYub3JnIiA8
Z2VuLWFydEBpZXRmLm9yZz4NCkNjOiAiZHJhZnQtaWV0Zi1kbW0tbG1hLWNvbnRyb2xsZWQtbWFn
LXBhcmFtcy5hbGxAaWV0Zi5vcmciIDxkcmFmdC1pZXRmLWRtbS1sbWEtY29udHJvbGxlZC1tYWct
cGFyYW1zLmFsbEBpZXRmLm9yZz4NClN1YmplY3Q6IHJldmlldyBvZiBkcmFmdC1pZXRmLWRtbS1s
bWEtY29udHJvbGxlZC1tYWctcGFyYW1zLTAzLnR4dA0KUmVzZW50LUZyb206IDxhbGlhcy1ib3Vu
Y2VzQGlldGYub3JnPg0KUmVzZW50LVRvOiA8ZGhwYXRraUBjaXNjby5jb20+LCA8c2d1bmRhdmVA
Y2lzY28uY29tPiwgPGpvbmdoeW91a0BzbXUuYWMua3I+LCA8ZnVxaWFvMUBvdXRsb29rLmNvbT4s
IDxseWxlLnQuYmVydHpAc3ByaW50LmNvbT4sIDxqb3VuaS5ub3NwYW1AZ21haWwuY29tPiwgPG1h
eHBhc3Npb25AZ21haWwuY29tPiwgPHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20+LCA8dGVy
cnkubWFuZGVyc29uQGljYW5uLm9yZz4sIERhcGVuZyBMaXUgPG1heC5sZHBAYWxpYmFiYS1pbmMu
Y29tPiwgPG1heC5sZHBAYWxpYmFiYS1pbmMuY29tPg0KUmVzZW50LURhdGU6IE1vbmRheSwgMjcg
RmVicnVhcnkgMjAxNyBhdCA1OjExIFBNDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2
aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENClJldmlldyBUZWFtIChHZW4t
QVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQNCmJ5IHRoZSBJ
RVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0
DQpsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0
aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFj
L2dlbi93aWtpL0dlbkFydGZhcT4uDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLWRtbS1sbWEtY29u
dHJvbGxlZC1tYWctcGFyYW1zLTAzLnR4dA0KUmV2aWV3ZXI6IEZyYW5jaXMgRHVwb250DQpSZXZp
ZXcgRGF0ZTogMjAxNzAyMTcNCklFVEYgTEMgRW5kIERhdGU6IDIwMTcwMjI0DQpJRVNHIFRlbGVj
aGF0IGRhdGU6IHVua25vd24NCg0KU3VtbWFyeTogUmVhZHkNCg0KTWFqb3IgaXNzdWVzOiBOb25l
DQoNCk1pbm9yIGlzc3VlczogTm9uZQ0KDQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czogDQogLSBU
b0MgcGFnZSAyIGFuZCA5ICh0aXRsZSkgcGFnZSA4OiBBY2tub3dsZWRnZW1lbnRzIC0+IEFja25v
d2xlZGdtZW50cw0KDQpbRGhhbmFuamF5XSBCb3RoIHNwZWxsaW5ncyBhcmUgdmFsaWQuIEkgc2Vl
IHRoZSBmb3JtZXIgaW4gbWFueSBSRkNzLiBTbyBJIGxlZnQgaXQgYXMgaXQgaXMuDQoNCiAtIDEg
cGFnZSAyOiB5b3UgbXVzdCBleHBhbmQgdGhlIGFiYnJldnMgYXQgZmlyc3QgdXNlIGluIHRoZSBi
b2R5IG9mDQogIHRoZSBkb2N1bWVudDogdGhlIGFic3RyYWN0IGlzIG5vdCBhIHBhcnQgb2YgdGhl
IGJvZHkuDQoNCltEaGFuYW5qYXldIENvcnJlY3RlZA0KDQogLSAxIHBhZ2UgMjogc2luZ2FsaW5n
IC0+IHNpZ25hbGluZw0KDQpbRGhhbmFuamF5XSBDb3JyZWN0ZWQNCg0KIC0gMyBwYWdlIDM6IHN1
Ym9wdGlvbnMgLT4gc3ViLW9wdGlvbnMNCiAgKGJlY2F1c2UgdGhlIGRhc2ggd2FzIGF0IGFsbCBv
dGhlciB1c2VzKQ0KDQpbRGhhbmFuamF5XSBDb3JyZWN0ZWQNCg0KIC0gMyBwYWdlIDQ6IHRoZSB3
b3JkaW5nICJUaGUgc3ViLW9wdGlvbnMgYXJlIG9wdGlvbmFsIiBpcyBhbWJpZ3VvdXM6DQogIGl0
IGNhbiBtZWFuIHRoYXQgdGhlcmUgaXMgbm8gbWFuZGF0b3J5IHN1Yi1vcHRpb25zIG9yIHRoYXQg
dGhlDQogIGZpZWxkIGNhbiBiZSBlbXB0eS4gT2J2aW91c2x5IGl0IGlzIHRoZSBmaXJzdCBhY2Nv
cmRpbmcgdG8gdGhlDQogIHNlY3Rpb24gMyBpbnRybyAiTVVTVCBjb250YWluIG9uZSBvciBtb3Jl
Ii4NCg0KW0RoYW5hbmpheV0gQ29ycmVjdGVkLiBSZXdvcmRlZCBhcyBmb2xsb3dzLg0KDQogICAg
4oCcTENNUCBTdWItb3B0aW9ucyBhcmUgZGVzY3JpYmVkIGluIHRoZSBiZWxvdyBzZWN0aW9ucy4g
VGhlIHN1Yi1vcHRpb25zDQogICAgIGNhbiBiZSBwcmVzZW50IGluIGFueSBvcmRlci4gSW5jbHVz
aW9uIG9mIGFueSBzcGVjaWZpYyBzdWItb3B0aW9uIGlzDQogICAgIG9wdGlvbmFsLCBidXQgYXQg
bGVhc3Qgb25lIHN1Yi1vcHRpb24gTVVTVCBiZSBwcmVzZW50LuKAnQ0KDQogLSAzLjEgcGFnZSA0
OiBCaW5kaW5nIFJlZnJlc2ggQ29udHJvbCBTdWItT3B0aW9uIC0+DQogIEJpbmRpbmcgUmUtcmVn
aXN0cmF0aW9uIENvbnRyb2wgU3ViLU9wdGlvbg0KICAoaXQgaXMgdGhlIG9mZmljaWFsIG5hbWUg
b2YgdGhlIG9wdGlvbiBjZiBzZWN0aW9uIDYpDQoNCltEaGFuYW5qYXldIENvcnJlY3RlZA0KDQog
LSBhdXRob3JzJyBhZGRyZXNzZXMgcGFnZSAxMjogQ2hpbmEgLT4gUC5SLiBDaGluYSBvciBJU08g
MzE2NiBDTg0KICBCVFcgSSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgdGhlICJLYW5zYXMiOiBJIGNh
biB1bmRlcnN0YW5kDQogIHRvIHB1dCBvbmx5IHRoZSBzdGF0ZSBmb3IgQ2FsaWZvcm5pYSBvciBU
ZXhhcyBidXQgS2Fuc2FzPyAoOi0pDQoNCltEaGFuYW5qYXldIENoYW5nZWQgQ2hpbmEgdG8gUC5S
LiBDaGluYSAodGhvdWdoIEkgZmluZCBtYW55IFJGQ3MgdGhhdCB1c2UganVzdCBDaGluYSkuIElz
IHRoZXJlIGFueXRoaW5nIHRvIGJlIGNvcnJlY3RlZCBmb3Ig4oCcS2Fuc2Fz4oCdPyA6LSkNCg0K
UmVnYXJzDQoNCkZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnINCg0KDQo=

--_002_11C3DA1E287F40FB89008C74F9D6A51Aciscocom_
Content-Type: application/pdf;
	name="draft-ietf-dmm-lma-controlled-mag-params-04.txt.pdf"
Content-Description: draft-ietf-dmm-lma-controlled-mag-params-04.txt.pdf
Content-Disposition: attachment;
	filename="draft-ietf-dmm-lma-controlled-mag-params-04.txt.pdf"; size=17791;
	creation-date="Tue, 28 Feb 2017 04:16:04 GMT";
	modification-date="Tue, 28 Feb 2017 04:16:04 GMT"
Content-ID: <15C2EC4A7E9496459265C816F34E1C56@emea.cisco.com>
Content-Transfer-Encoding: base64

JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQp4nK1Wy3LbOBC86yumcolcZVKWvBslufld3rJSSqytHOI9QOSQQkwCDADK0n79
9pDUw3aqkjhLHUSJmJ6enh6A3+goHtKRfLrvpOwNPo0p970jynvfesPmIXVfSUmnMyx4S8MRzbJe
GzOk0TGNj9/RrOz1zycT+nxFL77OY5qqcK8PZl97w2Oa3fT61yawMxyic6ey8EtotzFd1SZVSy4K
ffC6xTIpp+SDCrV/T7dB4blLPc2cSu5/AvNM+8QK1sWq0o6BcVLntQ90PDyk0dFw/PP0/orphlmw
fqmqTXHK5OW6Njn9bfSSnddh/VKsJ9fHmC7r38U6W2ijaGLnunhxjfvXTUyn7MK//0+Nt5XTJvwG
1iXPXa3cmkbjtu/AkiG4+Q7izeSEzqwJzhYFzDc5uaJb9l5bA7c7VTIc7hHfOX4/NBXTR5pDFqVl
GRWlipItUlSqPKoEwUdHf8RhJQWN3jQgJ3MfYOlNibOF9uQrTnSmExUkdcqZNuxJkeEH4hVGQygd
Ct1oRzcC3egRuY571HD3FCxNnV2tu17T9XT5Ju4y2qpJlShDc6bao/r5msJi44jCJqqgUgJhX1Im
WVhH2jxHJK9zowoNv2dYYmzQ2Rq/OiBAtjBMKklAkHIV+EGthR4UQ0wpt0vltK09VVvd5WlQUCLt
oJA9CPetIvFO1dtm3yCbteVNuLT7Aj/Zq0Tyel7qEFA3YLO6KDZkUCrTgw6LTo2dvJWzSy15mzyn
Z1Mav4UyaXv7bo8NFj/OiGY6oFp3LzqlNqlLNqHBEYE2i+nC5CiYXavfLvVM+Xu6tA7U7vrXF7PL
uwN08oMNjHgVyALFUe5sXXkqIa4qvKVUw2p6XodNV58TUE+18Y1DmArECr2kdg4rd6s6qK4sKIn0
ixCq94NBqtAF2a7ZxTIZsXX5oBkUP+hwBj9WqQnYo7iEudLGWwqlrXRZl0LM6xWMZcLi8YBKP0QA
cXUFQpwekuOqUIncAcTOvS04tIZvdduTIwBgs1sHXTLUuG78gj2zggGwOykR3crMPKfvkStjFJps
JC+xHDGFpBbH66ZlXHap0T0jYa+kNWJF5Mhxevn41SOhvufiBw3XcnPaEWb5yXEnQvfPbLV2Ol8E
8Yrektr9fddP7g7a41FshdNWMERE8WWFMRS76xTqYIOCaOD6dC428pGqA3YJcdAJmDUJRBDPbslp
/LyebWA7j185CaLR3mQ1w7Hl9drjXM5V8Sj7dDeVn7jADgp/A6SJOt80tqv7rt85NQgc886lBcQx
niONPQCCoBGcZcLHmoaEOAmuA86foyZz8zZ0SJhZVcT7B0P3+vGjt48vU5UzDf8B4sWs9xGf/wCg
erZ+ZW5kc3RyZWFtCmVuZG9iago2IDAgb2JqCjEwMTgKZW5kb2JqCjEyIDAgb2JqCjw8L0xlbmd0
aCAxMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJ2X31MiORDH3/kr+m21CjkH
VPQRXd2zCvc4pe4eVh9CpmfI7cxkTDIg//11JxkEznNFqFp2fuSTb3f6l89w3EvgmL/xV5ad3+6H
kNvOMeSd507iH0L8kSVcTumFc0j6MM06YU0C/QEMh+cwLTsHt5VDU6E7+mpE5oA+47sRXOnKGV0U
mMLd6Bs8oLVKVzARRpRICyy/eIMz0wizgv5xMjyc/tMZXMB03DmgR3UzK5QUjhfpDNxcWUi1bEqs
XA9gUqCwCAYXCpf0FOmifWwPv3SSQQuSwmDWFMWqC8LymytI0UqjZggr3RgwKp87C6JKCWedUZI3
tbBUbs53apSOiMxy+j9CrnSK9E9Z64q3BnxxRkhHZmdGl9uvQ9nYFqUqWTS09EGVdaEyRQsuH77C
WEmsyBZHHNbbSk1pATnRS4OTHpJPWk1zhKkhMIwxFwVMjF4o6y1gk8h6qPlWSgw2STcOlsIYUbkV
7RApW/sw8m1dPXq9f+ZdOxWzgmX4k45eZ1JCTrnls0+boBZ6e34B+lsn2Pdurha0ydqsKZpSVbrQ
+epDxEFUx7Rkh7evuk0Wa9tPy9usAce00U5LXcD1CznU7um7TV0Db+ONNqVwIXsQxld3E3hoZkd/
1MHsd1kna1agMe9SVamqcrjHI4O5olQJ6RlTfQMOW6zTHRb77HcUxs2Q5L2/elfXWWSdbPqLEJnK
myjnL2EUx+a7Fm6ymMb2jbWk/LnTM1Uoyo1RJefawNH/4t9ine7ospR3YeFH4wzgfK3r9B1dO/AP
sNjvnoIwkpIKMnwTDpdi9UHWRWSdcYaPvo8+Z982a0gXVNYaw5Z9zl/JcWSd08VI/qz0krpOjr4V
7Fd9XlkXdHGPGRqs5K8i6VcspvE5fvf5qBa4N3mb1fcVNvskDZIkskYNdQNjv8AoTanP2f3tDKzY
EHYLf7sLFMLkyFnxsmrj73ayOIPHg8kd/+fxkNpPXegVn1gXbCPn3PpIEgUD1WhRbLWDzXelqGAu
FtwvKWB8pdONpQbhL8qwmQjBnodgb/vU4wHNJbS1rQ0K6pPSaH4JdW5EPVeccoUOA4gly/6eM0o5
v+UMI0TXMVoFDRgg5/SDVc5FkkaFUlSCDA/2RC9UTTlDw+Jod9slYCQxVhRWExsWSCNRqrJMyaZw
jCLrGmrkcqsSSU4XS5bLVZQfWaTCl3zeAlQWhh4eBCpN+slxxssN+tLQDT2XhLeIPOeQ4PBaiKJB
78/6dXh7PaTtXuBUiTxh0BFE0nxd6RUPikTzttbahbNlv9EJOAz2cPrzYGFVTk5lTxZatCwdZpPC
F8SyLYgiFMTHA5o7Hw+5IW8NXXH6obkBKlyuDy7IZdf6/XyLpLmV7sjYkRZU6SmaNs2OAsixkdP6
ge/u+iIz+Nz40/lxf3N12k8GT352WXskMnbeOz8ZPnHA8fjpx8egtev32I6A0NptG42uCbZsCE5p
LN048qifDQ12W6q+ZkHDXURMgrNoJTnCZ9YMHZHWTomEGdJDpU07XfhQ4/FyPU86PxWRN5TcOcwN
FTxPnp36zJ4I91N1ASl2ih5sfK5fakWxSOUq5yl3kHT9nwuw8/kx4WTrPxHxetr5k77/Av2cmgFl
bmRzdHJlYW0KZW5kb2JqCjEzIDAgb2JqCjEyMTUKZW5kb2JqCjE3IDAgb2JqCjw8L0xlbmd0aCAx
OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nLVVTW/bOBC961cMcqmDxl5Lij+y
NyVxtgHs2LWVQ9HkQEu0rI1EuiSVxkDR397hh2wpDdAudpc+iBJn3ryZeRx/gX7Ph77+uWdSen8s
R5BJrw+Z98XzzSG4R1LCZYwGY/ADiDee9fEhCGE0GkNcep1bpqhgVHWvBdkowDWdRXDFmRK8KGgK
s+gvWFEpc85gQQQpKTpIbXhD16IiYg9B3x+dxn974QXEU68T9EADPFOm0EkCYSnEVJQ54wXP9qfv
vGDoDP22KR51EDjeUniie/jKRSrhZHa/ik/O7BPu5ma/nHy8v11OrvV+9SGaTg8ba4FIfmiCIB4e
zO+nzlbvjihX89lscndtgWbRJ3xouifzRXw7v4umJ5AzUNu8ppbypCqRLRBBQXFYUzTAguwEliUF
IiGlMhH5Gl/Q8/Py5irw/YvHXjNrXaB2QTR0VBQYCVHxREIlLYKO/VtRNzmjaSttF38Q+OHjmd2O
z0ePJkH9NhoMwyaxEGktBFc84QVMXhRluumNnryhjIYiHjrTq9ni4RT4TjcTkDeBkq/zIld72FKS
UtHi5+xMppgUfUm2hGU6tQ0XJTGHghZE2XNdm90xnNoSrIdjp5lR7ZZQCehGNLmeZe3CJITZuiVF
ldraYrIve7jMWZqzrO5C8sT4V0wPiTx0FpcRJlSi/Am+c1bsrT6QC3aiFqTGLbluDSZw4CQRtNAB
pSIsQe+NbeahJHWdmEkNQ9WBDPGD5F7bm6gJtoGgJ2cILGx0XX6Q1bprDaXLX39xUO7AyMgpRodf
0cQgh+Y+ah9S5BkziqtZW1eHYyhg0udO4efDvhHSIKh7i2Pm5+W/8S1441vYkomdWBDCOQxgCCMY
w8U/+eY4v+/+y5/D+WY5xvsdNRv9PqUsU1s4vNdrSSUVz1jkxvr2//Bprl6vZ8WwOojhoSNRyPrg
p/X9PyTUEMBx3eRZhYLz//zFAJnXEnPzyFXZ0YOj7CRV9UB4JkVlrtZtdBd1/TPQlznB2cEyOyFy
ZQcRhu62ZQUNKl2k0m1QsUXrtbjYJh/ZjLtrBK9wSGb2HimaUdEmQKGw0tBXNVFUSXuh6GsqNuCZ
HoI4nmpnIzI9b5zANjktUqlpDQfGeUHUU45eOAmLVmsnL7tc4CyMqqySCkKsjP6Xft37zws918JH
RJzE3kf8/QBsmDnhZW5kc3RyZWFtCmVuZG9iagoxOCAwIG9iago4ODkKZW5kb2JqCjIyIDAgb2Jq
Cjw8L0xlbmd0aCAyMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nK1VTXPTMBC9
+1fsjXSoQxy3TdpbP6EzzRAac6IcFHvtCBwpleS2YRh+OytZjp2kHBiQDx5rpaent2/XjzDoRzCw
j3+ny+Dd/QgKHQygCB6DyAXBv9IlXCS0YAzREJI8qPdEMIxhNBpDsgx6t8KgEmjCK8VyAzTuJudw
KYVRsiwxg8n5e5ih1lwKmDLFlkgbtF14g3NVMbWG4SAaHSTfgvgUkrugR6F71KieMDt4EwxPmkka
k8+zBOYIGg0YCT9QSXheoKAJkXFRABMZ8EJIRSe7gMIUOSH1CcqC3F1OpjCr5qFcGaL00NMPBz60
H9XAFEKGOlV8TohcgFkgESjlMx2ZujV9gIQmNe0ioCju0G1QUiYs65WiawljYZhYg1QZKtp9K9Ky
cvrI3AX0ClOepy0tvWEEXHtUVh7CvDLADJTItAEpsLvQS9WC+NP7raZxP6Ljb6RaEgidbe+2UeBj
zd3vT5qQ3hGn0qRLLhXdUam1TQEXuUO0JLDEJZ2pt4RRWDJDuyiBT0xxWWlYtcYwCyIjsI6TaKkU
OS8qm1BZy0+O6re0NG5x8lJzq2nWpsxx98pkmHPhQh5lVmcSYp9KVpKFLO9GlH1Z4Uj4xfVlPZJb
TynaThjTtKokz2jL+3i4ccgA9kf0ytzwlbl422yuLCGGIziGExjBGE7/Zs7zfxv+4+Nxfja1lKxX
6L7d1x2Kwix83I7WaHDFDNtc7td/5NPRuxk3zlAwPHutWXWaVEtvqxHZS7V1NQ7n3EAlNJnGucpg
gYreGU+pCqgirIWMFaJbY61F+rttI3EWck3AQWw8q9322ksOmED12W6THEDYbaC9xlchXPC6S95j
qLDg2qga3Suwfd9e470QPiBTZo5UmH9cWaf2b1UR1XJOs6SLTA0a7Qrflf6uJihSmaHb1DHMIeCL
LfQGr/Wc/RF0PNcSyzmWmd6vbJuFk2N34pSZ75ygqbmW/a5vrl9WnLoonFdFRR03jg7dv2u3NL9M
WUEd4ishXifBJ3p+A0MHEn5lbmRzdHJlYW0KZW5kb2JqCjIzIDAgb2JqCjc2OAplbmRvYmoKMjcg
MCBvYmoKPDwvTGVuZ3RoIDI4IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicrVVN
T9tAEL37V8ytoOI0jiGBSj0QChVSIlzinEoPa2fsbLF3w+4aiMSP76y9xEmaIqXFPiSa3Xnz3nz5
AbqdALr2db9p6X26HUCuvS7k3oMX1IfgftIShjFdOIWgB3HmNT4B9EIYDE4hLr2Da2FQCTT+V8Uy
A/SMxudwIYVRsihwBuPzbzBBrbkUEDHFSiQHbS9eYaIqppbQ6waDw/iXF55BPPIOwk5AL8CQixkX
OdyirzDn2ihmLIoDh0mV+DcLazr84PX6tS/BxnPcwxW4BgalTHjBzRI0HRBaEL6iyeZWypTipIYL
MIQ/uhhHrZO7M8OMi+bOBNPaZKUQXEOLIln4DUQNaouiwoIZQjG8RAWPrKhQd2pVCh3UeDqJIUEQ
kjgoJEZMkAhNiguk8NowkSLIjE42gxI1S93hNMYGHDKpSmZ2OumVtAQL+WQVuVLZMnbhzyfYYevt
sIUbuW56C0I4hhPowwBO4Wwfm5P10f/P1+G8NGWOlwuELxTxBRrDCEVu5vZ8u7/8iWHK+DGVzvq/
Ox+4FtxwVvi3SBGFLnk9Vy7gC4zZMy+rcvfxu/JZq797rnheUS+Gn/91blfJdjTrNqKu3A9vhdRU
qcXqu79/L9la3L6fcAOV0DxvJtpgTtNoiaTkRmTsFhBVmZDVjozNcEXF0TQixBk3+xrq6/i84LTt
6glDiMbX0WMfEieu4BnWKE9zbHbMOsuWmsJMoZ7DQsmUtioIxJkGI+0+YLR0Hu3yoJG+EdiysiN8
3GJoTKWY6c5G+t9orb0SU3Jhe5BWRsGWduG4aG8kJuNKG4iUfF6uij1dzEgJ3B1Ew+ndIcleZ+Vy
2PKi1EqBwgqAhKX3vsyy1xRtynxjRPaT2eDsI7NgVuVwui2mJJIsx9fG2KWlpbYmyn6BKUDEzD0/
AjTAis76cr20/UZfmPMqryhyGBzVX9rtHfwjssFPfhLiZex9p/c32GRO7WVuZHN0cmVhbQplbmRv
YmoKMjggMCBvYmoKNzMyCmVuZG9iagozMiAwIG9iago8PC9MZW5ndGggMzMgMCBSL0ZpbHRlciAv
RmxhdGVEZWNvZGU+PgpzdHJlYW0KeJytVU1v2kAQvftXvFuJGlwMBJJKPZCvthKoNHF7aXpYm8Fs
a6/J7pqAlB/fWWOCSehH1NgHo9mZN29m3iy3aPkBWu6tvnHmvbnqIzFeC4l36wXlIapPnOE0ZIdj
BG2EU28dE6DdQb9/jDDzGh+VJa3INs+1mFrwMxwNcJYrq/M0pQlGg/e4JmNkrjAWWmTEAcY5XlKk
C6FXaLeC/kH4w+ucIBx6jY4f+G0f+EBC24iE3cDhuoian+aWoQ5eeQ2H0cLTJ9hja++xdRgk6JQp
11BcGDro4gg99HGMk+fYKkavm//5Vjj3GJ6NxghXc8I7znePtWFIKrEzd149H06b5QwWIq0Xd//i
fNa5rshqoUwmy4k2zykVK9TOR2L5yMe8OJ9KJ08neimTQhO6b/+mnXZvg/DQ5Y2inFamuf4X9dUG
so3uVT9rc9keBr1mJC0KZWSieDkkeySk+TuRsbBSJZg95JVV+CGkTz6szGhXscCkbL9UMBTnamLA
O8hwAqaIY166aZHWAGkZz4RKCDeNB+OWm6bbgozl4tM0v2Ny0YptZs4TpJsD3M1Iwc4IipZ2H2gs
1BYsIlgtE66NJv5Ow3+joWf1KJNKZkVWtuRJDx73KCIeJ3FPtpwzbo1gytJwhRUXa/cw3aPm5xEV
y5KoKrKIT/Ip6o3foal309SodPkuHOvc5jGLkMU4dSoXTof4KrQUUUolqy7fmyzKPOabYJRHMpV2
hYGKZ6zm5p8COXvIg3UX9+jLdQjhBFDOeq0FV8liEwCbu+nGFdxaJ+y7U49ZGUsZl6+4zRkp669T
1KJY2Cy3ctU42hDmVYkVo23CkpMp9EIuiIesF9xJTVGeW9a7mpQmGZMTq+Xmmt0pXiiH4laV95fX
94olmVQrzY5H7dJxLOxPeQiyXLxfv1IulnPJwBgUScHL0QkOy7+rxzfPt7HTU+87I16E3md+fwFa
jAgqZW5kc3RyZWFtCmVuZG9iagozMyAwIG9iago3MjMKZW5kb2JqCjM3IDAgb2JqCjw8L0xlbmd0
aCAzOCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nKWW23LbNhCG7/kUe1d7RlZ1
SKTkUj6k4VSyVYmeaSfOZEBySaIhQRkH2Xr7LEBSpCzbjVPqwhYI/Pj3w+5C9zDoD2FgP/XfqPB+
X00hVd4AUu/eG7qXUP+JCjgPaMIHGI4gSLxqzRBGY5hOP0BQeCe+0CgF6rNLyRIN9MwXM7gohZZl
nmMMi9kfsEaleClgySQrkBYoO/EThtIwuYPRYDg9Df71xh8hmHsn4J4g4wqSnKXARcwjplGBzhDK
DUqmSY3loDQNQ5m4F+d2nkhhhWenv3nDcUdLYsqVrpY13kCZ8KzcuCFlNptS6r7dFSHGhJlcw5bl
BiEpJcnVQro1pUChBl3C3cng7rTXuLQOdMZ0o2nXd+21WuTzv3zRJjFXLCSOfVo4mjQxXQk7OL9Y
LNcmvNnoz8ikDpHpWqTd5c0Y91LQah3A/Hluz+Fqnf0ktyM/HQOt2IukrLGEMrF8sDtsmeR2kqK0
/AdC55kLylKm3bvSKEglEyanL5rTPGWi7IAAU0DoIKyOs+e+bBClladcrwai3ChKc8uUxhRQLEzs
oKSAmmyKaEZZ0G6l2dDavk2IlMmYzKnmLForu2qIq2Z1KRKemuoIe26yrbvF7TqwYdkYbW7GttgK
itDNqA6m0lZYK7VI6ECZcOex5bGhvKhjhJAp4hvu4IE5Hweb1zIZp3ySUbY7xG9TdIXdPF9rOs+A
F/gkRxsf9iiNoiMh+y5lyDhFwAtTgKZlZJBiolDoHxCmCB3RgwwliwrJZEymkfKoih4fN1zuGrTL
hb/cTvYh5jxBp/6QoejWOx42D4mJRJXBRpaRPaj155vb+aVDHmm+pTqKD6uh1aroU3TUXI3gWvXs
ZmQOWZS5EfvyXWP9mKNPUzjLV0hmhCq466m/SDLGnM6SCB6CekrSLkm4VBqW57cUfHfnhiRxLQUK
a40yJfp+ViZJw6f/ijVFV4GtJv/aD/zZ/Nu5f305u/jzW+Avrm5uAyisZmmLk3dOZI2RO4hJ/2P/
nbXwZfXp4v1oOP76bBeyuOsYj4Eu2KOF8f+AVhpvAZqz53kWBIyl+BrX1lgD+BWwi9nfL0PttE7x
C1DHo5fzdN+x/bpS34DT1eARS/plQc2UHd9EkWWQmByy/S2Bj1HGBGG8O2kHJd4bVLq+CWjLcNea
ooIm0grvTl31Ox8CH/VzohF1SCp2LXmaUu3Wxd5qHYGaDPagAHzdNIzrG9en658QrufT7SdgPGi1
mujp8iiqJmYnTAZdxeCwrXfp0g1HWpP3DtiS6e+8B7Qdy/vQea5sV6TmPzMpXUgwHvbczzF48nxZ
2sycfiXFq8D7iz4/AJiFP6tlbmRzdHJlYW0KZW5kb2JqCjM4IDAgb2JqCjEwMDUKZW5kb2JqCjQy
IDAgb2JqCjw8L0xlbmd0aCA0MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJVW
wXLbNhC98yv2VntGcU2pitzeaJuJNSNaqki30yYeD0iCEhoSYADQsf6+CxAURTlWWuogzWDx9u3b
t0t9hcsLHy7Nx31nlffzegYb5V3Cxvvq+fYQ3FdWwXWCAVfgjyEpvPaOD+MJzGZXkFTe2ZxrKjnV
724lKTTgs4gCuBFcS1GWNIco+AgxVYoJDisiSUXxgjKBH2gqGyJ3ML70Z+fJP97kV0gW3hnYJ6WQ
U8meEaKQogK9pfBMJCNpSeEuDNbJdRgkT/P7JFz/ESwwuGAcgxk//8nzJwdIMc20yT4FUcCn9Yeb
6dUvs0dgBWSCF2zTSLyG5yYDkr/A++P33f3FTbS6o0TqlBK9ploSripmy7mlJdlhsEuTbJnqGeLv
RiGuFqCottgV46xqsBJWmdrwMpLFU2SRq2PSKS2EpEBg2yWHClUkGwstOyJa0/zC5DbilA01JWok
0tPaM4rvlg+LW6NriUAYRfiwOttKRHF4KChpSn2IZBJg9mlH+oRUEXkZqqX+j1LkxSrFmyql0tS0
V+FYJzlMMuTuKKOSVpRBzkkbelye068PjYK/TnqxB4jmcTy///i0N2f8FCwWyz/D2wNzvu3GHuhH
tpwi9ZUUWmSiNKOmGLIj+kBko0GB8ye+Mb4xeAchQOq63Bm5HTIQntvfOKoXBwB4LaO1bkgJ14zn
BumGZHgQ4nDvICeagNKyyTRSxZ4xromtMt0ZuEGnMM0IVVCZZOmRDriJOiXG/uRxz+Z1esftocbU
yJwpDfQ/UTGVDdM7qI7E+yMSI4ge4sT0nb5oynNnT21G0qqGVgdRm7sOSeI8awuNbqus0kBLWiFB
VFwpkTF7/o3pbVteIyUeouetczvh45pmrGAZKcuWet/Gut+eHTvnq98GcyjaUVxTSTeoUdv2WOMA
Jbh5XB4XNOdMM1IOR/V1WNQO5I/CXq2SN47f3qPHkd9fI+gZHIGFQJUgEikrmd5BwLMtDvp352HJ
sUEZZc9GRwKr64f9Nu2NZ0ebtF7pRsMKjZ7PvgzszIrh+yjk5sswj5t0WWurvXsJmmVzMNHG3nbP
Ccft85n/+RzLmRewo2pkAxAfDWAseaKTIwdwso8W7mQLgciujS0vuF/eP/0drpftSlRWDQ5Mt2ow
npVNTvc7YU3fHdJDqOnY6rQi+gsbAWLad0r/hC81k1RB0GwanOGJP7J/AeDo+bQy/bl6RMQw8X7H
z7+qIb6UZW5kc3RyZWFtCmVuZG9iago0MyAwIG9iago5MjIKZW5kb2JqCjQ3IDAgb2JqCjw8L0xl
bmd0aCA0OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nM1WXW/iOBR9z6+46ktb
CdgG1I+ZN/ox00qlZSF9mQ+tTHITPJPY1HZK+fd77TiQANuZWa1GGx4iYvv4+Jxzb/IMJ70QTuzP
3+Mi+GNyDpkOTiALnoPQDYK/xQVcRjThAsI+RGlQrQmhP4Dz8wuIiuDoThhUAk33WrHUAF33oyFc
SWGUzHNMYDT8CFPUmksBY6ZYgbRA24kfcKZKplbQPwnPj6NvweAdRPfBEQ359TAtZ93HhbFruQAz
R7i/Go2hkDOec7MCWY0t5zyeA9duUqnE8WEQDmosLuK8TIiJRxhfDqEgQizDHsBd6h6+MMXZLEda
adfcCPvH7kUMiMAEFWY1KdonliLlWakIlYkENBowEr4chV+O3QOe0m3lwWTqWDsMro1ilvPUMGUi
XmDHDd4JbjjLJ0jDQhfc6WWHLZzHsfNG7JUXZbFnHrHyND7dTB7pQHlJ2HQ2rxu5MnqaRh5L4UIq
A2x9EkcKUCmp3AkUfsPYuKUzLhIuMnr0XKI2MKsPprEaYE1NYcnNHLRhprQ6JQiHYf+iO0GmaYMn
oRcY85RjcuhRPk8+XJ32w8HXHj3on9W2RQ3SwHItIZ5j/N1KW5u1Y9MtkqgzZMZb1c7Bm7ZVUVih
7qwNzHOyrqH9Gt1lngTutB+3TbnGnK223FtPJRvbszUwhTWhh8eHvzYmau8iNx7JKeJTDWvIX6wZ
j7VdOf9JtWzb0Mjmdon8ToV/XCFNgf/nFXLa65MfI2sqwjCOCRo+MoNLkoRk1zzBirH2IN66Jo81
LhGPkb+Q66mSxbpf0MkN46RcHaJWPW03YauJnXjpxZhgt9nw9uSz46mtLbDvCie+fEG1VNzglrxt
REUBMETaUP9THmuxecU0qj2XMZUzUd3s40ywfxorahk8FpXAzx+mqo4q0hZ3l4+vqJ+HtIm1Ud3R
qWmi02tG/T8Tsm5srM5pPWl6+/h0f03TPFIuswyTdsOd8oLnTOWrjq3Nf3zXtkKx031aCWk4/UOP
52uk3+DqXupveLnrosd6s/via4wLA7eX3XYn6laN69+a+4vOntnDDB+G+7tCNCcaiYzLAoVx/Ysr
rLxN6ftNLm1S3XIWm6qLViwPfOu5G7+ctUzffOMdgM/3qh00CdSwnELh+4qA73hxVQgJplwQCQYC
l5v8UUKIvY9hp7UnXQd7PjsbVHr+qNtp5laI074DGjPznXeAXhEs70HjunldOFWGZVZSdx+EHffJ
ClvX57E15N1XQryJgj/p9zfA1az3ZW5kc3RyZWFtCmVuZG9iago0OCAwIG9iago5NDkKZW5kb2Jq
CjUyIDAgb2JqCjw8L0xlbmd0aCA1MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4
nLVWXW/bNhR916+4yEsTVP6Qk9VxMQywk3YLGreuY+ylzQMtXUmcJVIhKXsG8uN3ScmR5DkDiqE0
5A+JPPfw3HsP/QTDfgBD+6o/w9wbLMeQaG8IiffkBe4h1B9hDrMVTbiGYASr2KvWBDC6hPH4Gla5
d34nDCqBpnerWGyAxv18CjdSGCWzDCOYT3+HB9SaSwELpliOtEDbiR9xrUqm9jAaBuOL1V/e5QRW
9945uBGhDhVfEwIXBBAaC3DZB1ilCGZfIGxZViJ8P7+bfp72gu8XEEsFJuUaZGFnX7zxgssWokCM
NBgJawRGhBJB4LGSOS1C0MQMRJmvUXGRgC5YaKcByzIZMoMRwdVAVRwESW8KcrnmGTf7Oqr27aoI
Yy4q7t+WH2/ejca/PPYJYfTuQEgCTKtNjd7Tnoi1LjDkMadg9m6FQPGJ964Jost17/T2iFXOjO+Y
3d/MF221m1W1gNVkkLETrNnaiTjA9WvJCBwa111WNVTIhFU6ZErxauEpZh1WrbQSwQbKdGN0Mpkz
wRLCX+/BFoIPpYiwyo/ChGuj9g3Q2YnibJF5oBBfqhArS+VPS0Wf1btsYLqZUqhRbSlVxglL9bKz
FdRsRhPAtCiUpF9Wckpog/V6qtoIwBS+bDiir6mSZZK6LTdYH/4uUBlY4pbjrltuNN72ej17/fh4
e1xrz2QDzxTHbTyCHxjPDdv/x+eFSUDXjIvIar7EXp30KjV1qtuJ/YlMRnT9gUyZNVJv/Vfsn6RJ
ne4x1Rs1aalsIxMNzakjnCCHGl692olt5zL/diW6Yd2v1NgpCZq8mE0hJ5+nZjy4QuMfBxPI+IZM
VeyPrLNmlSKzrVsvYy+xj3yUACKIJDWFkIa676nkyqHWMG4VdZo+SBB2JGj1xbVtzHAj5I7MIMEc
hWkrxEqTSlJmJ8us5k4taFImNq7Xb+dzeqY2tvIS6sfCaUMHhn3a0SeUuQOvqHMdlu5AJIlqlSMZ
lnZG/1RklmlZ0+qSeCjJe1L4pLhOBdmtRV+yrEjhlo41fTiouCKVrCXUIDHZ55qFm5YSEwq8xBgV
ihCdBhPn7p/dOcG3ePSUUGw+RkEweQSYKRYJVD489H04+4R7K0v0Uio2ezTZOfYdNao9To8d5TCW
VTqtFnCPW8z0mQ+zmwUEV74FARvSbxrmMG6/3NG/ln4wvroeD2pmPsyZClMIJpPxiSW/psYU7weD
3W7XV3HYw4gbqfpSJQMuYjmgexblNytTMLxyZBfMbLgPaCgp/TYYWS/R1jAtk1IbuAx897fmqNO/
Lag9iOcjQX5YeV/p9Q/Y4rZSZW5kc3RyZWFtCmVuZG9iago1MyAwIG9iago5ODgKZW5kb2JqCjU3
IDAgb2JqCjw8L0xlbmd0aCA1OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJ2V
bW/aMBDH3+dTnPZmrZSFhKfANE1Lga1A2Rhhm7R1L0xiEo/EzhynlH36nUO6QglStUQiwT6f7373
P+c32JYDtr6rZ5AajYULUW7YEBm/DaechOoRpHC1RIMeOE1Yro39GgeaLXDdHixT42LMFZWcqldD
SdYK8LqZeTAQXEmRJDSEmfcBfJrnTHCYE0lSigtybfiermRB5A6atuNeLn8ZrT4sb4wLnPqxeD/o
NJ3WT4APBQ/JHU0SZoJvmTAK8eeGFjwyYYqvQ3qHXjNSGny1zMuXhtN68HNwDWKxDeNC7vbLCA/h
ysKIFEtMeDGX4n4HM7FiCYXx/K77Qjt64gKDAh0VbvppjIwsx2333EYVqwleERW5wnTsXs3qN7FS
2etGY7vdWnIdvKIhU0JaQkYNxteigWPazVsLlza7RyR6bRdJPM10j2IqRKgHFv/YsNSEaz1DuDLh
43kkU8nymBO+B6uJTCy4IRHhjEqEck2JVCtKFMxoEONonsJayNPUaujtYWHgNbDK0UnB6aknlIJt
PgsVOqlB5Xa6WjRz8ifeEc4LuQfjZ5QFsU5KZ/pUUlMhY8EpPwtq8ohnSlhWliAlSamc0b2iXKs7
ByVAxfSIxmmGGg/cXsxn+uX2ErwgwO6Aj1RthdzAOKRcsTUWAD5lCt1WKHViNaJ6yrY0K9lqlJ3/
k6F2csi2bzUtDBxnZYr9ckdhQddUUo6RVxto9s121y5lSiXT3elbJbSFBdeMY1oI6+G00IyUCAQC
/IqngT4buufg315UpLCIAZIJyAEWveepwsrRGlg0oOkKyTr9fu9ZKtOOalTWbbodrTIqN4znJgwe
em8iYp4LzHT4qBhPbjYCcy8FwdTuXJ5+kWVCKmD8sIX0VqcJ7kcnRbKrbSHnWclpJ4fJeYWKhcxf
gheGEjX5r7hD7H3Cf5GdPi437CiBAcsDUdkNcBEncFXkjGtN43G/AX/0XR9FYbGiNEc/sW6easEV
4RFJhKTaQnKiyIYAdLp4gLqVyZiHjBwVYJQSlryGMM50MO8CHYAViBSNHj8gvmQHbX42Yse14RvF
M3tJ8pRwGEpUdzXn4/+JyDG2gQfQ7zitdjXzxffqIsqj/YZHITl2uzQryZmA0ieJdViu0X3GkPbD
x6OFtdPfw+Oawo85iSg4zk90OVoan/H+Cx5vDY1lbmRzdHJlYW0KZW5kb2JqCjU4IDAgb2JqCjg4
OAplbmRvYmoKNjIgMCBvYmoKPDwvTGVuZ3RoIDYzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4K
c3RyZWFtCnicbVLLbtswELzzK/bWBLBYPYoo7cmK4/QRu3BsBShQ9EAra5q2SNp8pFG/vpRCozWQ
5YFYzuzMgOQRUppB2q+4N5K8X5bALUmBkyPJBhDi1ki4qQPhGrIc6g15nckgL6Asr6GW5OKrcmgU
uuTWsI2DULN5BROtnNFti08wrz7DCq0VWsGCGSYxDNieeIdr45npIE+z8rLekeIj1DNyEaBvWvHk
S6f9HmaIl+9IVpygFVNcdl5xeFTiOUgJ1wVCDxXZKMIY5p8YJly0I7gNjWIy4T7yJtuAMwVFkSZl
nsbTJR78uhUN6A3ca4MsnOdXJ9upZKL9BLugte1zja30lDV0bwLtX/AHwTTc+bPEk61QDOZ6LVqM
Xj88U7+9RPUioHpGCt81LfII3qDYCcVjt6BL+irxVp6NPwbHbKy9a7Xe00bLszyzrkWog6Rxf86v
8WCEctHjninLbGweV9VbTr0SremgNLbD9Mnt6sPAXTC3FyNAB6yl8F9NXw7CoIXKc2/d8Ez9k8N5
/VwwjuGj/QqS05o8hPUXPiG22WVuZHN0cmVhbQplbmRvYmoKNjMgMCBvYmoKNDExCmVuZG9iago0
IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJl
bnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA5IDAg
UgovRm9udCAxMCAwIFIKPj4KL0NvbnRlbnRzIDUgMCBSCj4+CmVuZG9iagoxMSAwIG9iago8PC9U
eXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9S
ZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTQgMCBSCi9Gb250IDE1
IDAgUgo+PgovQ29udGVudHMgMTIgMCBSCj4+CmVuZG9iagoxNiAwIG9iago8PC9UeXBlL1BhZ2Uv
TWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8
PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTkgMCBSCi9Gb250IDIwIDAgUgo+Pgov
Q29udGVudHMgMTcgMCBSCj4+CmVuZG9iagoyMSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3gg
WzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0
Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMjQgMCBSCi9Gb250IDI1IDAgUgo+PgovQ29udGVudHMg
MjIgMCBSCj4+CmVuZG9iagoyNiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUg
ODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1Rl
eHRdCi9FeHRHU3RhdGUgMjkgMCBSCi9Gb250IDMwIDAgUgo+PgovQ29udGVudHMgMjcgMCBSCj4+
CmVuZG9iagozMSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90
YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRH
U3RhdGUgMzQgMCBSCi9Gb250IDM1IDAgUgo+PgovQ29udGVudHMgMzIgMCBSCj4+CmVuZG9iagoz
NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFy
ZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMzkg
MCBSCi9Gb250IDQwIDAgUgo+PgovQ29udGVudHMgMzcgMCBSCj4+CmVuZG9iago0MSAwIG9iago8
PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBS
Ci9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNDQgMCBSCi9Gb250
IDQ1IDAgUgo+PgovQ29udGVudHMgNDIgMCBSCj4+CmVuZG9iago0NiAwIG9iago8PC9UeXBlL1Bh
Z2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJj
ZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNDkgMCBSCi9Gb250IDUwIDAgUgo+
PgovQ29udGVudHMgNDcgMCBSCj4+CmVuZG9iago1MSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFC
b3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9j
U2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNTQgMCBSCi9Gb250IDU1IDAgUgo+PgovQ29udGVu
dHMgNTIgMCBSCj4+CmVuZG9iago1NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1
OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYg
L1RleHRdCi9FeHRHU3RhdGUgNTkgMCBSCi9Gb250IDYwIDAgUgo+PgovQ29udGVudHMgNTcgMCBS
Cj4+CmVuZG9iago2MSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQov
Um90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9F
eHRHU3RhdGUgNjQgMCBSCi9Gb250IDY1IDAgUgo+PgovQ29udGVudHMgNjIgMCBSCj4+CmVuZG9i
agozIDAgb2JqCjw8IC9UeXBlIC9QYWdlcyAvS2lkcyBbCjQgMCBSCjExIDAgUgoxNiAwIFIKMjEg
MCBSCjI2IDAgUgozMSAwIFIKMzYgMCBSCjQxIDAgUgo0NiAwIFIKNTEgMCBSCjU2IDAgUgo2MSAw
IFIKXSAvQ291bnQgMTIKPj4KZW5kb2JqCjEgMCBvYmoKPDwvVHlwZSAvQ2F0YWxvZyAvUGFnZXMg
MyAwIFIKL01ldGFkYXRhIDY3IDAgUgo+PgplbmRvYmoKNyAwIG9iago8PC9UeXBlL0V4dEdTdGF0
ZQovT1BNIDE+PmVuZG9iago5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjEwIDAgb2JqCjw8
L1I4CjggMCBSPj4KZW5kb2JqCjE0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjE1IDAgb2Jq
Cjw8L1I4CjggMCBSPj4KZW5kb2JqCjE5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjIwIDAg
b2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjI0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjI1
IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjI5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2Jq
CjMwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjM0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5k
b2JqCjM1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjM5IDAgb2JqCjw8L1I3CjcgMCBSPj4K
ZW5kb2JqCjQwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjQ0IDAgb2JqCjw8L1I3CjcgMCBS
Pj4KZW5kb2JqCjQ1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjQ5IDAgb2JqCjw8L1I3Cjcg
MCBSPj4KZW5kb2JqCjUwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjU0IDAgb2JqCjw8L1I3
CjcgMCBSPj4KZW5kb2JqCjU1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjU5IDAgb2JqCjw8
L1I3CjcgMCBSPj4KZW5kb2JqCjYwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjY0IDAgb2Jq
Cjw8L1I3CjcgMCBSPj4KZW5kb2JqCjY1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjggMCBv
YmoKPDwvQmFzZUZvbnQvQ291cmllci9UeXBlL0ZvbnQKL0VuY29kaW5nIDY2IDAgUi9TdWJ0eXBl
L1R5cGUxPj4KZW5kb2JqCjY2IDAgb2JqCjw8L1R5cGUvRW5jb2RpbmcvRGlmZmVyZW5jZXNbCjEy
Ni90aWxkZV0+PgplbmRvYmoKNjcgMCBvYmoKPDwvVHlwZS9NZXRhZGF0YQovU3VidHlwZS9YTUwv
TGVuZ3RoIDEzNTQ+PnN0cmVhbQo8P3hwYWNrZXQgYmVnaW49J++7vycgaWQ9J1c1TTBNcENlaGlI
enJlU3pOVGN6a2M5ZCc/Pgo8P2Fkb2JlLXhhcC1maWx0ZXJzIGVzYz0iQ1JMRiI/Pgo8eDp4bXBt
ZXRhIHhtbG5zOng9J2Fkb2JlOm5zOm1ldGEvJyB4OnhtcHRrPSdYTVAgdG9vbGtpdCAyLjkuMS0x
MywgZnJhbWV3b3JrIDEuNic+CjxyZGY6UkRGIHhtbG5zOnJkZj0naHR0cDovL3d3dy53My5vcmcv
MTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIycgeG1sbnM6aVg9J2h0dHA6Ly9ucy5hZG9iZS5jb20v
aVgvMS4wLyc+CjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSd1dWlkOjgwMzdmNzc2LTM1ODgt
MTFmMi0wMDAwLTkxMjFiN2UzZDA5NycgeG1sbnM6cGRmPSdodHRwOi8vbnMuYWRvYmUuY29tL3Bk
Zi8xLjMvJyBwZGY6UHJvZHVjZXI9J0dQTCBHaG9zdHNjcmlwdCA5LjA1Jy8+CjxyZGY6RGVzY3Jp
cHRpb24gcmRmOmFib3V0PSd1dWlkOjgwMzdmNzc2LTM1ODgtMTFmMi0wMDAwLTkxMjFiN2UzZDA5
NycgeG1sbnM6eG1wPSdodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvJz48eG1wOk1vZGlmeURh
dGU+MjAxNy0wMi0yN1QyMDoxMToxNy0wODowMDwveG1wOk1vZGlmeURhdGU+Cjx4bXA6Q3JlYXRl
RGF0ZT4yMDE3LTAyLTI3VDIwOjExOjE3LTA4OjAwPC94bXA6Q3JlYXRlRGF0ZT4KPHhtcDpDcmVh
dG9yVG9vbD5HTlUgRW5zY3JpcHQgMS42LjUuOTA8L3htcDpDcmVhdG9yVG9vbD48L3JkZjpEZXNj
cmlwdGlvbj4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J3V1aWQ6ODAzN2Y3NzYtMzU4OC0x
MWYyLTAwMDAtOTEyMWI3ZTNkMDk3JyB4bWxuczp4YXBNTT0naHR0cDovL25zLmFkb2JlLmNvbS94
YXAvMS4wL21tLycgeGFwTU06RG9jdW1lbnRJRD0ndXVpZDo4MDM3Zjc3Ni0zNTg4LTExZjItMDAw
MC05MTIxYjdlM2QwOTcnLz4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J3V1aWQ6ODAzN2Y3
NzYtMzU4OC0xMWYyLTAwMDAtOTEyMWI3ZTNkMDk3JyB4bWxuczpkYz0naHR0cDovL3B1cmwub3Jn
L2RjL2VsZW1lbnRzLzEuMS8nIGRjOmZvcm1hdD0nYXBwbGljYXRpb24vcGRmJz48ZGM6dGl0bGU+
PHJkZjpBbHQ+PHJkZjpsaSB4bWw6bGFuZz0neC1kZWZhdWx0Jz5FbnNjcmlwdCBPdXRwdXQ8L3Jk
ZjpsaT48L3JkZjpBbHQ+PC9kYzp0aXRsZT48L3JkZjpEZXNjcmlwdGlvbj4KPC9yZGY6UkRGPgo8
L3g6eG1wbWV0YT4KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAo8P3hwYWNrZXQgZW5k
PSd3Jz8+CmVuZHN0cmVhbQplbmRvYmoKMiAwIG9iago8PC9Qcm9kdWNlcihHUEwgR2hvc3RzY3Jp
cHQgOS4wNSkKL0NyZWF0aW9uRGF0ZShEOjIwMTcwMjI3MjAxMTE3LTA4JzAwJykKL01vZERhdGUo
RDoyMDE3MDIyNzIwMTExNy0wOCcwMCcpCi9UaXRsZShFbnNjcmlwdCBPdXRwdXQpCi9DcmVhdG9y
KEdOVSBFbnNjcmlwdCAxLjYuNS45MCk+PmVuZG9iagp4cmVmCjAgNjgKMDAwMDAwMDAwMCA2NTUz
NSBmIAowMDAwMDEzNzA1IDAwMDAwIG4gCjAwMDAwMTYwOTggMDAwMDAgbiAKMDAwMDAxMzU2OCAw
MDAwMCBuIAowMDAwMDExNjI3IDAwMDAwIG4gCjAwMDAwMDAwMTUgMDAwMDAgbiAKMDAwMDAwMTEw
MyAwMDAwMCBuIAowMDAwMDEzNzcwIDAwMDAwIG4gCjAwMDAwMTQ1MzAgMDAwMDAgbiAKMDAwMDAx
MzgxMSAwMDAwMCBuIAowMDAwMDEzODQwIDAwMDAwIG4gCjAwMDAwMTE3ODYgMDAwMDAgbiAKMDAw
MDAwMTEyMyAwMDAwMCBuIAowMDAwMDAyNDEwIDAwMDAwIG4gCjAwMDAwMTM4NzAgMDAwMDAgbiAK
MDAwMDAxMzkwMCAwMDAwMCBuIAowMDAwMDExOTQ4IDAwMDAwIG4gCjAwMDAwMDI0MzEgMDAwMDAg
biAKMDAwMDAwMzM5MiAwMDAwMCBuIAowMDAwMDEzOTMwIDAwMDAwIG4gCjAwMDAwMTM5NjAgMDAw
MDAgbiAKMDAwMDAxMjExMCAwMDAwMCBuIAowMDAwMDAzNDEyIDAwMDAwIG4gCjAwMDAwMDQyNTIg
MDAwMDAgbiAKMDAwMDAxMzk5MCAwMDAwMCBuIAowMDAwMDE0MDIwIDAwMDAwIG4gCjAwMDAwMTIy
NzIgMDAwMDAgbiAKMDAwMDAwNDI3MiAwMDAwMCBuIAowMDAwMDA1MDc2IDAwMDAwIG4gCjAwMDAw
MTQwNTAgMDAwMDAgbiAKMDAwMDAxNDA4MCAwMDAwMCBuIAowMDAwMDEyNDM0IDAwMDAwIG4gCjAw
MDAwMDUwOTYgMDAwMDAgbiAKMDAwMDAwNTg5MSAwMDAwMCBuIAowMDAwMDE0MTEwIDAwMDAwIG4g
CjAwMDAwMTQxNDAgMDAwMDAgbiAKMDAwMDAxMjU5NiAwMDAwMCBuIAowMDAwMDA1OTExIDAwMDAw
IG4gCjAwMDAwMDY5ODggMDAwMDAgbiAKMDAwMDAxNDE3MCAwMDAwMCBuIAowMDAwMDE0MjAwIDAw
MDAwIG4gCjAwMDAwMTI3NTggMDAwMDAgbiAKMDAwMDAwNzAwOSAwMDAwMCBuIAowMDAwMDA4MDAz
IDAwMDAwIG4gCjAwMDAwMTQyMzAgMDAwMDAgbiAKMDAwMDAxNDI2MCAwMDAwMCBuIAowMDAwMDEy
OTIwIDAwMDAwIG4gCjAwMDAwMDgwMjMgMDAwMDAgbiAKMDAwMDAwOTA0NCAwMDAwMCBuIAowMDAw
MDE0MjkwIDAwMDAwIG4gCjAwMDAwMTQzMjAgMDAwMDAgbiAKMDAwMDAxMzA4MiAwMDAwMCBuIAow
MDAwMDA5MDY0IDAwMDAwIG4gCjAwMDAwMTAxMjQgMDAwMDAgbiAKMDAwMDAxNDM1MCAwMDAwMCBu
IAowMDAwMDE0MzgwIDAwMDAwIG4gCjAwMDAwMTMyNDQgMDAwMDAgbiAKMDAwMDAxMDE0NCAwMDAw
MCBuIAowMDAwMDExMTA0IDAwMDAwIG4gCjAwMDAwMTQ0MTAgMDAwMDAgbiAKMDAwMDAxNDQ0MCAw
MDAwMCBuIAowMDAwMDEzNDA2IDAwMDAwIG4gCjAwMDAwMTExMjQgMDAwMDAgbiAKMDAwMDAxMTYw
NyAwMDAwMCBuIAowMDAwMDE0NDcwIDAwMDAwIG4gCjAwMDAwMTQ1MDAgMDAwMDAgbiAKMDAwMDAx
NDYwOCAwMDAwMCBuIAowMDAwMDE0NjY3IDAwMDAwIG4gCnRyYWlsZXIKPDwgL1NpemUgNjggL1Jv
b3QgMSAwIFIgL0luZm8gMiAwIFIKL0lEIFs8QTREMDU2MzVEQ0Q4QzVFMzc5NEJFQTAzN0VCRDY2
REE+PEE0RDA1NjM1RENEOEM1RTM3OTRCRUEwMzdFQkQ2NkRBPl0KPj4Kc3RhcnR4cmVmCjE2Mjc3
CiUlRU9GCg==

--_002_11C3DA1E287F40FB89008C74F9D6A51Aciscocom_--


From nobody Mon Feb 27 20:30:35 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2771293E3; Mon, 27 Feb 2017 20:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cfe1gKx_8pKQ; Mon, 27 Feb 2017 20:30:32 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA5BF1294BD; Mon, 27 Feb 2017 20:30:32 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-d8-58b4b6900182
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id 38.4C.02566.196B4B85; Tue, 28 Feb 2017 00:30:27 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0319.002; Mon, 27 Feb 2017 23:30:29 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
Thread-Topic: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
Thread-Index: AQHSkO5qaAL8+iSgEEmWyfeFJo1k5KF+JLUAgAAD+YA=
Date: Tue, 28 Feb 2017 04:30:19 +0000
Message-ID: <96654188-E0BF-409A-B254-811272FEAAB5@ericsson.com>
References: <201702271130.v1RBUZaY065404@givry.fdupont.fr> <11C3DA1E-287F-40FB-8900-8C74F9D6A51A@cisco.com>
In-Reply-To: <11C3DA1E-287F-40FB-8900-8C74F9D6A51A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_FED0710A-91FB-4072-A73B-7C51508DE148"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrEIsWRmVeSWpSXmKPExsUyuXRPgu7kbVsiDFZPFrV4cPMEu8WZD09Y LB5N28lqcfXVZxYHFo8pvzeyeryb+ofVY8mSn0wBzFFcNimpOZllqUX6dglcGYfWCxc89a54 v2AFWwPjSbcuRg4OCQETif6PQl2MXBxCAusZJaY+6mHrYuQEcpYzSux9zAtiswHVbNj5mQnE FhEwlmh42coI0sAssJ9R4sbGFlaQhLCAm8Sz35eZIYrcJd6veMMGYVtJvDn+DMxmEVCVONbS yQ5i8wrYSzw8eoAJYlmuxIJVk8B6OQVsJU6fawKbySggJvH91BqwGmYBcYlbT+aD2RICIhIP L55mg7BFJV4+/scKYStJzHl9jRniuCmMEp+WLmGEWCYocXLmE5YJjCKzkMyahaxuFpI6iKIk iWsTrrND2NoSyxa+Zp4FDDFmAR2JyQsZUYUh7I/njzBB2KYSr49+hKqxlpjx6yAbhK0oMaX7 IfsCRu5VjBylxQU5uelGhpsYgbF7TILNcQfj3l7PQ4wCHIxKPLwb2LZECLEmlhVX5h5iVAFq fbRh9QVGKZa8/LxUJRHejp9Aad6UxMqq1KL8+KLSnNTiQ4zSHCxK4rzXQ+6HCwmkJ5akZqem FqQWwWSZODilGhg5J7bscUj+tlj/j75zMEvb032sby9zR/8QcWFjkjL/6339r1HZpW9u2wrX PX5VWmO+4fvzt7qKP35HzQ+4meL23vTMxuIpE74leJ0RXr+ju2y+goRe8OYcTePpB94ecLh8 u51fgDX544tH2kEqPEX6189pe3o9PFTw+HVR3dmVKRZL352flLVOiaU4I9FQi7moOBEAWwmu dOUCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/JxSdPtfk-4LPeYLCyKTztWy4_wE>
Cc: Gen art <gen-art@ietf.org>, "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" <draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 04:30:34 -0000

--Apple-Mail=_FED0710A-91FB-4072-A73B-7C51508DE148
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F654C435-45A6-4D1A-A28D-6E72E34AD2BE"


--Apple-Mail=_F654C435-45A6-4D1A-A28D-6E72E34AD2BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Feb 27, 2017, at 11:16 PM, Dhananjay Patki (dhpatki) =
<dhpatki@cisco.com> wrote:
>=20
> Hi Francis,
>=20
> Please see inline responses. Also, please find attached version 04 of =
the draft attached to this email. I will upload the new version once you =
approve the rework. Or would you want the updated draft to be uploaded =
first? Let me know if you have any further comments.

Thanks Francis and Dhananjay. Once you converge on the proposed changes, =
feel free to submit the new revision of the draft.

Regards
Suresh


--Apple-Mail=_F654C435-45A6-4D1A-A28D-6E72E34AD2BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><br class=3D""></div><div =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Feb 27, 2017, at 11:16 PM, Dhananjay Patki (dhpatki) &lt;<a =
href=3D"mailto:dhpatki@cisco.com" class=3D"">dhpatki@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Hi Francis,</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Please see inline responses. Also, please find =
attached version 04 of the draft attached to this email. I will upload =
the new version once you approve the rework. Or would you want the =
updated draft to be uploaded first? Let me know if you have any further =
comments.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div>Thanks Francis =
and Dhananjay. Once you converge on the proposed changes, feel free to =
submit the new revision of the draft.<div class=3D""><br =
class=3D""></div><div class=3D"">Regards</div><div =
class=3D"">Suresh</div><div class=3D""><br =
class=3D""></div></div></div></body></html>=

--Apple-Mail=_F654C435-45A6-4D1A-A28D-6E72E34AD2BE--

--Apple-Mail=_FED0710A-91FB-4072-A73B-7C51508DE148
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjI4MDQzMDE4WjAjBgkqhkiG9w0B
CQQxFgQUz9YgCc9NK2qDKp2fj8JkNrgo+ogwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQDHK22EmvQmrwd05DzEXE9FVSQPBn+/9P+xZBGPq1SbxDAIURkvxFJ3Qy+ePkg+
FQA1GpMMidIaTWdvAj79E9r4FIqjjTTLC0QVg+FUnSCoWCd172WjD9B7Jg0ZEYyBFsmrknZ5Knum
WLa0PkdgvXmaqahUUdD5FskWAfdZYVtv/Dozn/jzPdO8EsBEwhCxI1XygxSwafL8SBhguTJqpDL9
ygklY/Xsg8U8/mpe1W+FG2uW3sm2pQ0a0LL/UKEldpysT1tRqoK7gMSZ0BpyJgezLm1b2uXea7Ns
mykoRZeBNwrtVmPMbzn2hfWPW6kDjtRMkC3yoJlnlDMF/2QkfYCzAAAAAAAA

--Apple-Mail=_FED0710A-91FB-4072-A73B-7C51508DE148--


From nobody Tue Feb 28 07:07:22 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D421295C0 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 07:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZhQgTAqzSMZ for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 07:07:18 -0800 (PST)
Received: from nm41-vm1.bullet.mail.gq1.yahoo.com (nm41-vm1.bullet.mail.gq1.yahoo.com [67.195.87.88]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4750012953F for <gen-art@ietf.org>; Tue, 28 Feb 2017 07:07:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1488294437; bh=kI8oX3F/WR6ViKNiZxJFgFrx08oP/eS2UNa/28Zj/xA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=WNlQGDhZQMdvXVKOU4Nf82wLjxMLobZvgpbYV2fd8TsXflKkHxOY5WUBstp3RFSkHZtcCs4NZ1RgLZWAx/PwPePmXfDu6x+FAEj05W5PUplsxxN230wLoQhaV1a/UGOx6exRJKws/dctu4Uezp2altBZj9Xmpo+nsLmgFWNpcAwJ3n7ef00G4KEPkCeuuayRIyQ0vqtctNA77BwvExkejSJ25nEdCbfFrX/FnV3owEoBPplgKRxj1nHOfaxClCcsIKMSDYCIgnsZu0rNZGjZxTmrfX0oHrtZed00/7z+pYNmgYjA62qOddsqIlA+sFbakMMs85c/VFxv0GN8vko2Sg==
Received: from [127.0.0.1] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 28 Feb 2017 15:07:17 -0000
Received: from [98.137.12.62] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 28 Feb 2017 15:04:25 -0000
Received: from [98.137.12.217] by tm7.bullet.mail.gq1.yahoo.com with NNFMP; 28 Feb 2017 15:04:25 -0000
Received: from [127.0.0.1] by omp1025.mail.gq1.yahoo.com with NNFMP; 28 Feb 2017 15:04:25 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 83362.82351.bm@omp1025.mail.gq1.yahoo.com
X-YMail-OSG: eK82bHYVRDtgfAoCqOIpFuQf7CXNzbPmvwqKAF0E6WpCYH8GW8U-
Received: from jws300003.mail.gq1.yahoo.com by sendmailws113.mail.gq1.yahoo.com; Tue, 28 Feb 2017 15:04:24 +0000; 1488294264.593
Date: Tue, 28 Feb 2017 15:04:24 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: jouni korhonen <jouni.nospam@gmail.com>,  General Area Review Team <gen-art@ietf.org>,  "draft-ietf-ippm-6man-pdm-option.all@ietf.org" <draft-ietf-ippm-6man-pdm-option.all@ietf.org>
Message-ID: <1447603174.3532009.1488294264199@mail.yahoo.com>
In-Reply-To: <1332138488.632081.1487514414996@mail.yahoo.com>
References: <1332138488.632081.1487514414996.ref@mail.yahoo.com> <1332138488.632081.1487514414996@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/uhmPXramIxVlHr2sjWzJxKV6WZ0>
Cc: Robert Hamilton <rhamilton@cas.org>, Michael Ackermann <mackermann@bcbsm.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Minor and editorial
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 15:07:20 -0000

Jouni,

We have posted a new version which addresses the minor and editorial comments. It is below.  I am waiting for your response to the major comments & then I will integrate.   As far as I know now, I have addressed all outstanding issues.   My comments to your editorial / minor is below.

https://datatracker.ietf.org/doc/draft-ietf-ippm-6man-pdm-option/


Nits/editorial comments: 

>1) Section 1.4 numbered list: add missing full stops. 

Actually, I think it is better to remove the full stops from the two that have it.  These are sentence 
fragments. 

>2) Section 3.2: remove 

> "The 5-tuple consists of 

>   the source and destination IP addresses, the source and destination 

>   ports, and the upper layer protocol (ex. TCP, ICMP, etc)." 

> since this is unnecessary repetition. 


This is in the section below: 

Old 
---- 
Packet Sequence Number This Packet (PSNTP) 

16-bit unsigned integer.  This field will wrap. It is intended for 
use while analyzing packet traces. 

Initialized at a random number and incremented monotonically for each 
packet of the session flow of the 5-tuple.  The 5-tuple consists of 
the source and destination IP addresses, the source and destination 
ports, and the upper layer protocol (ex. TCP, ICMP, etc).   The 
random number initialization is intended to make it harder to spoof 
and insert such packets. 

New 
---- 
Packet Sequence Number This Packet (PSNTP) 

16-bit unsigned integer.  This field will wrap. It is intended for 
use while analyzing packet traces. 

Initialized at a random number and incremented monotonically for each 
packet of the session flow of the 5-tuple. 


>3) Section 3.2: remove 

> "Operating systems MUST NOT implement a single 

>  counter for all connections." 

>Seems again like unnecessary repetition to previous sentence. 


This is in the section on "Packet Sequence Number This Packet (PSNTP)" 

Old 
--- 
Operating systems MUST implement a separate packet sequence number 
counter per 5-tuple. Operating systems MUST NOT implement a single 
counter for all connections. 

New 
--- 
Operating systems MUST implement a separate packet sequence number 
counter per 5-tuple. 


>4) Section 3.2 again unnecessary repetition of IPv6 basics that can be read from RFC2460. Suggest strongly to remove: 

> "This indicates the following processing requirements: 

>   00 - skip over this option and continue processing the header. 

>   RFC2460 [RFC2460] defines other values for the Option Type field. 

>  These MUST NOT be used in the PDM." 

> and 

>  "The possible values are as follows: 

>  0 - Option Data does not change en-route 

>   1 - Option Data may change en-route 

>   The three high-order bits described above are to be treated as part 

>   of the Option Type, not independent of the Option Type.  That is, a 

>  particular option is identified by a full 8-bit Option Type, not just 

>  the low-order 5 bits of an Option Type." 


Old 
---- 
Option Type 

The two highest-order bits of the Option Type field are encoded to 
indicate specific processing of the option; for the PDM destination 
option, these two bits MUST be set to 00. This indicates the 
following processing requirements: 

00 - skip over this option and continue processing the header. 

RFC2460 [RFC2460] defines other values for the Option Type field. 
These MUST NOT be used in the PDM. 

In keeping with RFC2460 [RFC2460], the third-highest-order bit of the 
Option Type specifies whether or not the Option Data of that option 
can change en-route to the packet's final destination. 

In the PDM, the value of the third-highest-order bit MUST be 0.  The 
possible values are as follows: 

0 - Option Data does not change en-route 

1 - Option Data may change en-route 

The three high-order bits described above are to be treated as part 
of the Option Type, not independent of the Option Type.  That is, a 
particular option is identified by a full 8-bit Option Type, not just 
the low-order 5 bits of an Option Type. 



New 
---- 
Option Type 

In keeping with RFC2460[RFC2460], the two high order bits of the Option Type field are encoded to 
indicate specific processing of the option; for the PDM destination 
option, these two bits MUST be set to 00. 

The third high order bit of the Option Type specifies whether or not the Option Data of that option 
can change en-route to the packet's final destination. 

In the PDM, the value of the third high order bit MUST be 0. 



5) Section 3.3 same as in comment 4). Suggest strongly removing: 

>  "This follows the order defined in RFC2460 [RFC2460] 

>                IPv6 header 

>               Hop-by-Hop Options header 

>              Destination Options header  <-------- 

>             Routing header 

>            Fragment header 

>           Authentication header 

>          Encapsulating Security Payload header 

>         Destination Options header <------------ 

>        upper-layer header" 



>6) Suggest removing entire Section 3.4 and moving the following text to Section 3.3: 

> "PDM MUST be placed before the ESP header in 

> order to work.  If placed before the ESP header, the PDM header will 

> flow in the clear over the network thus allowing gathering of 

> performance and diagnostic data without sacrificing security." 


ESP processing with PDM was changed because of comments from security reviewer. 



>7) Section 3.6 suggest removing the following text. I see no value it would add to what has already been said: 

>  "As with all other destination options extension headers, the PDM is 

>   for destination nodes only. As specified above, intermediate devices 

>   MUST neither set nor modify this field." 


Done 


>8) Section 3.6 suggest removing the following 5-tuple text as it has already been described earlier in Section 2: 

>  "The 5-tuple is: 

>   SADDR : IP address of the sender SPORT : Port for sender DADDR : IP 

>   address of the destination DPORT : Port for destination PROTC : 

>   Protocol for upper layer (ex. TCP, UDP, ICMP)" 

Done 


>9) Sections 4.2 and 4.3 suggest removing them entirely. I see what value these sections add. I acknowledge they are good 
>to know information of timer hardware implementation difference but do not really add value on the on-wire encoding of the PDM option. 

>10) Section 4.4 suggest removing the entire section. Time Base was already described in detail enough in Section 3.2. 

>11) Section 4.5 time base for picoseconds is 11 not 00. 

>12) Section 4.5 suggest removing the following text, since it does not add any more clarity to what has already been said in my opinion. This is because all the examples follow nice nybble increment in scaling: 

>  "Sample binary values (high order 16 bits taken) 

>   1 psec            1                                              0001 

>   1 nsec          3E8                                    0011 1110 1000 

>   1 usec        F4240                          1111 0100 0010 0100 0000 

>   1 msec     3B9ACA00           0011 1011 1001 1010 1100 1010 0000 0000 

>   1 sec    E8D4A51000 1110 1000 1101 0100 1010 0101 0001 0000 0000 0000" 

>12) Section 4.6 I do not understand why this section is here. I strongly suggest removing it. Sections 4.5 and 3.2 already describe how I would encode the delta time using scaling as a separate fields not embedded (option fields ScaleDTLR and ScaleDTLS). Did I misunderstand something here? 


Points 9 - 12 refer to the timing calculations.  The timebase has been fixed to be attoseconds. 
The entire timing section has been re-written.  It has also been moved to an appendix. 
Please let us know if it this addresses your concerns. 



>13) Section 5 suggest removing the following text because of it repeating what has already been said earlier: 

>  "Each packet, in addition to the PDM contains information on the 

>  sender and receiver. As discussed before, a 5-tuple consists of: 

>    SADDR : IP address of the sender 

>    SPORT : Port for sender 

>   DADDR : IP address of the destination 

>    DPORT : Port for destination 

>    PROTC : Protocol for upper layer (ex. TCP, UDP, ICMP) 

>  It should be understood that the packet identification information is 

>  in each packet. We will not repeat that in each of the following 

>  steps." 


This is now in Appendix B.  It has been removed from that section. 



>14) Section 5.3 suggest merging the following text into one example and do necessary rewording. There is no need to do the same 
>   calculation twice on almost adjacent lines: 

> "Sending time : packet 2 - receive time : packet 1 

>  We will call the result of this calculation: Delta Time Last Received 

>  (DELTATLR) 

>  That is: 

>  Delta Time Last Received = (Sending time: packet 2 - receive time: packet 1)" 

Done 


> 15) Expand RTT and PSN on their first use. 

Done
 
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


From nobody Tue Feb 28 10:13:41 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BA623129664; Tue, 28 Feb 2017 10:13:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148830561976.29462.5646221515903137638.idtracker@ietfa.amsl.com>
Date: Tue, 28 Feb 2017 10:13:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/AIH9xoX466oUS6AV09M05eGy9HY>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-temporal-hitless-psm.all@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-mpls-tp-temporal-hitless-psm-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 18:13:40 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-tp-temporal-hitless-psm-??
Reviewer: Stewart Bryant
Review Date: 2017-02-28
IETF LC End Date: 2017-03-03
IESG Telechat date: 2017-03-16

Summary:

This document is a valid critique of the existing MPLS SPM design, and
sets out a list of requirements that were called up at the time of its
design but not met. As such this is a valid set of requirements. What
is unclear is whether it is feasible to meet the requirements set out
in this document, and if so whether or not this will require a change
to the MPLS architecture. It would be useful to the reader to clarify
the feasibility of a solution in order not to set false expectations.

Major issues:

The title is "Hitless path segment monitoring".  I read the document
hoping to find that this was a solution. It is not, it is a
requirements text and really ought to be titled as such.

Whilst this text describes a list of issues with the existing IETF
design, it should be remembered that the design was the best that
could be accomplished at the time within the constraints of the MPLS
architecture. So that leaves the reader with a question: do the
authors now have an insight into how a solution can now be designed to
meet the requirement,  or do the authors intend to propose a change to
the MPLS architecture, or is the intention to publish this to state
the requirements in the hope that someone will eventually propose a
solution?

The text  says:

"In particular, performance monitoring measurements (e.g.  Delay
Measurement and Packet Loss  Measurement) are sensitive to these
changes."

Whilst technically true, I am not sure the impact on delay is
significant in any engineering sense. We are talking four bytes per
packet over a service that is going at 1 to 400 Gb/s. Again it is hard
to imagine a significant impact on loss. If this is a key point it
need some justification from an engineering perspective.

In Figure 5 it is unclear what the difference between the first and
second on-demand point is. Is this a reference to input and output
interface monitoring. If  so I think that this should be made clear,
together with a note that a lot of MPLS forwarding designs find this
difficult to achieve. 

The text around Figure 8 explains the deficiency in TTL based section
of an OAM monitoring point in MPLS. However the authors give no
indication of a feasible alternative. Do they have one in mind?

Minor issues: None

Nits/editorial comments: 
     From ID-Nits: The abstract seems to contain references
([RFC6371]), which it
     shouldn't.  Please replace those with straight textual mentions
of the
     documents in question.

For exampla in OTN, TCM allows the insertion - Typo example


From nobody Tue Feb 28 12:39:51 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A063C1296CB for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 12:39:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smaiUG3B3-aB for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 12:39:49 -0800 (PST)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308B81296DF for <gen-art@ietf.org>; Tue, 28 Feb 2017 12:39:49 -0800 (PST)
Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by resqmta-po-04v.sys.comcast.net with SMTP id ioWmcsWUfxUJaioYmcUec4; Tue, 28 Feb 2017 20:39:48 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-08v.sys.comcast.net with SMTP id ioYkcRaE30ttWioYmc0mZE; Tue, 28 Feb 2017 20:39:48 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1SKdkqF011080; Tue, 28 Feb 2017 15:39:46 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1SKdkkJ011077; Tue, 28 Feb 2017 15:39:46 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
In-Reply-To: <87innwmphk.fsf@hobgoblin.ariadne.com> (worley@ariadne.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 28 Feb 2017 15:39:46 -0500
Message-ID: <87o9xmjbhp.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfCHvKlmAm3J0N85SXjYzwuFs5LxA9fegEMMe5ewUZbffN0wOGu+/m0wnbCzc03Od1KxYjGEvxgjDFYXl3zBJ2WfG/YvbppN1YevVLFRV4BhXYoWdiIlA siiXlp0JiVgIBHqMyhPJVpsin2yT2IH1oJkkYRLqLNtvVvAno1o4snp7MQNckgyKQlk0buVCk4tRn6d1Vv9ZLu8Cl0VXDCV45p0ZdDWPiwxSZrIQK4XnnA/E JIpBWqBabcG1rywvcQopCg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/3fSCsGp6ubxi3hM-QZv2lL7PsCs>
Subject: Re: [Gen-art] Review of draft-ietf-dane-smime-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 20:39:49 -0000

worley@ariadne.com (Dale R. Worley) writes:
> [How about salting the hashes?]

OK, this has been discussed...

Dale


From nobody Tue Feb 28 12:50:46 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E69129706 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 12:50:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f_9hhf6JUNek for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2017 12:50:32 -0800 (PST)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D52CF1296FD for <gen-art@ietf.org>; Tue, 28 Feb 2017 12:50:32 -0800 (PST)
Received: from resomta-po-10v.sys.comcast.net ([96.114.154.234]) by resqmta-po-02v.sys.comcast.net with SMTP id iohVcF6zIJ5z3iojAcSZ3L; Tue, 28 Feb 2017 20:50:32 +0000
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-po-10v.sys.comcast.net with SMTP id ioj9ctw2bCp2Wioj9csYuW; Tue, 28 Feb 2017 20:50:32 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: draft-bchv-rfc6890bis.all@ietf.org
Message-ID: <7b83db1c-22b6-5208-e5ee-8ccaeacf2210@alum.mit.edu>
Date: Tue, 28 Feb 2017 15:50:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfNL6nQT/xccI9XKuKd3XyMVjCE5yFrWbI5248qhqqpEuplW76UaujGb1jErsnkdcDy5Td4hxeicowdGwkqbQFMn8ROFgbosRi/nicXTCvpsVenQVmU/6 k5JsD5aVAGbqNrAUtwxBd0/cDQHyznN/7HowZ49U+5beGM5LJv+aJT++e6Ne3DZ2GW2Kg+6sm2ryZZjiLaLkDfF7pRPsNzpKk8eavdkuyzmcFYhaxChkBy3S
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KhDXZE9JE7jeMJ_cSAzYW6NGM00>
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-bchv-rfc6890bis-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 20:50:33 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area 
Review Team (Gen-ART) reviews all IETF documents being processed by the 
IESG for the IETF Chair. Please treat these comments just like any other 
last call comments. For more information, please see the FAQ at 
<​http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-bchv-rfc6890bis-04
Reviewer: Paul Kyzivat
Review Date: 2017-02-28
IETF LC End Date: 2017-03-10
IESG Telechat date:

Summary:

Ready with Issues

General Comments:

It seems that the primary intent of this document is simply to clarify 
the use of the term "Global". As such it should be just an editorial 
change.

However it takes on the job of restating all the data in RFC6890 that 
provided the initial population of the IANA registries, and also 
restating all the new entries that have been added to those registries 
since RFC6890 was published. And the editorial changes apply to every 
table entry, so there are a *lot* of changes. A diff of the new document 
against the old one fails to match up the appropriate corresponding 
tables, making the document especially hard to review.

I have *tried* to at least spot check the changes, especially those for 
registrations made since RFC6890. But I did not do an exhaustive check 
of every one.

Issues:

Major: 0
Minor: 1
Nits:  1

(1) Minor:

I am concerned that the format of this document may be difficult for 
IANA to act on, and may increase the potential for mistakes to be 
introduced. The IANA format for their special purpose IP address 
registries contains the same information as this document but in a 
different format. If I understand correctly, no changes are required to 
the per-address content of the registries - only the introductory 
content and table headings need changes. But given the document format 
IANA will be obligated to check the content of every entry.

I suggest that it might be better to eliminate duplicating the table 
content, and simply state what changes need to be made to the registries.

(2) NIT:

There is an error in the use of footnotes in Table 38. The reference to 
footnote "[2]" should be "[6]". (The footnote numbering has changed 
since RFC680, but both references were intended to be to the same footnote.)


From nobody Tue Feb 28 21:16:17 2017
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 884331294A0; Tue, 28 Feb 2017 21:16:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee <peter@akayla.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148834537055.29494.17692224713818414298.idtracker@ietfa.amsl.com>
Date: Tue, 28 Feb 2017 21:16:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Jbbx2Ep5uXK6MLtsX4kpzeVADWA>
Cc: draft-ietf-6man-rfc2460bis.all@ietf.org, ipv6@ietf.org, ietf@ietf.org
Subject: [Gen-art] Review of draft-ietf-6man-rfc2460bis-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 05:16:10 -0000

Reviewer: Peter Yee
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc2460bis-08
Reviewer: Peter Yee
Review Date: 2017-02-28
IETF LC End Date: 2017-03-01
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits.  This Internet-Draft is an update to RFC
2460, the specification for IPv6.  See the following note.

Note that I read this document in the context that it is an update of
RFC 2460, primarily for the purpose of cleaning up minor items (things
that to moved to other documents, for example) and addressing errata. 
I did not do a top-to-bottom review of the document as though it were
a wholly new work.

Major issues: None

Minor issues: None

Nits/editorial comments: 

General:

For RFCs named outside of references (i.e., those that aren't found in
square brackets), separate "RFC" from the following numbers with a
space.  This is especially prevalent in Appendix B.

>From the mailing list discussion back in 2015, I can't determine if an
actual decision was taken as to whether RFC 2119 recommended/expected
language ought to be used in this document.  The discussion mentioned
leaving the topic for IETF LC, but I can't even tell if there was
consensus to do that.  This document does not use RFC 2119 language
primarily because it is minor update to RFC 2460, which itself did not
use RFC 2119 language.  There was a healthy debate on the mailing list
and I feel it came down mostly on the side of using RFC 2119, but
again no consensus was obvious, just a preponderance of opinions.  The
thread starts here:
https://www.ietf.org/mail-archive/web/ipv6/current/msg23284.html

Change all uses of "en-route" to "en route".  Usage is mixed in the
document, but en-route is never used before a noun and as a borrowed
word from French would arguably not even be hyphenated had it appeared
before a noun.  We won't even get into italicizing it. ;-)

Change all uses of "behaviour" to "behavior".  Although both British
and American English are permissible, it seems preferable that only
form be used in any particular document.  Given so many other
Americanized spellings in the document, I'm recommending going with
American English in this case.

Specific:

Page 20, 5th bullet item, 2nd paragraph, 2nd sentence: delete "an"
before "overlapping".

Page 22, Section 4.8, 1st paragraph, append a comma after "because".

Page 23, 1st partial paragraph, 1st full sentence: insert "be" before
"a".

Page 23, 1st full paragraph, 2nd sentence: insert "be" before "a".

Page 23, 2nd full paragraph: consider changing "need to" to "must". 
(Ignoring any decision taken on RFC 2119 usage.)  I don't believe the
"need to" at the top of this page needs to(!) change as it describing
what designers need to do, not placing a restriction on a protocol
element.

Page 23, Header Specific Data definition: change the comma to a
period.

Page 26, 2nd bullet item, 1st sentence: delete the comma after
"node".

Page 26, 3rd bullet item, 2nd sentence: change "use" to "Use" in the
title of RFC 6936.

Page 29, Section 12.1, [I-D.ietf-6man-rfc4291bis] reference: update
-06 to -07 to reflect the current version of that draft.

Page 34, Appendix B title: change to "Changes since RFC 2460".

Page 35, 1st 07) item: change "IPSEC" to "IPsec".

Page 39, 01) item: delete an extraneous space before "and".

