Re: [mpls] Stephen Farrell's Block on charter-ietf-mpls-05-01: (with BLOCK)
Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 15 August 2013 14:50 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 AD41521F8FCE; Thu, 15 Aug 2013 07:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level:
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MJxa6Z5byqBT; Thu, 15 Aug 2013 07:50:15 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5D12C21F85D4; Thu, 15 Aug 2013 07:50:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B7718BE53; Thu, 15 Aug 2013 15:50:04 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NA25qlJvyHIZ; Thu, 15 Aug 2013 15:50:04 +0100 (IST)
Received: from [134.226.63.225] (cswireless63-225.scss.tcd.ie [134.226.63.225]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8C9D8BE3F; Thu, 15 Aug 2013 15:50:04 +0100 (IST)
Message-ID: <520CEA9C.7040909@cs.tcd.ie>
Date: Thu, 15 Aug 2013 15:50:04 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: adrian@olddog.co.uk
References: <20130815133434.25448.80337.idtracker@ietfa.amsl.com> <006201ce99c5$faaea680$f00bf380$@olddog.co.uk>
In-Reply-To: <006201ce99c5$faaea680$f00bf380$@olddog.co.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, 'The IESG' <iesg@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
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:50:22 -0000
On 08/15/2013 03:44 PM, Adrian Farrel wrote: > 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. Great. > 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. I agree. > 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? Yes. However, I'm sure that I don't know what'd be a good set of even high-level requirements. But I am quite happy to try work with others on that if it helps. I'll s/block/comment/ and we can chat on the call if we're still in chatting mood when we get to that. Or later if we're all chatted out today. Thanks, S. > > Cheers, Adrian > > > >
- [mpls] Stephen Farrell's Block on charter-ietf-mp… Stephen Farrell
- Re: [mpls] Stephen Farrell's Block on charter-iet… Adrian Farrel
- Re: [mpls] Stephen Farrell's Block on charter-iet… Stephen Farrell