Re: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
- To: "George Swallow (swallow)" <swallow at cisco.com>, "Loa Andersson" <loa at pi.se>
- To: "George Swallow (swallow)" <swallow at cisco.com>, "Loa Andersson" <loa at pi.se>
- Subject: Re: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
- From: "Rajiv Asati (rajiva)" <rajiva at cisco.com>
- From: "Rajiv Asati (rajiva)" <rajiva at cisco.com>
- Date: Thu, 12 Jun 2008 14:52:00 -0400
- Date: Thu, 12 Jun 2008 14:52:00 -0400
- Authentication-results: rtp-dkim-1; header.From=rajiva at cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
- Authentication-results: rtp-dkim-1; header.From=rajiva at cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
- Cc: mpls at ietf.org
- Cc: mpls at ietf.org
- Delivered-to: ietfarch-mpls-web-archive at core3.amsl.com
- Delivered-to: mpls at core3.amsl.com
- Delivered-to: ietfarch-mpls-archive at core3.amsl.com
- Delivered-to: mpls at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1392; t=1213296709; x=1214160709; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rajiva at cisco.com; z=From:=20=22Rajiv=20Asati=20(rajiva)=22=20<rajiva at cisco.com > |Subject:=20RE=3A=20[mpls]=20Last=20Call=20on=20draft-ietf- mpls-cosfield-def-02.txt |Sender:=20 |To:=20=22George=20Swallow=20(swallow)=22=20<swallow at cisco. com>,=0A=20=20=20=20=20=20=20=20=22Loa=20Andersson=22=20<loa @pi.se>; bh=ibNdX+RMFHutWUoF4UoYRQ6pNxAki8PTomWI51koeVg=; b=OMQKJbjeNuV+csbIIjpeSK+HVbY0r9aWIt8pIor0gH8Jn40FPZfh19g1BQ jussz1zItTHjKx+E2PxPnjOO/JdX55PyfukrKRH0OaAjLV7IZeyGr2tJ7HdP K8MtGoAuNB;
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=1392; t=1213296709; x=1214160709; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rajiva at cisco.com; z=From:=20=22Rajiv=20Asati=20(rajiva)=22=20<rajiva at cisco.com > |Subject:=20RE=3A=20[mpls]=20Last=20Call=20on=20draft-ietf- mpls-cosfield-def-02.txt |Sender:=20 |To:=20=22George=20Swallow=20(swallow)=22=20<swallow at cisco. com>,=0A=20=20=20=20=20=20=20=20=22Loa=20Andersson=22=20<loa @pi.se>; bh=ibNdX+RMFHutWUoF4UoYRQ6pNxAki8PTomWI51koeVg=; b=OMQKJbjeNuV+csbIIjpeSK+HVbY0r9aWIt8pIor0gH8Jn40FPZfh19g1BQ jussz1zItTHjKx+E2PxPnjOO/JdX55PyfukrKRH0OaAjLV7IZeyGr2tJ7HdP K8MtGoAuNB;
- In-reply-to: <C475C51A.22D77%swallow@cisco.com>
- In-reply-to: <C475C51A.22D77%swallow@cisco.com>
- List-archive: <https://www.ietf.org/mailman/private/mpls>
- List-archive: <https://www.ietf.org/mailman/private/mpls>
- List-help: <mailto:mpls-request@ietf.org?subject=help>
- List-help: <mailto:mpls-request@ietf.org?subject=help>
- List-id: Multi-Protocol Label Switching WG <mpls.ietf.org>
- List-id: Multi-Protocol Label Switching WG <mpls.ietf.org>
- List-post: <mailto:mpls@ietf.org>
- List-post: <mailto:mpls@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
- References: <C475C51A.22D77%swallow@cisco.com>
- References: <C475C51A.22D77%swallow@cisco.com>
- Sender: mpls-bounces at ietf.org
- Thread-index: AcjMD6vc6n0yvDgCEd2PMAARJIXBtgArAbYQ
- Thread-index: AcjMD6vc6n0yvDgCEd2PMAARJIXBtgArAbYQ
- Thread-topic: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
- Thread-topic: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
One minor comment for the 2nd para section 3 -
We may be using the term label loosely here to mean the 'label stack
entry' as defined in rfc3032 section 2. But in the interest of brevity,
we should use the latter.
~~~~~~~~~~~~~~~
3. Use of the CoS field
...
Current implementations look at the CoS field with and without label
context and the CoS field may be copied to the labels that are pushed
onto the label stack. This is to avoid the pushed labels having a
different CoS field.
...
~~~~~~~~~~~~~~~~~
The above may be misinterpreted as having one or more (20bit) label
values carrying the CoS values. We should be better off avoiding this
confusion.
Cheers,
Rajiv
> -----Original Message-----
> From: mpls-bounces at ietf.org [mailto:mpls-bounces at ietf.org] On
> Behalf Of George Swallow (swallow)
> Sent: Wednesday, June 11, 2008 6:08 PM
> To: mpls at ietf.org
> Subject: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
>
> This begins a two week last WG last call on the subject
> draft. The draft is
> available at
>
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-d
> ef-02.txt
>
> The last call closes June 25 0000 GMT.
>
> ...George
>
> _______________________________________________
> mpls mailing list
> mpls at ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls
7bit
Sender: mpls-bounces at ietf.org
Errors-To: mpls-bounces at ietf.org
One minor comment for the 2nd para section 3 -
We may be using the term label loosely here to mean the 'label stack
entry' as defined in rfc3032 section 2. But in the interest of brevity,
we should use the latter.
~~~~~~~~~~~~~~~
3. Use of the CoS field
...
Current implementations look at the CoS field with and without label
context and the CoS field may be copied to the labels that are pushed
onto the label stack. This is to avoid the pushed labels having a
different CoS field.
...
~~~~~~~~~~~~~~~~~
The above may be misinterpreted as having one or more (20bit) label
values carrying the CoS values. We should be better off avoiding this
confusion.
Cheers,
Rajiv
> -----Original Message-----
> From: mpls-bounces at ietf.org [mailto:mpls-bounces at ietf.org] On
> Behalf Of George Swallow (swallow)
> Sent: Wednesday, June 11, 2008 6:08 PM
> To: mpls at ietf.org
> Subject: [mpls] Last Call on draft-ietf-mpls-cosfield-def-02.txt
>
> This begins a two week last WG last call on the subject
> draft. The draft is
> available at
>
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-d
> ef-02.txt
>
> The last call closes June 25 0000 GMT.
>
> ...George
>
> _______________________________________________
> mpls mailing list
> mpls at ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
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.