The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Nov> msg00049



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

API

  • From: Curtis Villamizar <curtis@workhorse.fictitious.org>
  • Date: Tue, 07 Nov 2000 09:23:59 -0500
  • cc: curtis@avici.com, Gaitonde Anandprasanna <prasanna@csa.iisc.ernet.in>, David Charlap <david.charlap@marconi.com>, mpls@UU.NET


In message <Pine.GSO.4.21.0011061702090.13841-100000@regan.ee.surrey.ac.uk>, Ll
oyd Wood writes:
> On Mon, 6 Nov 2000, Curtis Villamizar wrote:
> > 
> > The IETF never specifies APIs or user level command interfaces.  This
> > applies to all IETF standards work not just MPLS.
> 
> RFC 2025. RFC 2744. RFC 2853...

Lloyd,

Security services has been an exception and an unwelcome exception to
some and there is one service location API.  As a rule the IETF wants
to stay out of APIs.  This has been discussed on the IETF list and at
the open pleniaries.

The transport and routing areas have explicitly stayed away from APIs.
For example, there is no IETF API for per microflow RSVP even though
this provides user services.  The sockets layer is also not
standardized for unicast or multicast.

Curtis

  • References:
    • API
      • From: Lloyd Wood <l.wood@eim.surrey.ac.uk>