Re: [pcp] DNS Indirection

<mohamed.boucadair@orange-ftgroup.com> Tue, 22 February 2011 17:03 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: pcp@core3.amsl.com
Delivered-To: pcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB59B3A6930 for <pcp@core3.amsl.com>; Tue, 22 Feb 2011 09:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.171
X-Spam-Level:
X-Spam-Status: No, score=-3.171 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, 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 S-ZgGe-hEv6Y for <pcp@core3.amsl.com>; Tue, 22 Feb 2011 09:03:33 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by core3.amsl.com (Postfix) with ESMTP id C1D2B3A6924 for <pcp@ietf.org>; Tue, 22 Feb 2011 09:03:32 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 906EC18C122; Tue, 22 Feb 2011 18:04:16 +0100 (CET)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 715F235C018; Tue, 22 Feb 2011 18:04:16 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.13]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Tue, 22 Feb 2011 18:04:16 +0100
From: mohamed.boucadair@orange-ftgroup.com
To: Dan Wing <dwing@cisco.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Tue, 22 Feb 2011 18:04:14 +0100
Thread-Topic: [pcp] DNS Indirection
Thread-Index: AcvPP3/kiIaFko4xRQSDjrN8nhXyAAAXXPhgAMVZcDA=
Message-ID: <20027_1298394256_4D63EC90_20027_174071_1_94C682931C08B048B7A8645303FDC9F33C45773671@PUEXCB1B.nanterre.francetelecom.fr>
References: <3155_1298014995_4D5E2313_3155_348950_1_94C682931C08B048B7A8645303FDC9F33C444C8C5F@PUEXCB1B.nanterre.francetelecom.fr> <0ab201cbcf9d$b2414c30$16c3e490$@com>
In-Reply-To: <0ab201cbcf9d$b2414c30$16c3e490$@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: 2011.2.22.143317
Subject: Re: [pcp] DNS Indirection
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 17:03:34 -0000

Hi Dan,

I fully agree with your analysis. 

I will remove that note from the I-D and add a sentence to record this. 

Cheers,
Med 

-----Message d'origine-----
De : Dan Wing [mailto:dwing@cisco.com] 
Envoyé : vendredi 18 février 2011 19:57
À : BOUCADAIR Mohamed OLNC/NAD/TIP; pcp@ietf.org
Objet : RE: [pcp] DNS Indirection

> -----Original Message-----
> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
> mohamed.boucadair@orange-ftgroup.com
> Sent: Thursday, February 17, 2011 11:43 PM
> To: pcp@ietf.org
> Subject: [pcp] DNS Indirection
> 
> Dear all,
> 
> We would like to have a feedback about an open question we have in
> http://tools.ietf.org/html/draft-bpw-pcp-dhcp-02 (Section 5.2):
> 
>       [Ed.  Is there a value to consider a level of indirection (e.g.,
>       SRV)? (1) to use an arbitrary port number for PCP Server instead
>       of the default port, (2) detect whether a security channel is in
>       use (using the transport protocol)]
> 
> The current text assumes there is no indirection.

There is value in SRV.  But there is additional complexity and additional
failure modes.  To my knowledge the only (relatively) widely deployed
application that uses SRV in real life is XMPP.  Just last year, Cisco 
bumped into a bug where our devices borked SRV responses that were 
longer than expected.  (1) would be neat to have, but I am not convinced
we necessarily need it.  (2) can be done without SRV; lots of protocols
without SRV already negotiate or force upgrading to a secure channel.

I vote for K.I.S.S.  That is, don't do SRV.

-d



********************************************************************************
IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles
et peuvent etre protegees par la loi.
Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus.
Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler  a l expediteur et effacer ce message 
et tous les fichiers eventuellement attaches.
Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite.
Tout message electronique est susceptible d alteration.
A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie.
De meme, il appartient au destinataire de s assurer de l absence de tout virus.

IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is
intended only for the named recipient(s) above.
If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message.
Any unauthorized view, usage or disclosure ofthis message is prohibited.
Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified.
Additionally the recipient should ensure they are actually virus free.
********************************************************************************