[mpls] Responding to two incoming liaisons from SG15

Loa Andersson <loa@pi.nu> Sun, 10 February 2013 11:40 UTC

Return-Path: <loa@pi.nu>
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 274DE21F852C; Sun, 10 Feb 2013 03:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.881
X-Spam-Level:
X-Spam-Status: No, score=-100.881 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqUgICP4tz-Z; Sun, 10 Feb 2013 03:40:35 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id EE6AA21F8505; Sun, 10 Feb 2013 03:40:34 -0800 (PST)
Received: from [192.168.1.104] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id D6E62823B5; Sun, 10 Feb 2013 12:40:33 +0100 (CET)
Message-ID: <51178733.8080608@pi.nu>
Date: Sun, 10 Feb 2013 12:40:35 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, ccamp@ietf.org, "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [mpls] Responding to two incoming liaisons from SG15
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: Sun, 10 Feb 2013 11:40:36 -0000

Working Groups,

I intended to send the mail below to the wg chairs, the liaison
managers and the AD's, and then sending a little short and more
to the point mail to the wg's; but I slipped and sent to the
pwe3 working group instead of the chairs, so I won't bother sending
that shorter mail to the mpls and ccamp groups. You'll have to do
with what I sent to the chairs ;).

Pleae see the mail below.

/Loa



We have two new liaisons from SG15, one on p2mp and one on linear
protection. Scott has distributed these liaisons to PWE3 and CCAMP.

There has been a few mail threads discussing how to respond to the
liaisons (without even really getting down to the technical issues).

The dead line for both liaisons are June 1st.

As before we have Scott (in his role as MPLS liaison manager)
coordinating the activities needed to send responses. John should
be second in this work. I've also included Eric O on this mail
since he has a documented interest in at least the

What is need is something like this:

1. Make sure we have the right people involved for each liaison,
    e.g. the authors of the MPLS-TP P2MP Framework for the p2mp
    liaison, and the authors of RFC6378.

2. Go through the liaisons and decide what points we need to respond
    to. As much as possible break these points out and send one liaison
    per issue.
    Scott - needs to keep us updated about these points and we need to
    agree on them.

3. If we can say that the some of the points are questions for
    clarification or informative, we can send them right away without
    polling the wg's for consensus.

4. Identify what we need to have wg consensus for; and which wg's.

5. Set appropriate dead lines, but also make sure that we don't need
    to spend valuable cycles around IETF meetings.

6. As much as possible keep the responses to "Yes, we see your point,
    would be nice if you could put this into a draft!" or "This is not
    an issue, it is taken care of but the following wg document(s)!"
    "Please use the IETF process to progress these issues!"
    We don't want to set ourselves up to write other new drafts than
    those we are directly interested in, we have a limited number of
    cycles.

Workable? (Yes, you are supposed to respond!)

/Loa
-- 


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