RE: [STDS-802-21] Inconsistency in 802.21(c) parameters -- please take a look

["Cypher, David E." <david.cypher@xxxxxxxx>]

Charles,

I do not have 802.21c in front of me, but …

The original formatting for 802.21 was that the parameters list of a primitive contains all of the parameters that could be included, as well as in the tables following the parameter list explains when and or if the parameter is included.

When it came to the actual message format it had to include also all of the fields that could be part of the message and within that field (mark as optional)

There should be no inconsistency between the primitive parameters list and the message fields (as you appear to be pointing out).  That is there shall be a one for one match between the primitive list, primitive table, and message format.

I am not commenting on whether source address is required or not in order to remover the inconsistency.

David Cypher

From: Charles E. Perkins [mailto:charles.perkins@xxxxxxxxxxxxx]
Sent: Tuesday, August 07, 2012 3:30 PM
To: STDS-802-21@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-21] Inconsistency in 802.21(c) parameters -- please take a look

 

Hello folks,

I am noticing various inconsistencies, which mostly I
can fix.  But here is an example where I am not so sure.

For instance in section 7.4.29.1.2:

1.1.1.1.1   Semantics of service primitive

MIH_LL_Transfer.request

includes:

          DestinationIdentifier,

          TargetLinkIdentifier,

          LLInformation,

          TMGWIdentifier,

          CandidateLinkList

But section 8.6.3.24 calls also for
a "Source Identifier".  I think this can be argued
both ways, but the Source Identifier is unlikely
to be absolutely required and so I could omit it.

Comments, please?