Re: [802SEC] Clause 19 Report regarding P802.21/D13 to RevCom
Hello David,
This comment is restatement of previous comment by Tony in Recirc-4, Comment #1 which is as follows:
Comment: " In your (revised) response to my comment #143 on recirc 2 you state: "The PICS Proforma has been developed w.r.t the following references: [1] ITU-T Recommendation X.290 (1995), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - General concepts. and [2] ITU-T Recommendation X.296 (1995), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - Implementation conformance statements." Both recommendations refer to (protocol specification) conformance clauses, which is a concept that is discussed, defined, and mandated in Recommendation X.291 (1995) for "Each base specification, which specifies an OSI protocol, abstract syntax, encoding rules, or information object..." (Clause 6 of Rec X.291). If you are claiming that the PICS proforma has been developed with respect to those two references then: (a) the list of references is incomplete, because X.291 is also part of !
the story, as you are developing an OSI protocol; and (b) your specification is incomplete, as it does not include a protocol specification conformance clause."
Proposed Resolution: " Add a reference to X.291 in Clause 2 of the draft, and follow its guidance (in Clause 6 and elsewhere) by developing a protocol specification conformance clause."
Resolution Status: Disagree
Resolution Detail: "Neither IEEE nor IEEE 802 require a PICS Proforma. Neither IEEE or IEEE 802 provide any guidance for its creation. Therefore the only authoritative reference for the creation of a PICS Proforma is ITU-T X.296 (ISO/IEC 9646:7). Following its guidance only X.290 and X.296 are required as per 8.2.4."
Kind Regards
-Vivek
-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of David Law
Sent: Sunday, August 17, 2008 10:01 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] Clause 19 Report regarding P802.21/D13 to RevCom
Hi Vivek,
In review of the Tony Jeffree 1/2 [
https://mentor.ieee.org/802.21/file/08/21-08-0249-00-0000-p802-21-to-revcom.ppt#8
] I note that Tony is a Disapprove voter and has marked this comment as
Must Be Satisfied. I further note that the response doesn't state that the
comment is out of scope due to being related to unchanged text - nor does
it state that the comment is a restatement of a previous comment - instead
the response simply provides a rebuttal. Based on this you appear to me to
be treating this comment as a new valid Disapprove comments - is this
correct ?
I did try to find the comments and response from the previous
recirculations on the IEEE 802.21 web site but was unable to find them so
I'm unable to see what comment #1 on recirculation #4 stated.
Best regards,
David
***** IEEE 802 Executive Committee List *****
<STDS-802-SEC@LISTSERV.IEEE.ORG> wrote on 15/08/2008 19:45:43:
> Dear EC Colleagues:
>
> I am reporting on the status of P802.21/D13.0, as per the Clause 19
> Conditional Approval granted on 18 July, 2008.
>
> The Sponsor Ballot Recirculation-6, including the review of
> P802.21/D13.0 ran from 30 July, 2008 - 14 August, 2008.
> The final vote tally is: 126/5/11
> The Approval Ratio is 96.18% and the Return Ratio is 86%.
>
> The conditions have been met.
> ? No New Disapprove votes were received during this recirculation
> ? Total of 12 comments were submitted. 7 of these are from
> Disapprove voters.
> ? No Technical changes are required as a result of these comments
> ? No new valid Disapprove comments on new issues
>
> The complete report is available at:
>
http://mentor.ieee.org/802.21/file/08/21-08-0249-00-0000-p802-21-to-revcom.ppt
>
> Accordingly, I shall be forwarding P802.21 to RevCom.
>
> Best Regards,
> Vivek
>
> Vivek Gupta
> Chair, IEEE 802.21
> ----------
> This email is sent from the 802 Executive Committee email reflector.
> This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.