About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Fw: (ngtrans) I-D ACTION:draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt

  • From: "Thomas Trede" < >
  • Date: Fri, 15 Jan 1999 14:26:24 +0100
  • Reply-to: "Thomas Trede" < >

FYI.

Regards,
  Thomas Trede

-----Original Message-----
From: Internet-Drafts@localhost Internet-Drafts@localhost
To: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;
<"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;>
Cc: ngtrans@localhost ngtrans@localhost
Date: Donnerstag, 14. Januar 1999 00:19
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt


>A New Internet-Draft is available from the on-line Internet-Drafts
directories.
>This draft is a work item of the Next Generation Transition Working Group
>of the IETF.
>
> Title : Assignment of IPv4 Global Addresses to
>                          IPv6 Hosts (AIIH)
> Author(s) : J. Bound
> Filename : draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt
> Pages : 18
> Date : 12-Jan-99
>
>   The initial deployment of IPv6 will require a tightly coupled use of
>   IPv4 addresses to support the interoperation of IPv6 and IPv4.  Nodes
>   will be able to be deployed with IPv6 addresses, but will still need
>   to communicate with IPv4 nodes that do not have a dual IP layer
>   supporting both IPv4 and IPv6.  This specification defines a
>   mechanism called Assignment of IPv4 Global Addresses to IPv6 Hosts
>   (AIIH), which will assign an IPv6 Host a temporary IPv4 Global
>   Address, which can be used to communicate with a Host that supports
>   IPv4 or IPv4/IPv6.  An objective of this specification is to avoid
>   the use of address translation for the deployment of IPv6 in a
>   network.  Another objective is to demonstrate that IPv6 Addresses can
>   be deployed now instead of non-Global IPv4 Addresses within an
>   Intranet.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-01.
txt
>
>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-ngtrans-assgn-ipv4-addrs-01.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
> mailserv@localhost.
>In the body type:
> "FILE /internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-01.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.
>
<ftp://ftp/internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt>

  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community