IPoRPR draft updates
"Glenn Parsons" <[email protected]> Mon, 21 Aug 2006 10:37:29 -0400
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D0B93A13D@zcarhxm0.corp.nortel.com> |
This is a multi-part message in MIME format.
--===============1065490917==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C6C52F.56A92E12"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6C52F.56A92E12
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Folks,
Based on discussion with some Transport Area experts at IETF 66, I am
proposing some minor updates to the IPoRPR draft.
1. The behaviiour or DSCP 010010 was inconsistent with the others and
should be aligned. The update to the first part of Table 2 is as
follows:=20
|----------|-------------------|-------------|-------------|
| DSCP | RPR | RPR | Traffic |
| | service_class | mark_fe | Allocation |
=
|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D|
| 000000 | classC | ignore | EIR |
| 001000 | | | |
|----------|-------------------|-------------|-------------|
| 001010 | | FALSE | classB-CIR |
| | |-------------|-------------|
| 001100 | | TRUE | classB-EIR |
| 001110 | | | |
|----------| |-------------|-------------|
| 010000 | | FALSE | classB-CIR |
|----------| classB |-------------|-------------|
| 010010 | | FALSE | classB-CIR |
| | |-------------|-------------|
| 010100 | | TRUE | classB-EIR |
| 010110 | | | |
|----------| |-------------|-------------|
| 011010 | | FALSE | classB-CIR |
| | |-------------|-------------|
| 011100 | | TRUE | classB-EIR |
| 011110 | | | |
|----------|-------------------|-------------|-------------|
=20
2. To align with this modified table, change the paragraph following
Table 2 (on the bottom of page 14) as follows:
Services marked with a DF and CS1 DSCP only an EIR component.=20
Service marked with AF11, AF21, AF31 and CS2 DSCPs have an
aggregated CIR and services marked with AF12, AF13, AF22, AF23, AF32 and
AF33 have an aggregated EIR component.
Traffic marked with CS6 DSCP class (routing control) also has
only a CIR component. Further, it is recommended that CS6 marked traffic
be assigned its own RPR service. These guidleines are provided so that
congestion from other traffic sources does not cause routing instability
since it is separated from the routing control traffic.
As CS7 is for future use, no mapping is provided.=20
An updated draft will be issued shorlty, followed by a joint IPoRPR/MPLS
WG last call.
Cheers,
Glenn.
------_=_NextPart_001_01C6C52F.56A92E12
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.14">
<TITLE>IPoRPR draft updates</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=3D2 FACE=3D"Arial">Folks,</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Based on discussion with some Transport =
Area experts at IETF 66, I am proposing some minor updates to the IPoRPR =
draft.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">1. The behaviiour or DSCP 010010 was =
inconsistent with the others and should be aligned. The update to =
the first part of Table 2 is as follows:</FONT> </P>
<P><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------|-------------------|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | DSCP =
| =
RPR | =
RPR | Traffic |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
| | =
service_class | mark_fe | =
Allocation |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 000000 =
| =
classC | =
ignore | =
EIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 001000 =
| =
=
| =
=
| =
|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------|-------------------|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 001010 =
| =
| =
FALSE | classB-CIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
| =
| =
=
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 001100 =
| =
| =
TRUE | classB-EIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 001110 =
| =
=
| =
=
| =
|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------| &=
nbsp; =
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 010000 =
| =
| =
FALSE | classB-CIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------| =
classB =
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 010010 =
| =
| =
FALSE | classB-CIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
| =
| =
=
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 010100 =
| =
| =
TRUE | classB-EIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 010110 =
| =
=
| =
=
| =
|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------| &=
nbsp; =
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 011010 =
| =
| =
FALSE | classB-CIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
| =
| =
=
|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 011100 =
| =
| =
TRUE | classB-EIR |</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> | 011110 =
| =
=
| =
=
| =
|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New"> =
|----------|-------------------|-------------|-------------|</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"> </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">2. To align with this modified table, =
change the paragraph following Table 2 (on the bottom of page 14) as =
follows:</FONT>
</P>
<UL>
<P><SPAN LANG=3D"en"><FONT FACE=3D"Courier New">Services marked with a =
DF and CS1 DSCP only an EIR component. </FONT></SPAN>
<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Courier New">Service marked with =
AF11, AF21, AF31 and CS2 DSCPs have an aggregated CIR and services =
marked with AF12, AF13, AF22, AF23, AF32 and AF33 have an aggregated EIR =
component.</FONT></SPAN></P>
<P><SPAN LANG=3D"en"><FONT FACE=3D"Courier New">Traffic marked with CS6 =
DSCP class (routing control) also has only a CIR component. Further, it =
is recommended that CS6 marked traffic be assigned its own RPR =
service. These guidleines are provided so that congestion from =
other traffic sources does not cause routing instability since it is =
separated from the routing control traffic.</FONT></SPAN></P>
<P><SPAN LANG=3D"en"><FONT FACE=3D"Courier New">As CS7 is for future =
use, no mapping is provided.</FONT> </SPAN>
</P>
<BR>
</UL>
<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">An updated draft =
will be issued shorlty, followed by a joint IPoRPR/MPLS WG last =
call.</FONT></SPAN>
</P>
<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Cheers,</FONT></SPAN>
<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Glenn.</FONT></SPAN>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6C52F.56A92E12--
--===============1065490917==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
IPORPR mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/iporpr
--===============1065490917==--