RE: [NSIS] GIST over GIST-unaware NATs
"Hancock, Robert" <robert.hancock@roke.co.uk> Thu, 12 October 2006 09:35 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXwyP-0000pa-Pp; Thu, 12 Oct 2006 05:35:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXwyO-0000of-Jj for nsis@ietf.org; Thu, 12 Oct 2006 05:35:28 -0400
Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXwyN-0002aU-3I for nsis@ietf.org; Thu, 12 Oct 2006 05:35:28 -0400
Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id k9C9Wi8d017510; Thu, 12 Oct 2006 10:32:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] GIST over GIST-unaware NATs
Date: Thu, 12 Oct 2006 10:32:44 +0100
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C50157A93D@rsys005a.comm.ad.roke.co.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NSIS] GIST over GIST-unaware NATs
Thread-Index: AcbtzINuofKr9XHaT36po+kF3ZZMtAAFDl8Q
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: Martin Stiemerling <stiemerling@netlab.nec.de>, john.loughney@nokia.com
X-MailScanner-roke-co-uk: Found to be clean
X-MailScanner-roke-co-uk-SpamCheck:
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: fu@cs.uni-goettingen.de, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org
hi, just a note to the effect that I was planning to cover point (1) below (detection of the unaware NAT by header analysis) in the GIST spec in section 7.2 (see email discussions at http://www1.ietf.org/mail-archive/web/nsis/current/msg06710.html) and include an informative reference to andreas' draft. r. > -----Original Message----- > From: Martin Stiemerling [mailto:stiemerling@netlab.nec.de] > Sent: 12 October 2006 08:03 > To: <john.loughney@nokia.com> > Cc: fu@cs.uni-goettingen.de; nsis@ietf.org > Subject: Re: [NSIS] GIST over GIST-unaware NATs > > > I'm in favour of having such document dealing with GIST-unaware NAT > traversal. However, I haven't read the latest version of draft- > pashalidis-nsis-gist-legacynats-00 by now (on my record for the next > days). > > Martin > > Am 12.10.2006 um 05:14 schrieb <john.loughney@nokia.com> > <john.loughney@nokia.com>: > > > Actually, I think this should be added as a WG document. > > > > Comments? > > John > > > >> -----Original Message----- > >> From: ext Xiaoming Fu [mailto:fu@cs.uni-goettingen.de] > >> Sent: 11 October, 2006 22:49 > >> To: nsis@ietf.org > >> Subject: [NSIS] GIST over GIST-unaware NATs > >> > >> Hi all, > >> > >> There were some IESG discussions on GIST over GIST-unaware > NATs. I > >> read through draft-pashalidis-nsis-gist-legacynats-00 > >> and found it makes a number of clarifications on this issue: > >> > >> - The presence of a GIST-unaware NAT can be detected by comparing > >> headers of the GIST query-response procedure message in the two > >> adjacent non-NAT GIST nodes. > >> > >> - Upon the detection of such a NAT (and affiliated rules), > these two > >> GIST nodes can then establish a UDP tunnel between them, and > >> encapsulate the GIST messages (query-response-...) into > the tunnel, > >> and the outgoing tunnel endpoints decapsulate the messages > into the > >> desired format. > >> > >> - The draft also gives detailed description on GIST signaling and > >> data traffic processing in both the case where a NAT is > located close > >> to the NI and the case where a NAT is close to the NR. The > rationale > >> looks fine to me. If there is an implementation demoing this, it > >> would be even nicer. > >> > >> What do others think? > >> Xiaoming > >> > >> _______________________________________________ > >> nsis mailing list > >> nsis@ietf.org > >> https://www1.ietf.org/mailman/listinfo/nsis > >> > > > > _______________________________________________ > > nsis mailing list > > nsis@ietf.org > > https://www1.ietf.org/mailman/listinfo/nsis > > > _______________________________________________ > nsis mailing list > nsis@ietf.org > https://www1.ietf.org/mailman/listinfo/nsis > _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] GIST over GIST-unaware NATs Xiaoming Fu
- RE: [NSIS] GIST over GIST-unaware NATs john.loughney
- Re: [NSIS] GIST over GIST-unaware NATs Martin Stiemerling
- RE: [NSIS] GIST over GIST-unaware NATs Hancock, Robert
- RE: [NSIS] GIST over GIST-unaware NATs Georgios Karagiannis