Re: [mpls] Stephen Farrell's Block on charter-ietf-mpls-05-01: (with BLOCK)

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 15 August 2013 14:46 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B5821E8155; Thu, 15 Aug 2013 07:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level:
X-Spam-Status: No, score=-2.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599]
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 clCqvIuLUtvq; Thu, 15 Aug 2013 07:45:58 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3497821F944C; Thu, 15 Aug 2013 07:44:52 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7FEikcn032378; Thu, 15 Aug 2013 15:44:46 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7FEijDE032358 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 15 Aug 2013 15:44:45 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, 'The IESG' <iesg@ietf.org>
References: <20130815133434.25448.80337.idtracker@ietfa.amsl.com>
In-Reply-To: <20130815133434.25448.80337.idtracker@ietfa.amsl.com>
Date: Thu, 15 Aug 2013 15:44:42 +0100
Message-ID: <006201ce99c5$faaea680$f00bf380$@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: AQJqU1qHjF53ZSlOpLV3ZgTTXVM7Zphe4zrQ
Content-Language: en-gb
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org
Subject: Re: [mpls] Stephen Farrell's Block on charter-ietf-mpls-05-01: (with BLOCK)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 14:46:04 -0000

Hi Stephen,

> Just one little innocent question:-)
> 
> This says:
> 
> -   Evolve key MPLS protocols, including LDP, tLDP, mLDP, RSVP-TE
>     and LSP Ping to meet new requirements.
> 
> and
> 
> -   Document mechanisms for securing MPLS networks in coordination
>     with the KARP working group.
> 
> Karp is precluded from considering confidentiality and its charter
> doesn't mention privacy. 

Right. That makes the second bullet in your quote true and accurate.

> Assuming that MPLS might be used e.g. near the endpoints of
> transatlantic fibres, (is it?) do you think the WG might be open
> to considering work on confidentiality/privacy, perpaps even on
> opportunistic encryption or the like? I guess one could argue
> that there are requirements there that have only recently
> become clear.
> 
> If this will go for external review I'm fine with asking the question
> on ietf@ietf.org and will unblock.

I am asking that this does not go for external review so...

> If not, I'd appreciate a quick chat about this before I unblock.

The issue of confidentiality and privacy is definitely worth talking about, both for the control plane and for the data plane. 

I don't think we can drop a charter task in out of the blue since there is no evidence the WG wants to work on this. However, if the scenarios and high-level requirements were written up in an I-D it would:
- fit within the first bullet you quoted and so be within scope for 
  WG discussions
- possibly lead to a future recharter with a specific action

OK?

Cheers,
Adrian