[mpls] draft-mirskies straddling three working groups

Loa Andersson <loa@pi.nu> Wed, 02 August 2017 09:35 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A2A7F12EC13; Wed, 2 Aug 2017 02:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wxshu6p40q0M; Wed, 2 Aug 2017 02:35:19 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu []) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6032E127978; Wed, 2 Aug 2017 02:35:19 -0700 (PDT)
Received: from [] (c213-89-111-155.bredband.comhem.se []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 1FF13180156E; Wed, 2 Aug 2017 11:35:18 +0200 (CEST)
From: Loa Andersson <loa@pi.nu>
To: "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>
Cc: "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
Message-ID: <4432fd6b-fb9a-5ecf-faee-52d094cc01a2@pi.nu>
Date: Wed, 02 Aug 2017 11:35:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Al8h3wZGPWxUSlX-2QNAhCst4tg>
Subject: [mpls] draft-mirskies straddling three working groups
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Aug 2017 09:35:20 -0000


We have three drafts from Greg, they overlap in some fashion between
our working groups. I think it would be good if we could agree on how
the work is divided between the wg's, or maybe if if we should keep the
drafts at one place.

The drafts are:

BFD in Demand Mode over Point-to-Point MPLS LSP
BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP
Bidirectional Forwarding Detection (BFD) in Segment Routing Networks 
Using MPLS Dataplane

I could can think of doing this in different ways, obviously (if we
want to progress the draft).

We could do:

draft-mirsky-bfd-mpls-demand-01 in bfd
draft-mirsky-mpls-p2mp-bfd-01 in mpls; and
draft-mirsky-spring-bfd-01 in spring

That would obviously require quite a bit of coordination.

We could also do all of the in one working group, and if we do that
I think MPLS is the the stuckee. If someone else want to pick up the
draft I would not have strong objections, as long as we make sure
we have enough coordination.

In the MPLS wg we appoint a document shepherd prior to MPLS-RT review
(part of the adoption process). The shepherd then run the entire process
of adopting the document (with support from the mpls chairs; and we
don't start the process until the shepherd is reasonably sure that the
adoption will take place.

If (big if) we decide to take all documents to MPLS, then I'd like to
have a shepherd from the other working groups for "their" documents.

Opinions, ideas?



Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64