How about define a new option just for FQDN? Will this address the IESG¹s
concern?


On 10/7/10 11:24 PM, "Tomasz Mrugalski" <tomasz.mrugal...@gmail.com> wrote:

> Roberta, Mohamed,
> AFTR name option was removed as a result of a concerns raised by Jari Arkko
> and Ralph Droms during IESG review. They were very clear that defining two
> options to configure the same parameter is not acceptable.
> 
> Regarding scenario mentioned by Mohamed, since you are already differentiating
> between different locations (as I understand in your scenario different
> locations provide different DNS addresses that resolve the same AFTR FQDN to
> different addresses, right?), you may do this explicitly and provide different
> AFTR addresses. Would that solve the problem?
> 
> Hope that helps.
> Tomek
> 
> On Thu, Oct 7, 2010 at 11:58 AM, Maglione Roberta
> <roberta.magli...@telecomitalia.it> wrote:
>> Hello All,
>>     I fully agree with Med, both AFTR IP address and AFTR name options are
>> needed, in order to be able to handle different scenarios.
>> We really would like to see both of them back in the draft.
>> 
>> Best regards,
>> Roberta
>> 
>> -----Original Message-----
>> From: softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] On
>> Behalf Of mohamed.boucad...@orange-ftgroup.com
>> Sent: giovedì 7 ottobre 2010 10.07
>> To: draft-ietf-softwire-ds-lite-tunnel-opt...@tools.ietf.org; Softwire Chairs
>> Cc: softwires@ietf.org
>> Subject: [Softwires] DHCPv6 AFTR name option is needed
>> 
>> Dear authors, chairs,
>> 
>> We are surprised to see the AFTR name option being removed from the latest
>> version of this draft:
>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-softwire-ds-lite-tunnel-option-
>> 05.txt
>> 
>> Is there any reason why this option has been removed?
>> 
>> We would like to see this option back to the draft and that *** both *** the
>> AFTR IP address and the name options are defined.
>> 
>> FWIW, one of the deployment use cases we are considering is the distribution
>> of the DS-Lite serviced customers among several (geo distributed) AFTRs by
>> combining the search domain name dhcpv6 option (Code 24) and a generic FQDN
>> conveyed in the AFTR name option. This would allow for a more controlled load
>> distribution among deployed AFTRs.
>> 
>> 
>> Cheers,
>> Med
>> 
>> 
>> -----Message d'origine-----
>> De : softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] De la
>> part de internet-dra...@ietf.org
>> Envoyé : lundi 27 septembre 2010 21:30
>> À : i-d-annou...@ietf.org
>> Cc : softwires@ietf.org
>> Objet : [Softwires] I-D
>> Action:draft-ietf-softwire-ds-lite-tunnel-option-05.txt
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Softwires Working Group of the IETF.
>> 
>> 
>>         Title           : Dynamic Host Configuration Protocol for IPv6
>> (DHCPv6) Option for Dual- Stack Lite
>>         Author(s)       : D. Hankins, T. Mrugalski
>>         Filename        : draft-ietf-softwire-ds-lite-tunnel-option-05.txt
>>         Pages           : 6
>>         Date            : 2010-09-27
>> 
>> This document specifies single DHCPv6 option which is meant to be
>> used by a Dual-Stack Lite client (Basic Bridging BroadBand element,
>> B4) to discover its Address Family Transition Router (AFTR) address.
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-softwire-ds-lite-tunnel-option
>> -05.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> 
>> *********************************
>> 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.
>> ********************************
>> 
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>> 
>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
>> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
>> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
>> abbiate ricevuto questo documento per errore siete cortesemente pregati di
>> darne immediata comunicazione al mittente e di provvedere alla sua
>> distruzione, Grazie.
>> 
>> This e-mail and any attachments is confidential and may contain privileged
>> information intended for the addressee(s) only. Dissemination, copying,
>> printing or use by anybody else is unauthorised. If you are not the intended
>> recipient, please delete this message and any attachments and advise the
>> sender by return e-mail, Thanks.
>> 
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
> 
> 
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to