Re: [Ietf-behave] I-D ACTION:draft-ietf-behave-rfc3489bis-05.txt
Hi,
if not creating the registry was not an oversight but a conscious
decision, I am OK with it.
Cheers,
Gonzalo
Rohan Mahy wrote:
Gonzalo,
The purpose of a registry is to make sure that there are no conflicts
and that one specific item in a large number of items can be easily
found. It is not necessary to place in the registry every element of
any protocol.
I am skeptical that the IETF will ever define a new address family. The
IPv6 address space is large enough to address every atom in the known
universe. If the IETF defines a new address family there will be such a
substantial number of changes needed to STUN (for example replacing all
the attributes that can contain IP addresses). I am confident that
there will be no conflicts at that time with other address families and
that the community will be able to notice the change without consulting
a registry.
thanks,
-rohan
On Oct 28, 2006, at 9:17, Gonzalo Camarillo wrote:
Hi,
this draft defines two address families but does not create an IANA
registry for them. It should, in case it is necessary to register more
address families at some point in the future.
Thanks,
Gonzalo
Internet-Drafts@xxxxxxxx wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Behavior Engineering for Hindrance
Avoidance Working Group of the IETF.
Title : Simple Traversal Underneath Network Address
Translators (NAT) (STUN)
Author(s) : J. Rosenberg, et al.
Filename : draft-ietf-behave-rfc3489bis-05.txt
Pages : 61
Date : 2006-10-26
Simple Traversal Underneath NATs (STUN) is a lightweight protocol
that serves as a tool for application protocols in dealing with NAT
traversal. It allows a client to determine the IP address and port
allocated to them by a NAT and to keep NAT bindings open. It can
also serve as a check for connectivity between a client and a server
in the presence of NAT, and for the client to detect failure of the
server. STUN works with many existing NATs, and does not require any
special behavior from them. As a result, it allows a wide variety of
applications to work through existing NAT infrastructure.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-rfc3489bis-05.txt
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@xxxxxxxx with the word unsubscribe in the body
of the message. You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce to change your
subscription settings.
Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then "get
draft-ietf-behave-rfc3489bis-05.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@xxxxxxxxx
In the body type:
"FILE /internet-drafts/draft-ietf-behave-rfc3489bis-05.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
------------------------------------------------------------------------
_______________________________________________
Ietf-behave mailing list
Ietf-behave@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/ietf-behave
