[Sls-slp] FW: PICS annex for proximity-1 dll - definitions

[Kazz, Greg J (313B)]

Dear SLP WG,

As a follow on to my previous email, please consider these definitions for Mandatory, Optional, Conditional

Thanks!

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)
------------------------------------------------------

From: Thomas Gannett <tomg at aiaa.org<mailto:tomg at aiaa.org>>
Date: Wednesday, August 7, 2013 8:05 AM
To: "Kazz, Greg J (313B)" <greg.j.kazz at jpl.nasa.gov<mailto:greg.j.kazz at jpl.nasa.gov>>
Subject: Re: PICS annex for proximity-1 dll

Greg:

I'm also working on some generic definitions that you may want to share with the review team (so "M" and "O" mean the same thing to everyone):

optional. Not necessary for interoperability.

Optional capabilities can be excluded from an implementation (and made unavailable to users) without affecting the essential operation of the implementation.

Implementation options should not be confused with user options; i.e., there may be any number of features which a user can elect not to use but which need to be available in an implementation.

Also, whether a capability is optional may depend on whether the implementation is sending, receiving, or acting as a relay. A capability that a transmitter can do without might nevertheless be required at a receiver to accommodate transmitters that implement the capability.

mandatory. Required for interoperability.

Mandatory capabilities are all capabilities that need to be available for use for normal operation of an implementation, regardless of whether a user can elect not to use them.

conditional. Mandatory or optional depending on specified conditions.




At 09:51 AM 8/7/2013, Thomas Gannett wrote:
Greg:

The attached PICS annex reflects your changes. I don't really know who makes up the review team, so I think you should distribute it. If you know of individuals who were involved in the protocol testing it would be helpful to include them.

You might also communicate the following PICS general principles to the review team:

- A PICS proforma is supposed to be limited to static conformance requirements, so any items referencing dynamic protocol behavior should be omitted.

- A PICS proforma is supposed to list ALL optional capabilities but only MAJOR mandatory capabilities. Reviewers should determine whether lists of all-mandatory capabilities subordinate to a higher-level mandatory capability can be reduced to show simply the higher-level capability.

- Items that reference implementation-internal behavior that does not affect interoperability should not be included.

I'm still cross checking to make sure all the changes have been made to the specification itself.  I'll send it for WG signoff when I'm done.

Tom



At 08:19 PM 8/6/2013, Kazz, Greg J (313B) wrote:
Hi Tom,

I went through the proposed PICS for the Data Link Layer and made some
changes some of which we spoke about over the phone and some new ones.
Please use this content to send out to the review team. No doubt we will
quibble over some Os and Ms, but for the most part, I feel pretty secure
about them.

Also note:

1. Like we talked about, add a note about DLL = Data Link Layer in the
item mneumonic

2. I found an error in the Prox-1 spec. It is in the MIB annex (now annex
C ?). Remote_PCID is Mandatory (it says Optional in the spec, which needs
to be corrected.)

Thanks!

Greg
------------------------------------------------------
Greg Kazz
EEISE Group Supervisor
Systems Engineering Section (Section 313)
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena  CA 91109
MS 301-490
(818) 393-6529 (office)

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





On 7/31/13 12:31 PM, "Thomas Gannett" <tomg at aiaa.org<mailto:tomg at aiaa.org>> wrote:

>
>
>Thomas Gannett
>+1 443 472 0805

Thomas Gannett
+1 443 472 0805

Thomas Gannett
+1 443 472 0805
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20130807/194492bc/attachment.html>