headers
Sumanth Channabasappa | 8 Nov 2006 04:24
Favicon

Changes incorporated in draft-ietf-ipcdn-pktc-eventmess-09

Folks,

Just as an update, 'draft-ietf-ipcdn-pktc-eventmess-09' was submitted
before the I-D submission deadline and this email summarizes the changes
from the previous revision. 

As a note, there were no technical changes made, but an attempt was made
to address the comments received from experts received on this list
(thanks).

regards
Sumanth  (on behalf of the co-authors)

-----------------------------------------------------------------------
#0 
My personal comment is that we need to clean up the "nits" caught on
<http://tools.ietf.org/wg/ipcdn/draft-ietf-ipcdn-pktc-eventmess/draft-ie
tf-ipcdn-pktc-eventmess-08.nits.txt> in draft 09, subsequent to
completion of the WGLC. These appear to be caused mostly by minor
document formatting issues, especially the "missing sections" that are
in fact present in the latest draft.
[Sumanth] Fixed (please check)? 
-----------------------------------------------------------------------

-----------------------------------------------------------------------
1) Are you using nroff? The spacing of section titles is weird. Also,
the online idnits tool still complains that page 4 is longer than it
should be. It also complains that there is no Security Considerations or
IANA Considerations sections, and I suspect this relates to the
formatting of section titles.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sumanth Channabasappa | 8 Nov 2006 04:24
Favicon

Changes incorporated in draft-ietf-ipcdn-pktc-signaling-12

Folks,

The co-authors of the I-D titled "Network-Based Call Signaling (NCS) MIB
for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)"
submitted draft-12 before the I-D Submission deadline and this email
summarizes the changes. 

As a note, it does contain technical changes in addition to the changes
based on feedback received (thanks to those who provided comments).

regards
Sumanth (on behalf of the co-authors)

Link:
http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-12.t
xt

----------------------------------------------------------------------
1. [Dan] The title of the document includes twice the word 'signaling' -
is this necessary? 
[Rich] I agree it seems to be redundant. I think occasionally folks
refer to "NCS signaling", which is also a redundant term.
[Sumanth] Agree; additionally removed redundant term 'NCS Signaling'
elsewhere in the document
----------------------------------------------------------------------

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

2. [Dan] idnits complains about un-used references:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Woundy, Richard | 22 Nov 2006 00:51
Picon

DOCSIS Cable Device MIB and downref normative references

Folks,

In the process of trying to publish the updated DOCSIS Cable Device MIB,
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mibv2-11.txt,
we have identified five "downref" normative references that must be
fixed prior to publication.

As RFC 3967 explains:

   IETF procedures generally require that a standards track RFC may not
   have a normative reference to another standards track document at a
   lower maturity level or to a non standards track specification (other
   than specifications from other standards bodies).  For example, a
   standards track document may not have a normative reference to an
   informational RFC.

Per guidance from our Area Director, there are two ways to fix these
downref normative references:

1. Move the references to the informative references section, with WG
consensus, or

2. Explain each downref normative reference in the draft (per RFC 3967),
and perform another IETF Last Call.

My recommendation (both as co-author and as co-chair) is to move the
five references to the informative references section, and complete
publication of this draft as an RFC.

*** If you disagree with this recommendation, please reply to me and the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wijnen, Bert (Bert | 22 Nov 2006 11:02
Picon
Favicon

RE: DOCSIS Cable Device MIB and downref normative referen ces

I support moving these 5 references from the normative to the informative
section. 

Bert

> -----Original Message-----
> From: Woundy, Richard [mailto:Richard_Woundy <at> cable.comcast.com]
> Sent: Wednesday, November 22, 2006 00:52
> To: ipcdn <at> ietf.org
> Cc: jfm <at> cablelabs.com; Woundy, Richard
> Subject: [ipcdn] DOCSIS Cable Device MIB and downref normative
> references
> 
> 
> Folks,
> 
> In the process of trying to publish the updated DOCSIS Cable 
> Device MIB,
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-device-mib
> v2-11.txt,
> we have identified five "downref" normative references that must be
> fixed prior to publication.
> 
> As RFC 3967 explains:
> 
>    IETF procedures generally require that a standards track 
> RFC may not
>    have a normative reference to another standards track document at a
>    lower maturity level or to a non standards track 
> specification (other
(Continue reading)

Permalink | Reply | 0 comments |

Gmane