Re: [BEHAVE] draft-boucadair-behave-dns-a64-00.txt [was RE: I-DAction:draft-ietf-behave-dns64-01.txt]

actually, i guess it makes more sense for the NSP prefix than for the WK 
prefix, since synthetic RR containing addresses witht he WKP can be 
distinguished by the WKP, i guess

Regards, marcelo


mohamed.boucadair@orange-ftgroup.com escribió:
> Dear Xuewei, all,
>
> The A64 proposal does not make any assumption about the type of the pref6 to be used. Both WKP and LIR prefixes are supported. We are currently updating the draft to describe a mode in which an authoritative server can be updated to support A64 (and therefore a LIR pref can be used).
>
> Cheers,
> Med 
>
> -----Message d'origine-----
> De : Xuewei Wang [mailto:wangxuewei@huawei.com] 
> Envoyé : vendredi 23 octobre 2009 10:12
> À : BOUCADAIR Mohamed NCPI/NAD/TIP; Christian Huitema; teemu.savolainen@nokia.com; ajs@shinkuro.com; behave@ietf.org
> Objet : [BEHAVE] draft-boucadair-behave-dns-a64-00.txt [was RE: I-DAction:draft-ietf-behave-dns64-01.txt]
>
> Hi, mohamed,
> I have noticed your new draft draft-boucadair-behave-dns-a64-00.  If i understand it correctly this draft makes DNS server to add a new a64 RR to represent an IPv4-mapped IPv6 addresses. Because the DNS server don't serve any specific NAT64s, so the prefix64 which the DNS server uses to construct a64 RR must be a Well-Known Prefix rather than a Network-Specific Prefix, is my understand correct?
>
>
> Xuewei Wang
> ----- Original Message -----
> From: <mohamed.boucadair@orange-ftgroup.com>
> To: "Christian Huitema" <huitema@microsoft.com>; <teemu.savolainen@nokia.com>; <ajs@shinkuro.com>; <behave@ietf.org>
> Sent: Thursday, October 22, 2009 7:44 PM
> Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt
>
>
>
> Dear Christian, all,
>
> FYI, we have submitted a draft to describe the A64 record for IPv4-mapped IPv6 addresses. An updated version of the draft will be submitted soon
>
> Title           : A64: DNS Resource Record for IPv4-mapped IPv6 Address
> Author(s)       : M. Boucadair, E. Burgey
> Filename        : draft-boucadair-behave-dns-a64-00.txt
> Pages           : 9
> Date            : 2009-10-18
>
> In this context of IPv4-IPv6 interconnection, several solutions have been proposed.  Some of these solutions require the definition of a new IPv4-mapped IPv6 address [I-D.ietf-behave-address-format] which is used to represent an IPv4-only host in an IPv6 realms and the definition of a new mechanism called DNS64 for synthesizing a AAAA record, representing an IPv4-mapped IPv6 address in the DNS system, from the A record representing the IPv4 address of the IPv4-only host [I-D.ietf-behave-dns64].  This IPv4-mapped IPv6 address, when managed by a translator, is to be considered as "fake" address in a DNS system since it is not necessarily assigned to any host's interface qualified by the associated name.  This document defines a new DNS record type and query type to identify IPv4-mapped IPv6 address [I-D.ietf-behave-address-format] from native IPv6 ones.  The new record type and query type aim at helping the remote party to enforce its policies and avoid NAT64 boxes when possible.  Native addresses are to be preferred.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-boucadair-behave-dns-a64-00.txt
>
>
> Cheers,
> Med
>
>  
>
> -----Message d'origine-----
> De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Christian Huitema
> Envoyé : mercredi 21 octobre 2009 18:40
> À : teemu.savolainen@nokia.com; ajs@shinkuro.com; behave@ietf.org
> Objet : Re: [BEHAVE] I-D Action:draft-ietf-behave-dns64-01.txt
>
>   
>> The draft contains question about multihoming:"In particular, how is 
>> the multi-homed host supposed to know that a given AAAA is synthetic?".
>>     
>
> Wonder about that too. Isn't the best solution to create a new record type, say A4A6, that would contain the mapped addresses of IPv4 only hosts?
>
> -- Christian Huitema
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
> *********************************
> This message and any attachments (the "message") are confidential and intended solely for the addressees. 
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration. 
> France Telecom Group shall not be liable for the message if altered, changed or falsified.
> If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
> ********************************
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> *********************************
> This message and any attachments (the "message") are confidential and intended solely for the addressees. 
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration. 
> France Telecom Group shall not be liable for the message if altered, changed or falsified.
> If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
> ********************************
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>