Re: [Forces-protocol] RE: GET/SET in one msg ?

[Steven Blake <[e-mail]>]

On Mon, 2004-10-18 at 08:32, Jamal Hadi Salim wrote:

> 6.2 Query Messages
> -------------------
> 
> 6.2.1 Query message 
> -------------------
>
> main hdr (eg type = Query)
>      |
>      |
>      +--- T = LFBselect
>      |        |
>      |        +-- LFBCLASSID = target LFB class 
>      |        |
>      |        |
>      |        +-- LFBInstance = target LFB instance
>      |        |
>      |        |
>      |        +-- T = GET
>      |        |   |
>      |        |   +--  // one or more path targets 
>      |        |        // under discussion
>      |        |
>
> The LFB is targeted. So if you need to find a route
> from an LPM you target that LFB. If you need to find 
> neighbors of an FE you target the FE object LFB.
>
> The response is exactly the same as above with type = Query-response.
>
> 6.3 Configuration Message
> --------------------------
> 
> 6.3.1 Config request
> ----------------------
> 
> main hdr (eg type = config)
>      |
>      |
>      +--- T = LFBselect
>      |        |
>      |        +-- LFBCLASSID = target LFB class
>      |        |
>      |        |
>      |        +-- LFBInstance = target LFB instance 
>      |        |
>      |        |
>      |        +-- T = operation { ADD, DEL, GET, etc}
>      |        |   |
>      |        |   +--  // one or more path targets 
>      |        |        // under discussion
>      |        |
>      |        +-- T = operation { ADD, DEL, GET, etc}
>      |        |   |
>      |        |   +--  // one or more path targets 
>      |        |        // under discussion
>      |        |
>      |        +-- T = operation { ADD, DEL, GET, etc}
>      |        |   |
>      |        |   +--  // one or more path targets 
>      |        |        // under discussion
>      |        |
>
> In other words: Very similar to the way we have it already except
> the naming has changed and we can target multiple
> operations and multiple paths in an LFB instance

If people agree that the protocol should preclude GET operations in
CONFIG_REQUEST messages, and only allow them in QUERY_REQUEST messages,
then the latter BNF needs to be edited to remove GET from the operation
list.  I was assuming that the GET would be encoded as an operation TLV
in the QUERY_REQUEST message.


Regards,

// Steve


_______________________________________________
Forces-protocol mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/forces-protocol