Re: [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
"Reinaldo Penno (repenno)" <repenno@cisco.com> Thu, 19 July 2012 16:18 UTC
Return-Path: <repenno@cisco.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 EA9D421F86A8; Thu, 19 Jul 2012 09:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 bqtzgVANHGZp; Thu, 19 Jul 2012 09:18:36 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id EBE5F21F8672; Thu, 19 Jul 2012 09:18:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=repenno@cisco.com; l=4947; q=dns/txt; s=iport; t=1342714769; x=1343924369; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=RKERFEEvRvV+F3yzQ8zB3/0M1fr5oEZ9M6O4ibKmd+g=; b=kXGdq0vCKKAxk9PGKOhdyvklbtcy0jFW/s444oroN5mQ7abiqm19Ma2M AbFM/ffxV6cK+OEAeIehbtP/6zmjRZAJgFfsLw3DBFLVn6suIR/mJc//a c5u0PCDKWr4HjrUbnPPBddOeCSH81Q1DCrgPHM1KETxMq/jjTzP8UKfyL 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEwzCFCtJXHB/2dsb2JhbABFuUCBB4IcBAEBAQQBAQEPAQpRBgUSAQgYIzILFBECBAENBQkZhScHgiQKAwwLnjegCIplZxQEhngDiBiNLI4jgWaCX4FW
X-IronPort-AV: E=Sophos;i="4.77,615,1336348800"; d="scan'208";a="103492726"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 19 Jul 2012 16:19:29 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q6JGJTZa024543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Jul 2012 16:19:29 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.177]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0298.004; Thu, 19 Jul 2012 11:19:25 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Simon Perreault <simon.perreault@viagenie.ca>
Thread-Topic: [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
Thread-Index: AQHNZcpD5zVzSRWO2Ue47DGuTsCIiQ==
Date: Thu, 19 Jul 2012 16:19:25 +0000
Message-ID: <CC2D80C2.8041%repenno@cisco.com>
In-Reply-To: <CF11FD8E-395B-44CC-9F31-60494B5E668F@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.65.29]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19050.003
x-tm-as-result: No--51.962200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1771A1264D08E74EB0B132EF74003450@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
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: Thu, 19 Jul 2012 16:18:37 -0000
Humm...I'm not sure I agree. "However, if a router does implement EGP it also MUST IMPLEMENT BGP." http://www.ietf.org/rfc/rfc1812.txt Or look at the requirements for IPv6 CEs or any other device that needs to interoperate with others. On 7/19/12 9:05 AM, "Hannes Tschofenig" <hannes.tschofenig@gmx.net> wrote: >I agree with Martin's remarks. > >On Jul 19, 2012, at 3:51 PM, Simon Perreault wrote: > >> Behaviers, PCPers, >> >> During IESG review of draft-ietf-behave-lsn-requirements, a DISCUSS was >>filed regarding the PCP requirement. Details below. >> >> I think this DISCUSS needs to be discussed. So please discuss. >> >> Please reply to behave@ietf.org. >> >> Thanks, >> Simon >> >> >> -------- Message original -------- >> Sujet: Re: Martin Stiemerling's Discuss on >>draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT) >> Date : Thu, 19 Jul 2012 10:46:42 +0200 >> De : Martin Stiemerling <martin.stiemerling@neclab.eu> >> Pour : Simon Perreault <simon.perreault@viagenie.ca> >> Copie à : The IESG <iesg@ietf.org>, <behave-chairs@tools.ietf.org>, >><draft-ietf-behave-lsn-requirements@tools.ietf.org> >> >> Hi Simon, all, >> >> On 07/17/2012 11:11 PM, Simon Perreault wrote: >>> Le 2012-07-17 16:42, Martin Stiemerling a écrit : >>>>> Each and every CGN MUST have PCP and MUST follow the constraints. >>>>>I'll >>>>> fix the text in a later revision. >>>> >>>> Can we mandate a specific protocol to be used for this or can we only >>>> mandate that such a type of protocol is being used? I don't see the >>>>IETF >>>> in the position to mandate this type of protocol for CGNs. >>>> >>>> There are other protocols out there which might be suitable. Note >>>>that I >>>> am co-author of some, but this isn't the reason for the question. I do >>>> not get any reward if I promote these protocols. >>>> >>>> It is more: >>>> do we need to constrain CGN deployments to a protocol (PCP) which is >>>> developed right now, or are we open to existing or future protocols, >>>>or >>>> whatever folks deploying this deem right? >>>> >>>> I would propose to change REQ-9 to : >>>> REQ-9: A CGN MUST include a middlebox control protocol that allows >>>> manipulation of CGN bindings with the following contstraints <list >>>>items >>>> A and B> >>>> REQ-9a: If PCP is used these contstraints MUST be applied in addition >>>>to >>>> contraints A and B: >>>> <list items C and D> >>> >>> That was discussed in IETF 81 (Québec). Here's the extract from the >>> minutes: >>> >>> Stuart Cheshire: ietf has one port forwarding protocol, which >>> is PCP, so we should require it by name >> >> There are multiple middlebox control protocols published by the IETF >> (standards track and experimental) and I have not seen any call for >> consensus on what **the** IETF's middlebox control is, neither I have >> seen any RFC that states this. >> >> I do not see that an individual can declare IETF consensus based on his >> own opinion. >> >> >>> >>> Dave Thaler: I agree. PCP doc is in final stages. >> >> Again, an opinion of an individual. Nothing wrong about it, but it does >> not state IETF consensus. >> >>> >>> There was consensus from the WG. In consequence, the text was changed >>> from this (-02): >>> >>> A CGN SHOULD support a port forwarding protocol such as the >>> Port Control Protocol [I-D.ietf-pcp-base]. >>> >>> to this (-03): >>> >>> A CGN SHOULD include a Port Control Protocol server >>> [I-D.ietf-pcp-base]. >>> >>> (That requirement later became a MUST, but that's orthogonal to what >>> protocol we require.) >> >> I do not see that the IETF can mandate what protocols are being used to >> control a device. The market will decide! >> >> For instance, the is no MUST required that routers implement BGP. It is >> good to do this, but if one decides to go for IS-IS (or whatever) that >> is just fine. >> >> Another example, there is also no MUST requirement that routers, or >> hosts in general, have to implement SNMP. >> >> However, I can see the immediate need to mandate that a CGN SHOULD/MUST >> support a middlebox control protocol that is able to install and >> maintain NAT bindings. >> >> Martin >> >> -- >> martin.stiemerling@neclab.eu >> >> NEC Laboratories Europe - Network Research Division NEC Europe Limited >> Registered Office: NEC House, 1 Victoria Road, London W3 6BL >> Registered in England 283 >> >> >> _______________________________________________ >> pcp mailing list >> pcp@ietf.org >> https://www.ietf.org/mailman/listinfo/pcp > >_______________________________________________ >pcp mailing list >pcp@ietf.org >https://www.ietf.org/mailman/listinfo/pcp
- [pcp] Fwd: Re: Martin Stiemerling's Discuss on dr… Simon Perreault
- Re: [pcp] Fwd: Re: Martin Stiemerling's Discuss o… Sam Hartman
- Re: [pcp] Fwd: Re: Martin Stiemerling's Discuss o… Hannes Tschofenig
- Re: [pcp] Fwd: Re: Martin Stiemerling's Discuss o… Reinaldo Penno (repenno)
- Re: [pcp] [BEHAVE] Fwd: Re: Martin Stiemerling's … Simon Perreault
- Re: [pcp] [BEHAVE] Fwd: Re: Martin Stiemerling's … Sam Hartman
- Re: [pcp] [BEHAVE] Fwd: Re: Martin Stiemerling's … David Harrington