IETF Logo Mail Archive

Re: [v6ops] PCP server in draft-ietf-v6ops-6204bis

Wuyts Carl <Carl.Wuyts@technicolor.com> Mon, 30 January 2012 08:05 UTC

Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE4D21F85FC; Mon, 30 Jan 2012 00:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.158
X-Spam-Level:
X-Spam-Status: No, score=-6.158 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyVL1063dxOK; Mon, 30 Jan 2012 00:05:57 -0800 (PST)
Received: from na3sys009aog103.obsmtp.com (na3sys009aog103.obsmtp.com [74.125.149.71]) by ietfa.amsl.com (Postfix) with ESMTP id CDEBC21F85F7; Mon, 30 Jan 2012 00:05:44 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob103.postini.com ([74.125.148.12]) with SMTP ID DSNKTyZPVyAPgPcfFotdy3GHPwM1jD1T3cXa@postini.com; Mon, 30 Jan 2012 00:05:57 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Mon, 30 Jan 2012 09:03:39 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.206]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Mon, 30 Jan 2012 09:03:41 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: james woodyatt <jhw@apple.com>, Francis Dupont <Francis.Dupont@fdupont.fr>
Date: Mon, 30 Jan 2012 09:03:38 +0100
Thread-Topic: [v6ops] PCP server in draft-ietf-v6ops-6204bis
Thread-Index: AczerrnXT7Ic2xwYQ+K4iDFQAcxmvAAdrdKQ
Message-ID: <867F4B6A1672E541A94676D556793ACD0E91F41122@MOPESMBX01.eu.thmulti.com>
References: <201201291608.q0TG8oCF098440@givry.fdupont.fr> <85BE2EBF-C8AC-45E1-BF93-1E3066AD3172@apple.com>
In-Reply-To: <85BE2EBF-C8AC-45E1-BF93-1E3066AD3172@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_867F4B6A1672E541A94676D556793ACD0E91F41122MOPESMBX01eut_"
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "pcp@ietf.org" <pcp@ietf.org>, "Ole Troan (otroan)" <otroan@cisco.com>, "draft-ietf-v6ops-6204bis@tools.ietf.org" <draft-ietf-v6ops-6204bis@tools.ietf.org>
Subject: Re: [v6ops] PCP server in draft-ietf-v6ops-6204bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 08:05:58 -0000

+ 1 on Barbara's statement.  V6ops should take no position to select a mechanism here.  PCP seems to get the most attention but it should not make v6ops to decide to take it along explicitly in RFC6204bis.

Regs
Carl


From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of james woodyatt
Sent: zondag 29 januari 2012 18:52
To: Francis Dupont
Cc: v6ops@ietf.org; pcp@ietf.org; Ole Troan (otroan); draft-ietf-v6ops-6204bis@tools.ietf.org
Subject: Re: [v6ops] PCP server in draft-ietf-v6ops-6204bis

On Jan 29, 2012, at 08:08 , Francis Dupont wrote:

UPnP IGD v2 does the job, it was just published after the PCP effort beginning.

Was it published under terms that permit IETF to cite it in a standards track document as a normative requirement?  This has, in the past, been a problem with UPnP IGDv1.



--
j h woodyatt <jhw@apple.com<mailto:jhw@apple.com>>

v2.23.0 | Report a Bug | By Email