Re: Eric Rescorla's Discuss on draft-ietf-hip-native-nat-traversal-28: (with DISCUSS and COMMENT)

--===============6289246378200427062==
Content-Type: multipart/alternative; boundary="000000000000ed6e58056b8e4d6d"

--000000000000ed6e58056b8e4d6d
Content-Type: text/plain; charset="UTF-8"

On Sun, May 6, 2018 at 12:05 PM, Christer Holmberg <
[email protected]> wrote:

> Hi,
>
> The question is whether this document should re-define the HIP variations
> to ICE that RFC 5770 already does.
>

That may be your question, but it's not my question. My question is that
I'm not sure this document is sufficiently clear and unambigious to
implement, given its current structure.

-Ekr


> Regards,
>
> Christer
>
> Sent from my iPhone
>
> On 6 May 2018, at 22.01, Eric Rescorla <[email protected]> wrote:
>
>
>
> On Sun, May 6, 2018 at 10:19 AM, Christer Holmberg <
> [email protected]> wrote:
>
>> Hi,
>>
>> > I am very familiar with ICE and yet I found this document extremely
>> hard to follow. The problem is that it cherry-picks pieces
>> > of ICE and I'm just not sure that it's a complete specification when
>> put all together. I have noted a number of places where I
>> > actually am not sure how to implement something, and fixing those will
>> resolve this DISCUSS, but IMO you really should totally
>> > rewrite this document either (a) as a variant of ICE or (b) as an
>> entirely new document not with a pile of new text and then
>> > references out to ICE sections.
>>
>> I haven't been involved in the work on this draft, so I may be wrong, but
>> I did review the document and my understanding is that RFC 5770 is the
>> "variant of ICE", and this document is a modification/extension to RFC 5770.
>>
>
> This document is a variant of ICE in the sense that it is ICE-like and
> explicitly depends on quite a bit of ICE.
>
> -Ekr
>
>
>> Regards,
>>
>> Christer
>>
>>
>>
>

--000000000000ed6e58056b8e4d6d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, May 6, 2018 at 12:05 PM, Christer Holmberg <span dir=3D"ltr">&l=
t;<a href=3D"mailto:[email protected]" target=3D"_blank">chris=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">



<div dir=3D"auto">
Hi,
<div><br>
</div>
<div>The question is whether this document should re-define the HIP variati=
ons to ICE that RFC 5770 already does.</div></div></blockquote><div><br></d=
iv><div>That may be your question, but it&#39;s not my question. My questio=
n is that I&#39;m not sure this document is sufficiently clear and unambigi=
ous to implement, given its current structure.<br></div><div><br></div><div=
>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer<br>
<br>
<div id=3D"m_-957860738950567369AppleMailSignature">Sent from my iPhone</di=
v><div><div class=3D"h5">
<div><br>
On 6 May 2018, at 22.01, Eric Rescorla &lt;<a href=3D"mailto:[email protected]" =
target=3D"_blank">[email protected]</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sun, May 6, 2018 at 10:19 AM, Christer Holmbe=
rg <span dir=3D"ltr">
&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">chr=
ister.holmberg@ericsson.<wbr>com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<span><br>
&gt; I am very familiar with ICE and yet I found this document extremely ha=
rd to follow. The problem is that it cherry-picks pieces
<br>
&gt; of ICE and I&#39;m just not sure that it&#39;s a complete specificatio=
n when put all together. I have noted a number of places where I
<br>
&gt; actually am not sure how to implement something, and fixing those will=
 resolve this DISCUSS, but IMO you really should totally
<br>
&gt; rewrite this document either (a) as a variant of ICE or (b) as an enti=
rely new document not with a pile of new text and then
<br>
&gt; references out to ICE sections.<br>
<br>
</span>I haven&#39;t been involved in the work on this draft, so I may be w=
rong, but I did review the document and my understanding is that RFC 5770 i=
s the &quot;variant of ICE&quot;, and this document is a modification/exten=
sion to RFC 5770.<br>
</blockquote>
<div><br>
</div>
<div>This document is a variant of ICE in the sense that it is ICE-like and=
 explicitly depends on quite a bit of ICE.</div>
<div><br>
</div>
<div>-Ekr</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div></div></div>
</div>

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

--000000000000ed6e58056b8e4d6d--


--===============6289246378200427062==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hipsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/hipsec

--===============6289246378200427062==--