We have submitted a new version of this document that I will be presenting 
later, in case you haven’t read the update, so you’re in-sync with the actual 
text as my presentation is based on this version.

https://datatracker.ietf.org/doc/draft-li-intarea-nat64-prefix-dhcp-option

Regards,
Jordi
 

-----Mensaje original-----
De: <[email protected]>
Responder a: <[email protected]>
Fecha: lunes, 27 de marzo de 2017, 1:03
Para: Jianping Wu <[email protected]>, Cong Liu <[email protected]>, Yong 
Cui <[email protected]>, Lishan Li <[email protected]>, Jordi 
Palet <[email protected]>, Jordi Palet Martinez 
<[email protected]>, Fred Baker <[email protected]>
Asunto: New Version Notification for 
draft-li-intarea-nat64-prefix-dhcp-option-01.txt

    
    A new version of I-D, draft-li-intarea-nat64-prefix-dhcp-option-01.txt
    has been successfully submitted by Lishan Li and posted to the
    IETF repository.
    
    Name:               draft-li-intarea-nat64-prefix-dhcp-option
    Revision:   01
    Title:              DHCPv6 Options for Discovery NAT64 Prefixes
    Document date:      2017-03-26
    Group:              Individual Submission
    Pages:              12
    URL:            
https://www.ietf.org/internet-drafts/draft-li-intarea-nat64-prefix-dhcp-option-01.txt
    Status:         
https://datatracker.ietf.org/doc/draft-li-intarea-nat64-prefix-dhcp-option/
    Htmlized:       
https://tools.ietf.org/html/draft-li-intarea-nat64-prefix-dhcp-option-01
    Htmlized:       
https://datatracker.ietf.org/doc/html/draft-li-intarea-nat64-prefix-dhcp-option-01
    Diff:           
https://www.ietf.org/rfcdiff?url2=draft-li-intarea-nat64-prefix-dhcp-option-01
    
    Abstract:
       Several IPv6 transition mechanisms require the usage of stateless or
       stateful translators (commonly named as NAT64) able to allow IP/ICMP
       communication between IPv4 and IPv6 networks.
    
       Those translators are using either a default Well-Known Prefix (WKP),
       and/or one or several additional Network Specific Prefix (NSP), which
       need to be configured into the nodes willing to use the translator.
       Different translators will likely have different IPv6 prefixes, to
       attract traffic to the correct translator.  Thus, an automatic
       translator prefix discovery method is necessary.
    
       This document defines a DHCPv6-based method to inform DHCPv6 clients
       the set of IPv6 and IPv4 prefixes it serves.  This DHCPv6 option can
       be used by several transition mechanisms such as SIIT, 464XLAT, EAM.
    
                                                                                
      
    
    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    The IETF Secretariat
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the use of the 
individual(s) named above. If you are not the intended recipient be aware that 
any disclosure, copying, distribution or use of the contents of this 
information, including attached files, is prohibited.



_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to