The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2005-Dec> msg00040



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] I-D ACTION:draft-ietf-mpls-oam-requirements-07.txt

  • From: benjamin.niven-jenkins@bt.com
  • Date: Mon, 19 Dec 2005 15:45:40 -0000
  • Thread-Index: AcYBuccCGxsp5RaDQCKcJcZzN+3DOgC9jTHw
  • Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-oam-requirements-07.txt
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id jBJFuwr29753
  • X-OriginalArrivalTime: 19 Dec 2005 15:45:41.0802 (UTC)FILETIME=[444A60A0:01C604B3]

Authors,
Cc Colleagues,

I made several comments on the -06 version of this draft to the MPLS
mailing list on 22nd July 2005.  I believe some, but not all, of my
original comments have been addressed (at least in part).

So, I list below some follow-up comments:

(1) In the introduction the document refers to "requirements for user
and data plane operations and management", however the term "user plane"
is never used in the rest of the document.  So I would suggest removing
the term user plane from the introduction, unless the intention is to
emphasise that user plane == data plane in which case I think this
intention needs to be made more explicit.

(2) Section 4.1 refers to "customer traffic" and Section 4.4 refers to
"user traffic".  Is customer traffic synonymous with user traffic, in
which case I would suggest that the document standardises on one term.

3) Throughout the document, I am not sure that the use of customer is
consistent or its meaning clear - It would appear that sometimes what is
meant is an actual customer of a service provider and at other times
what is meant is the client layer of the MPLS (server) layer, in which
case I would comment that this client layer does not necessarily belong
to a "customer".  A definition of what is meant by customer in the
terminology section would help, but I would also suggest replacing
customer with a term such as client or client layer in those cases where
what you are discussing is not necessarily owned by a customer in a
business relationship sense (e.g. a SP may use a label stack to help
scaling/aggregation, but the same SP owns the client & server MPLS
layers, so who is the customer?).

4) Section 4.5, insofar-as => insofar as (According to The Columbia
Guide to Standard American English)


Thanks
Ben

--
Ben Niven-Jenkins
Networking Specialist, BT Exact
  
E-mail: benjamin.niven-jenkins@bt.com
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls