[Forces-protocol] Feedback: Section 6.2

- Section 6.2.1

 	     +--- T = Operation = SHOW
   		      |
   		      +-- FE NAME

What is the point of having this one operation called SHOW just
for this? Is it an operation at all given its position in the hierachy?
PENAME may have been a better name.

In the diagram: 
+ LFB Instance ID  and LFB Class ID 
should those just be set to 0x1? We already know thats where they are
going.
+ Type = operation, using the word "type" is confusing since it is also
used in the main header. I dont think we can avoid using the word type
in TLVs; my suggestion is we consider changing the main header type to 
"command". Thoughts? It is a command after all.
+ comment on SHOW applies here as well

+ "HBI will be exchanged with the CE using this LFB" ???

-6.2.2  Association Setup Response Message

In the diagram: 
+ LFB Instance ID  and LFB Class ID 
should those just be set to 0x1? We already know thats where they are
going.
+         
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Type = operation Show  |               Length          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~                   FE Object LFB (optional)                    ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

What is that?

+ "HBI will be exchanged with the CE using this LFB" ???

+ Type = T.reason  ?

This brings up that we need the following speacial TLVs.

FORCES_REASON, FORCES_RESULT, FORCES_NAME.

cheers,
jamal

_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol