Re: Hard questions (was: Diffserv PIB approved as Informational RFC)

Nguyen Thi Mai Trang <[email protected]> Tue, 25 Jun 2002 20:21:15 +0200
Newsgroups gmane.ietf.diffserv
Organization ENST - INFRES
Message-ID <[email protected]>
Hi everybody,

I read this mail session and find that the problem you rasied can be solved by my actual work:

http://www.ietf.org/internet-drafts/draft-nguyen-rap-cops-sls-02.txt
and more illustrations in "COPS-SLS: A service level negotiation for the Internet",
Communication Magazine, May 2002

I agree with Brian that service definition and DSCP mapping between domains may be work for a
trade association, not for the IETF. Each provider can build their services and choose a DSCP
mapping as they want. However, a protocol to make this mapping automatic, check the
interoperablility and negotiate for a end-to-end (or in general from one point to another point
in the network) service level is necessary and interesting for IETF, imho. Each DS domain can
be built and managed independently with their own policies and service definitions. COPS-SLS
can be used to hind the detail implementation and give an interoperability between
domains/sub-domains not only for Diffserv but also potentially other QoS technologies.

Maybe this is not the place to discuss the detail of this protocol but I hope that this work
can give a contribution for the deployment of Diffserv in large scale later. If you are
interested in this work, please mail to my personal email or discuss in an appropriate mailing
list (I don't know which list because this is an individual draft).
Regards,

Mai Trang

Dan Grossman wrote:

> We _already_ have service definitions ( RFC 2211 and RFC 2212).  A small number of
> additional ones  would be useful, but I agree that a signalling WG is not the place to be
> defining them.
>
> My point was that the Diffserv work is complete enough to confuse the innocent,  but not
> complete enough to be useful.     We have not defined any end-to-end (or even edge-to-edge)
> services... er.... behaviors, much less the complete set of mechanisms to offer them or
> even a sound architectural framework.  I don't think that NSIS can or should be expected to
> resolve all that.
>
> There may be some cause for hope that the NSIS work will ultimately provide much of the
> needed mechanism to allow capacity reservation.  It may even fill in some of the nagging
> holes in the Diffserv architecture (for example, the ability to nail a path,  mechanisms to
> manage DSCP mappings between DS domains, and ability to discover what services... er...
> PDBs...  might be available between two or more hosts).
>
> Dan
>
> Marcus Brunner wrote:
>
> > [...]
> > >> > You correctly note that there are difficult problems that remain in
> > >> > diffserv, but it's not clear that they can be solved in an IETF WG.
> > >> > So, I would say that we are taking a breather before finishing the
> > >> > job and further that the breather is required so we can get some
> > >> > experience.
> > >>
> > >> I think that addresses my question.  The question back to you is "until
> > >> when"?
> > >>
> > >
> > > I think you need to address that question to our AD. I'm not
> > > sure what event would be considered the appropriate one
> > > to start a new WG, though I heard in NSIS that they wanted
> > > to take another stab at defining "quality of service classes"
> > > so maybe the charter is going to be changed.
> >
> > Being active in NSIS, we basically ruled service definitions and
> > specifications out of scope. I think the service definition is partly too
> > difficult and on the other hand a service providers differentiater to offer
> > the service markets want.
> >
> > I feel it is not the task of the IETF to define it, even so I think a small
> > number of basic PDB would help first deployments.
> >
> > Marcus
> >
> > >
> > >       Kathie
> > >
> > > _______________________________________________
> > > diffserv mailing list
> > > [email protected]
> > > https://www1.ietf.org/mailman/listinfo/diffserv
> > > Archive:
> > > http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist
> > > .html
> > >
> >
> > --------------------------------------
> > Dr. Marcus Brunner
> > Network Laboratories
> > NEC Europe Ltd.
> >
> > E-Mail: [email protected]
> > WWW:    http://www.ccrle.nec.de/
> > personal home page: http://www.brubers.org/marcus
> >
> > _______________________________________________
> > diffserv mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/diffserv
> > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html
>
> _______________________________________________
> diffserv mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/diffserv
> Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html

--
----------------------------------------------------
Nguyen Thi Mai Trang
Ecole Nationale Superieure des Telecommunications
Dept. INFRES - Bur. C234-4
46 Rue Barrault - 75013 Paris
Tel: 01 45 81 74 61 - Fax : 01 45 81 31 19
email : [email protected]



_______________________________________________
diffserv mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html