[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: I-D ACTION:draft-ietf-v6ops-nap-06.txt
The name change was the result of an IESG DISCUSS item from Cullen
Jennings on the believe that 'NAP' as a term
was confusing for a variety of reasons. Middle ground solution was
elected and as result 'LNP' came out of pandora box (after an initial
change to NAP6).
The word 'Local Network Protection' refers to what is described in the
abstract. No change wrt to 'NAP'.
This name change was discussed with iesg@ietf.org and v6ops chairs in cc
(see 14th December 2006).
(I can fwd you and any who wants to know the mail if you can not locate
it)
Now after (exactly) 4 months... it is maybe a comment that should have
been spoken out loud 4 months ago when the suggestion for the name was
initially made.
There are many people and organisations waiting on this document to
become informational RFC, and I believe that we should aim to get the
document through the last step asap, and not re-discuss agreed items of
4 months ago.
Groetjes,
G/
-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On
Behalf Of Margaret Wasserman
Sent: Wednesday, March 14, 2007 1:29 PM
To: David Kessens; iesg@ietf.org
Cc: v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-v6ops-nap-06.txt
Hi All,
I would like to understand why the title of this document was changed at
the last minute. I also have at least a minor objection to the new
title, particularly to what it means by the word "protection".
The word "protection" in the original title referred to protecting the
end-to-end Internet architecture (the network architecture) from NAT.
In other words, we could use certain facilities in IPv6 instead of NAT
as a way to protect the end-to-end nature of IPv6 networks.
What does the word protection mean now, though? That the facilities in
this document protect the local network? From what?
Margaret
On Jan 11, 2007, at 3:50 PM, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IPv6 Operations Working Group of the
> IETF.
>
> Title : Local Network Protection for IPv6
> Author(s) : G. Van de Velde, et al.
> Filename : draft-ietf-v6ops-nap-06.txt
> Pages : 46
> Date : 2007-1-11
>
> Although there are many perceived benefits to Network Address
> Translation (NAT), its primary benefit of "amplifying" available
> address space is not needed in IPv6. In addition to NAT's many
> serious disadvantages, there is a perception that other benefits
> exist, such as a variety of management and security attributes that
> could be useful for an Internet Protocol site. IPv6 was designed
> with the intention of making NAT unnecessary, and this document
> shows
> how Local Network Protection (LNP) using IPv6 can provide the same
> or
> more benefits without the need for address translation.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-nap-06.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org 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-v6ops-nap-06.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@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-v6ops-nap-06.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.
> Content-Type: text/plain
> Content-ID: <2007-1-11122456.I-D@ietf.org>