From: John Grinham <jrg@hplb.hpl.hp.com>
Subject: Priority/resource management.
To: p8021@hepnrc.hep.net
Date: Fri, 14 Jun 96 13:47:39 BST


Given the recent .1p comments on resource allocation and priority
management, .1'ers may be interested in the following Internet Draft
submitted by Peter Kim (HP Labs) as a contribution to the IETF's Integrated
Services over Specific Link Layers working group. Comments welcome.

We are planning to present this at the IETF Montreal ISSLL meetings June
24/25th.

Regards, 

John.

P.S Its definitely on the US East Coast Site and Europe sites
    (addresses below)  - hasn't propagated to all the others yet.

-----------------------------------------------------------------------------
John Grinham.    Network Technology Dept          Hewlett-Packard Labs.
Filton Road, Stoke Gifford, Bristol BS12 6QZ, UK.
Tel: +44 117 9228138    Fax: +44 117 9228924 or 9228920        
jrg@hplb.hpl.hp.com                     
-----------------------------------------------------------------------------


I have submitted a new Internet-Draft titled "Link Level Resource
Management Protocol (LLRMP)". The draft is available from the on-line
Internet-Drafts directories in postscript or ACSII format.

       Title     : Link Level Resource Management Protocol (LLRMP).
       Author    : P. Kim
       Filename  : draft-kim-llrmp-00.txt
                   draft-kim-llrmp-00.ps

Abstract of the draft:

   This memo describes the LLRMP, a lightweight link level signalling
   protocol used to setup resources in shared medium and bridged or
   switched LANs. Network layer resource management protocols like RSVP
   or STII, or a local network manager, may invoke the LLRMP to request
   a certain quality of service over a bridged LAN.

   The LLRMP protocol supports a distributed admission control over each
   shared medium segment within the bridged LAN. Each node running the
   protocol has knowledge about the resources reserved on its local
   network segment. Resources are reserved independently on each
   segment, as a LLRMP reservation message travels along the data path
   from the source to the receiver.

I would be grateful about any comments or suggestions.

Regards

Peter

------------------------------------------------------------------------

   o Africa
     ftp.is.co.za (196.4.160.8)
   o Europe
     nic.nordu.net (192.36.148.17)
   o Pacific Rim
     munnari.oz.au (128.250.1.21)
     The Internet-Drafts on this machine are stored in UNIX compressed
     form (i.e., the .Z file extension).
   o US East Coast
     ds.internic.net (198.49.45.10)
   o US West Coast
     ftp.isi.edu (128.9.0.32)

in /internet-drafts