Issue23

Issue Title GIMPS-aware NAT functions
Document: GIMPS Protocol Specification v07 Section: 7.3 partly
Category: Editorial Priority: May Fix
Status: Closed

Created on 2005-01-17.12:41:35 by reh, last changed 2005-10-03.08:50:45.

Messages
msg224 Author: reh Date: 2005-10-03.08:50:45
Section 7.2 has been extended and rewritten with a more precise description of
what the GIST nodes MUST/SHOULD do, accompanied by an informative description of
what NATs could do.
msg164 Author: admin Date: 2005-07-13.14:33:26
And updated the document reference too!
msg163 Author: admin Date: 2005-07-13.14:31:50
Updated section reference for -07. See also issue 22.
msg160 Author: andreas Date: 2005-07-13.11:49:07
A document which could serve as a basis for discussing the solution for this
issue is available at
http://www.tschofenig.com/drafts/draft-pashalidis-nsis-gimps-nattraversal-00.html
msg62 Author: admin Date: 2005-03-02.16:19:55
[updated to refer to -05 version.]
msg29 Author: reh Date: 2005-01-17.13:03:03
In particular, it would be good to know that the solution worked in the presence
of nested-NATs.
msg24 Author: reh Date: 2005-01-17.12:41:35
Most of the details of NAT traversal (for GIMPS-aware NATs) are a local
implementation matter. However, it might be useful to document how NAT traversal
is actually possible, in order to validate that the protocol itself is not
NAT-unfriendly, and also to provide some background rationale for some of the
details of the fundamental specification. The processing details could go in an
informative annex to the main GIMPS specification.
History
Date User Action Args
2005-10-03 08:50:45rehsetstatus: Pending -> Closed
messages: + msg224
2005-07-13 14:33:26adminsetdocument: GIMPS Protocol Specification v05 -> GIMPS Protocol Specification v07
messages: + msg164
2005-07-13 14:31:50adminsetsection: 6.3 partly -> 7.3 partly
messages: + msg163
2005-07-13 11:49:07andreassetmessages: + msg160
2005-03-02 16:19:55adminsetsection: n/a -> 6.3 partly
document: GIMPS Protocol Specification v04 -> GIMPS Protocol Specification v05
messages: + msg62
2005-01-17 13:03:03rehsetstatus: No Discussion -> Pending
messages: + msg29
2005-01-17 12:41:35rehcreate