Re: [pcp] draft-ietf-pcp-proxy-01

<mohamed.boucadair@orange.com> Wed, 16 January 2013 13:55 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEDA321F889D for <pcp@ietfa.amsl.com>; Wed, 16 Jan 2013 05:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiBckhhG5NbK for <pcp@ietfa.amsl.com>; Wed, 16 Jan 2013 05:55:51 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 446DC21F8615 for <pcp@ietf.org>; Wed, 16 Jan 2013 05:55:51 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id EBA152DC7E1; Wed, 16 Jan 2013 14:55:49 +0100 (CET)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id D2F2B4C079; Wed, 16 Jan 2013 14:55:49 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Wed, 16 Jan 2013 14:55:49 +0100
From: mohamed.boucadair@orange.com
To: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>, "pcp@ietf.org" <pcp@ietf.org>
Date: Wed, 16 Jan 2013 14:55:48 +0100
Thread-Topic: draft-ietf-pcp-proxy-01
Thread-Index: AQHNfFtQglT2FR9y7E+uIv3odqkuvJghxfUAgCsiAtA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EA601E445@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120817092347.27948.43556.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36E512B43CD@PUEXCB1B.nanterre.francetelecom.fr> <A6A061BEE5DDC94A9692D9D81AF776DF2D53F2D6@szxeml527-mbx.china.huawei.com>
In-Reply-To: <A6A061BEE5DDC94A9692D9D81AF776DF2D53F2D6@szxeml527-mbx.china.huawei.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.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.1.16.113630
Subject: Re: [pcp] draft-ietf-pcp-proxy-01
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 16 Jan 2013 13:55:53 -0000

Dear Cathy,

Apologies for the delay to answer this message. 

I wonder whether your case isn't covered in this text (Section 9); especially the last sentence:

   Upon receipt of an unsolicited ANNOUNCE response from a PCP Server,
   the PCP Proxy proceeds to renewing the mappings and checks whether
   there are changes compared to a local cache if it is maintained by
   the PCP Proxy.  If no change is detected, no unsolicited ANNOUNCE is
   generated towards PCP Clients.  If a change is detected, the PCP
   Proxy MUST generate unsolicited ANNOUNCE message(s) to appropriate
   PCP Clients.  If the PCP Proxy does not maintain a local cache for
   the mappings, unsolicited ANNOUNCE messages are relayed to PCP
   Clients.


If not, please let me know what change you want to see added to that text. Thanks.

Cheers,
Med 

>-----Message d'origine-----
>De : Zhouqian (Cathy) [mailto:cathy.zhou@huawei.com] 
>Envoyé : jeudi 20 décembre 2012 09:28
>À : BOUCADAIR Mohamed OLNC/OLN; pcp@ietf.org
>Objet : RE: draft-ietf-pcp-proxy-01
>
>Dear Med and all,
>When looking over section 10 of this document, there is one 
>more advanced feature in my mind that may be added for PCP proxy. 
>In [I-D.ietf-pcp-base], the PCP server could send the ANNOUNCE 
>response to both multicast and unicast addresses. For 
>multicast address case, it only applies when the network is 
>layer2 network and there is a multicast link between PCP 
>client and PCP server. If there is no multicast link between 
>PCP client and PCP server, one access router (e.g., PCP proxy) 
>may perform the multicast address/unicast address conversion 
>function. When the PCP proxy receives the ANNOUNCE message 
>from the PCP server, it replaces the unicast address of itself 
>with the PCP client's multicast address and sends ANNOUNCE 
>message to the multicast address. It is required that the 
>network between the PCP proxy and the PCP client is layer2. 
>Any comments?
>
>Best Regards,
>Cathy
>
>
>> -----Original Message-----
>> From: pcp-bounces@ietf.org [mailto:pcp-bounces@ietf.org] On Behalf Of
>> mohamed.boucadair@orange.com
>> Sent: Friday, August 17, 2012 5:33 PM
>> To: pcp@ietf.org
>> Subject: [pcp] draft-ietf-pcp-proxy-01
>> 
>> Dear all,
>> 
>> A new version is now available online:
>> http://tools.ietf.org/html/draft-ietf-pcp-proxy-01
>> 
>> The main changes in -01 are as follows:
>> 
>> * The reference architecture is updated: the PCP proxy is 
>not restricted to
>> the CP router deployment case.
>> * Add a new section to specify the behaviour when the PCP 
>Proxy is not
>> co-located with a NAT function
>> * Add a new section for mappings repair
>> * More discussion for the multiple PCP Servers scenario
>> * Text is cleanup
>> 
>> A detailed diff is available here:
>> 
>>  http://www.ietf.org/rfcdiff?url2=draft-ietf-pcp-proxy-01
>> 
>> Please review this new version and provide input.
>> 
>> Cheers,
>> Med
>> _______________________________________________
>> pcp mailing list
>> pcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcp
>