Forwarding and Control Element Separation (forces)

Weiming Wang | 3 Jun 2005 16:50

Re: [issue37] TBD - FE Protocol Attributes

It seems we need to first decide "who should define the LFBs like FE-LFB, FE-protocol-LFB, this protocol
document or elsewhere"  before trying to decide this issue.

thanks,
Weiming
----- Original Message ----- 
From: "Avri Doria" <tracker-forces <at> mip4.org>
To: <FORCES <at> PEACH.EASE.LSOFT.COM>
Sent: Monday, May 23, 2005 2:50 AM
Subject: [issue37] TBD - FE Protocol Attributes


New submission from Avri Doria <avri <at> acm.org>:

6.2.1

   o  FE Protocol attributes (can be read and set):
      *  Current version of the ForCES protocol




Doria (co-editor)         Expires April 4, 2005                [Page 31]

Internet-Draft                   ForCES                     October 2004


      *  Current version of the FE model
      *  FE unicast ID
      *  FE multicast ID(s) (list)

(Continue reading)

headers

Joel M. Halpern | 3 Jun 2005 20:28

Re: [issue37] TBD - FE Protocol Attributes

A reasonable question.

My current take is that the FE LFB should come with the model document, and 
the FE-protocol LFB should be defined by the protocol document.
However, this is something on which reasonable people can easily differ, 
and I am open to alternatives.

Yours,
Joel

At 10:50 AM 6/3/2005, Weiming Wang wrote:
>It seems we need to first decide "who should define the LFBs like FE-LFB, 
>FE-protocol-LFB, this protocol document or elsewhere"  before trying to 
>decide this issue.
>
>thanks,
>Weiming