Re: [dhcwg] draft-bpw-pcp-dhcp-00.txt

<mohamed.boucadair@orange-ftgroup.com> Tue, 12 October 2010 14:36 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF5923A6823 for <dhcwg@core3.amsl.com>; Tue, 12 Oct 2010 07:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.067
X-Spam-Level:
X-Spam-Status: No, score=-2.067 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDcdmP-gjNiU for <dhcwg@core3.amsl.com>; Tue, 12 Oct 2010 07:36:12 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by core3.amsl.com (Postfix) with ESMTP id 631E13A699E for <dhcwg@ietf.org>; Tue, 12 Oct 2010 07:36:12 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 0043A2ACB84; Tue, 12 Oct 2010 16:37:26 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id AAC15C8064; Tue, 12 Oct 2010 16:37:25 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Tue, 12 Oct 2010 16:37:25 +0200
From: mohamed.boucadair@orange-ftgroup.com
To: Ralph Droms <rdroms.ietf@gmail.com>
Date: Tue, 12 Oct 2010 16:37:24 +0200
Thread-Topic: [dhcwg] draft-bpw-pcp-dhcp-00.txt
Thread-Index: ActqGF0JXLxckIHFSHS9GyG9DleoLAAAVW4Q
Message-ID: <12549_1286894245_4CB472A5_12549_79407_1_94C682931C08B048B7A8645303FDC9F327C1009107@PUEXCB1B.nanterre.francetelecom.fr>
References: <F4BBCA3A-64E1-4929-BDFB-F7EBFAD918E3@nominum.com> <10443_1286813519_4CB3374F_10443_28372_1_94C682931C08B048B7A8645303FDC9F327C1008BD5@PUEXCB1B.nanterre.francetelecom.fr> <2ACB3C3E-D437-49EC-8976-C8BC79ABEA6D@nominum.com> <9832_1286863080_4CB3F8E8_9832_26703_1_94C682931C08B048B7A8645303FDC9F327C1008C4D@PUEXCB1B.nanterre.francetelecom.fr> <EC9E3C74-2E54-4528-B5E5-DC787B081827@gmail.com>
In-Reply-To: <EC9E3C74-2E54-4528-B5E5-DC787B081827@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.10.12.135417
Cc: "dhcwg@ietf.org Group" <dhcwg@ietf.org>, Lemon Ted <Ted.Lemon@nominum.com>, Reinaldo Penno <rpenno@juniper.net>
Subject: Re: [dhcwg] draft-bpw-pcp-dhcp-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 14:36:14 -0000

Dear Ralph,

You are right the concatenation behaviour should be specified for the host so that this mechanism to work. This can be simplified if only a hostname is conveyed in the option instead of the FQDN (e.g., "cgn" or "aftr") and a domain search name (e.g., "city1.example.com"). The concatenation would lead to "cgn.city1.example.com". If in the same DHCP offer, a name for SBC/P-CSCF (e.g., "sbc") is provided, the host would build its specific FQDN for the SBC/P-CSCF (i.e., "sbc.city1.example.com"). This concatenation operation can be avoided if the specific FQDN is included in the AFTR name option.

Cheers,
Med


-----Message d'origine-----
De : Ralph Droms [mailto:rdroms.ietf@gmail.com] 
Envoyé : mardi 12 octobre 2010 16:19
À : BOUCADAIR Mohamed NCPI/NAD/TIP
Cc : Lemon Ted; dhcwg@ietf.org Group; Reinaldo Penno
Objet : Re: [dhcwg] draft-bpw-pcp-dhcp-00.txt

I don't understand how the mechanism in msg01649.html can work.  As I read the description, the DHCP server sends both "a generic FQDN of the AFTR [and] a suffix in the dns search list option."  The host combines those two strings into an FQDN for the service it is trying to discover.  Without some explicit rules about what part of the AFTR FQDN is replaced by which suffix in the DNS search list option, what is the expected behavior of the host?

- Ralph

On Oct 12, 2010, at 1:57 AM 10/12/10, <mohamed.boucadair@orange-ftgroup.com> <mohamed.boucadair@orange-ftgroup.com> wrote:

> Dear Ted,
> 
> One of the main use cases of the PCP is to control Carrier Grade NAT such as DS-Lite CGN or NAT64. It is likely that the PCP Server be co-located with the CGN function. A similar use case is discussed in http://www.ietf.org/mail-archive/web/softwires/current/msg01649.html: load-balancing.
> 
> Cheers,
> Med 
> 
> -----Message d'origine-----
> De : Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Envoyé : lundi 11 octobre 2010 19:01
> À : BOUCADAIR Mohamed NCPI/NAD/TIP
> Cc : Reinaldo Penno; Dan Wing; dhcwg@ietf.org Group
> Objet : Re: draft-bpw-pcp-dhcp-00.txt 
> 
> On Oct 11, 2010, at 9:11 AM, <mohamed.boucadair@orange-ftgroup.com> <mohamed.boucadair@orange-ftgroup.com> wrote:
> 
>> As for the options, what about defining a single option with sub-code field which indicates whether the option conveys an IP address or a FQDN? Is this acceptable?
> 
> No.   Why do you want this?
> 
> 
> *********************************
> 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.
> ********************************
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


*********************************
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.
********************************