[mpls] multiple-working group last call on draft-ietf-mpls-cosfield-def-04.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mpls] multiple-working group last call on draft-ietf-mpls-cosfield-def-04.txt
All,
this mail initiates a two week multiple-working group last call on
draft-ietf-mpls-cosfield-def-04.txt
Background:
The name "EXP field" of a three bit field in the MPLS shim header,
and the statement in RFC3032 "For experimental use" has led other
SDOs to believe that this field could be used for any type of
experiments. The field has however from the start been intended to
carry Class of Service (CoS) information.
The draft therefore renames the field "Class of Service (CoS) Field".
This is an update of RFC3032, and also of drafts that builds on
RFC3032. This multiple-working group last call is therefore sent to
working groups with RFCs that has been updated.
The document has been through wg last call in the mpls working group,
which I don't think will stop that wg producing new comments now,
nor should it :) .
This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.
Since this is also of interest in the work we started on a
Transport Profile for MPLS (MPLS-TP) we are also sending it to the
Ad HoC Team on MPLS in the ITU-T.
Please review and send comments to the mpls wg mailing list, or to
the mailing list for mpls-tp discussion that just been set up:
mpls-tp at ietf.org
or directly to the mpls wg co-chairs before e.o.b. July 24.
/Loa
--
Loa Andersson
Principal Networking Architect
Acreo AB phone: +46 8 632 77 14
Isafjordsgatan 22 From mpls-bounces at ietf.org Thu Jul 10 04:59:33 2008
Return-Path: <mpls-bounces at ietf.org>
X-Original-To: mpls-web-archive at megatron.ietf.org
Delivered-To: ietfarch-mpls-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 9EEBC3A6A1D;
Thu, 10 Jul 2008 04:59:33 -0700 (PDT)
X-Original-To: mpls at core3.amsl.com
Delivered-To: mpls at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 0FF2E3A6932;
Thu, 10 Jul 2008 04:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id Ky+loTHdXEpF; Thu, 10 Jul 2008 04:59:31 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
by core3.amsl.com (Postfix) with ESMTP id F08203A69E0;
Thu, 10 Jul 2008 04:59:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by neo.viciousnest.net (Postfix) with ESMTP id C39E81C2C5;
Thu, 10 Jul 2008 13:59:44 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 22062-01; Thu, 10 Jul 2008 13:59:43 +0200 (CEST)
Received: from [127.0.0.1] (pat.acreo.se [217.151.195.214])
by neo.viciousnest.net (Postfix) with ESMTP id 0FA7F1C2BC;
Thu, 10 Jul 2008 13:59:43 +0200 (CEST)
Message-ID: <4875F9A1.5070408 at pi.nu>
Date: Thu, 10 Jul 2008 13:59:29 +0200
From: Loa Andersson <loa at pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: tsvwg at ietf.org, ahtmpls at itu.int, ccamp <ccamp at ops.ietf.org>,
L2VPN <l2vpn at ietf.org>, pwe3 <pwe3 at ietf.org>, mpls at ietf.org
X-Virus-Scanned: by amavisd-new at viciousnest.net
Subject: [mpls] multiple-working group last call on
draft-ietf-mpls-cosfield-def-04.txt
X-BeenThere: mpls at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
<mailto:mpls-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls at ietf.org>
List-Help: <mailto:mpls-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
<mailto:mpls-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mpls-bounces at ietf.org
Errors-To: mpls-bounces at ietf.org
All,
this mail initiates a two week multiple-working group last call on
draft-ietf-mpls-cosfield-def-04.txt
Background:
The name "EXP field" of a three bit field in the MPLS shim header,
and the statement in RFC3032 "For experimental use" has led other
SDOs to believe that this field could be used for any type of
experiments. The field has however from the start been intended to
carry Class of Service (CoS) information.
The draft therefore renames the field "Class of Service (CoS) Field".
This is an update of RFC3032, and also of drafts that builds on
RFC3032. This multiple-working group last call is therefore sent to
working groups with RFCs that has been updated.
The document has been through wg last call in the mpls working group,
which I don't think will stop that wg producing new comments now,
nor should it :) .
This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.
Since this is also of interest in the work we started on a
Transport Profile for MPLS (MPLS-TP) we are also sending it to the
Ad HoC Team on MPLS in the ITU-T.
Please review and send comments to the mpls wg mailing list, or to
the mailing list for mpls-tp discussion that just been set up:
mpls-tp at ietf.org
or directly to the mpls wg co-chairs before e.o.b. July 24.
/Loa
--
Loa Andersson
Principal Networking Architect
Acreo AB phone: +46 8 632 77 14
Isafjordsgatan 22 mobile: +46 739 81 21 64
Kista, Sweden email: loa.andersson at acreo.se
loa at pi.nu
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls
mobile: +46 739 81 21 64
Kista, Sweden email: loa.andersson at acreo.se
loa at pi.nu
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.