Re: [Pce] 答复: Ramblings of two old dogs

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 05 March 2013 12:31 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DB121F86EA for <pce@ietfa.amsl.com>; Tue, 5 Mar 2013 04:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
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 26GH3aGXPITx for <pce@ietfa.amsl.com>; Tue, 5 Mar 2013 04:31:55 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7D421F86DC for <pce@ietf.org>; Tue, 5 Mar 2013 04:31:54 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r25CVioR010181; Tue, 5 Mar 2013 12:31:46 GMT
Received: from 950129200 (089144192117.atnat0001.highway.a1.net [89.144.192.117]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r25CVfgo010099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 5 Mar 2013 12:31:43 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Oscar González de Dios' <ogondio@tid.es>
References: <014701cdf4d2$4a259960$de70cc20$@olddog.co.uk> <C636AF2FA540124E9B9ACB5A6BECCE6B1396A74F@szxeml535-mbx.china.huawei.com> <020201ce107d$6f3231c0$4d969540$@olddog.co.uk> <C636AF2FA540124E9B9ACB5A6BECCE6B13974D99@szxeml535-mbx.china.huawei.com> <512C67FB.5060607@cttc.es> <8DC6547C806B644F998A0566E79E15920F7D2FC4@DEMUMBX006.nsn-intra.net> <01fa01ce1787$127a93d0$376fbb70$@olddog.co.uk> <83B4BFD4-C93C-4271-8CAD-F7315F66FAA9@tid.es>
In-Reply-To: <83B4BFD4-C93C-4271-8CAD-F7315F66FAA9@tid.es>
Date: Tue, 05 Mar 2013 12:31:43 -0000
Message-ID: <031201ce199d$674d6b90$35e842b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEbr0aHqBqTIRDPJXEElxhEkwsLCgIUD3MTATbKSlcCV5+gLwGjurk4AdPr/ssCsyzJEQLG+VjTmYc2tdA=
Content-Language: en-gb
Cc: pce@ietf.org, "'Margaria, Cyril (NSN - DE/Munich)'" <cyril.margaria@nsn.com>
Subject: Re: [Pce] 答复: Ramblings of two old dogs
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2013 12:31:56 -0000

Hello Oscar,

> I fully agree it is important to keep functional elements separated. That
> does not mean a vendor cannot sell a single box with several
> functionalities... 

sell != try_to_sell  :-)

[snip]

> ergo PCEP can be used to provide topology information to the
> PCE... Wait! Heresy!!! IGP does that! TED seems sacred and
> forbidden for PCEP... Syllogism failed... But it seems reporting
> LSP state information is OK....   

Hold on a moment.
Where does it say that the IGP is (MUST be) used for the collection of information in the TED?
In 4655 we have:
   The TED may be fed by Interior
   Gateway Protocol (IGP) extensions or potentially by other means.

Does that mean it makes sense to have each node in the network reporting TED information "northbound"? That depends. It doesn't make sense to me to have two protocols simultaneously doing the same thing in a network. But see BGP-LS.

[snip]

> Finally, Adrian, I would like to ask what would be the process of
> defining extensions of the PCEP protocol to be used by non-PCE
> boxes (and thus, out of current PCE charter).

That's two "finally"s in one email, but we'll let you off because you used "syllogism" in an IETF email, and that surely gains you some points.

The process would be easy...

If there is a WG for the work
   do the work there
   ensure PCE WG review for risks of breaking PCE
Elsif there is IETF support for the work
   do the work as AD sponsored
   ensure PCE WG review for risks of breaking PCE
Else the work to the ISE
   ensure PCE WG review for risks of breaking PCE
Endif

In general, re-use of protocols is a fine thing. Issues are only:
- breakage of existing uses (especially deployments)
- confusion in the market
- twisting or crowding that makes extensions for the
   primary use difficult.

Approaches used in the past for this type of thing have included:
- no distinction at all
- distinct ranges of TLV/message identifiers
- separation of protocol instances
- use of a new protocol number or port numbers even when the
   core protocol is the same

A