Re: [mpls] MPLS wg charter update

Loa Andersson <loa@pi.nu> Sun, 12 May 2013 07:00 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 3565521F87D2 for <mpls@ietfa.amsl.com>; Sun, 12 May 2013 00:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level:
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, 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 WL2Fvt71E3Eb for <mpls@ietfa.amsl.com>; Sun, 12 May 2013 00:00:25 -0700 (PDT)
Received: from pipi.pi.nu (unknown [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6DCB021F89B2 for <mpls@ietf.org>; Sun, 12 May 2013 00:00:24 -0700 (PDT)
Received: from [192.168.1.130] (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) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id CFF5B1802D26; Sun, 12 May 2013 09:00:19 +0200 (CEST)
Message-ID: <518F3E03.7080003@pi.nu>
Date: Sun, 12 May 2013 09:00:19 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
References: <518E0484.7030904@pi.nu> <3598378B-38F0-4AB4-ABEA-5BEFBB714DD8@cisco.com>
In-Reply-To: <3598378B-38F0-4AB4-ABEA-5BEFBB714DD8@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "<mpls-ads@tools.ietf.org>" <mpls-ads@tools.ietf.org>
Subject: Re: [mpls] MPLS wg charter update
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, 12 May 2013 07:00:30 -0000

Carlos,

thanks for comments! My personal response too them would be:

1. Work items vs. focus areas.
    Not being a native English speaker I would need a better definition
    of the terms, tentatively I'd say that either would work for me,
    maybe say "work items and focus areas" if that aligns with how
    the  terms are defined.

2. IPv6 gap analysis
    I believe that the IPv6 gap analysis is part of "necessary
    extensions ... for dual stack and IPv6 only"
    The gap analysis will show up as a milestone when we accept
    an ID on that topic as a wg group document.

/Loa

On 2013-05-12 01:24, Carlos Pignataro (cpignata) wrote:
> Hi Loa,
>
> Please find two very small questions/comments inline.
>
> Thumb typed by Carlos Pignataro.
> Excuze typofraphicak errows
>
> On May 11, 2013, at 4:43 AM, "Loa Andersson" <loa@pi.nu> wrote:
>
>> Working Group,
>>
>> The working group chairs have discussed an MPLS wg charter update
>> for sometime.
>>
>> We have converged on the text below and while we understand that
>> it still not "perfect" (for some value of perfect) we believe that
>> it is good enough to serve as a basis for a working group discussion
>> of our charter.
>>
>> Please note that this is not a "re-charter", but a normal charter update
>> (maintenance) that should take place when adopting new work items or
>> finalizing others. The only "issue" is that we have not maintained the
>> charter to the degree we should have during the last years when the
>> work load has been quite heavy.
>>
>> Please view the text below as a starting point for an update of our
>> charter and send your comments to mpls@ietf.org. We would like to see
>> your comments before June 7th, 2013.
>>
>> -------------------- Proposed new charter text -------------------------
>>
>>
>> Description of Working Group
>>
>> The MPLS working group is responsible for standardizing technology
>> for label switching and for the implementation of label-switched
>> paths over packet based link-level technologies.
>>
>> The responsibility includes procedures and protocols for the
>> distribution of labels between Label Switching Routers (LSRs),
>> MPLS packet encapsulation, and for Operation, Administration, and
>> Maintenance (OAM) (including the necessary management objects
>> expressed as MIB modules or using other techniques).
>>
>> The current WG work items are:
>>
>
> The text above looks good. A nit: are these "work items" or "focus areas"?
>
>> •    Maintain existing MPLS requirements, mechanisms, and protocols,
>>         in coordination with other working groups, e.g. CCAMP, PWE3
>>         and OPSAWG working groups.
>> •    Evolve key MPLS protocols, including LDP, tLDP, mLDP, RSVP-TE
>>         and LSP Ping to meet new requirements.
>> •    Define an overall OAM framework for topology-driven, traffic
>>         engineered, and transport profile MPLS applications.
>> •    Determine MPLS-specific aspects of traffic engineering for
>>         multi-areas/multi-AS in cooperation with the CCAMP WG
>> •    Define necessary extensions for MPLS key protocols for
>>         dual-stack and IPv6 only networks
>
> In addition to defining extensions, could we add also a "gap analysis" of the IPv6 (dual stack and IPv6 only) state for MPLS key protocols and procedures?
>
> Thanks,
>
> Carlos.
>
>> •    Coordinate with the CCAMP working group on the extensions of
>>         MPLS and GMPLS protocols
>> •    Document current implementation practices for MPLS load sharing.
>> •    Document mechanisms for securing MPLS networks in coordination
>>         with the KARP working group.
>> •    Document mechanisms for adding multi-topology support to
>>         existing MPLS protocols.
>> •    Document use cases for MPLS protocols.
>>
>> -------------------------- end proposed text ------------------------
>>
>> Loa
>> (for the wg chairs)
>>
>> --
>>
>>
>> Loa Andersson                        email: loa@mail01.huawei.com
>> Senior MPLS Expert                          loa@pi.nu
>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>

-- 


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