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

--===============1752646353015655203==
Content-Type: multipart/alternative; boundary="000000000000099d00056b8e2f5d"

--000000000000099d00056b8e2f5d
Content-Type: text/plain; charset="UTF-8"

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
>
>
>

--000000000000099d00056b8e2f5d
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 10:19 AM, 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">Hi,<br>
<span class=3D""><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 va=
riant of ICE in the sense that it is ICE-like and explicitly depends on qui=
te a bit of ICE.</div><div><br></div><div>-Ekr</div><div><br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
</blockquote></div><br></div></div>

--000000000000099d00056b8e2f5d--


--===============1752646353015655203==
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

--===============1752646353015655203==--