Hi,
What’s the difference in VAD implementation for G.711 described in G.711 Appendix-II and G.711 VAD requirements mentioned in “IMTC voice-over-ip Service Interoperability Implementation Agreement 1.0”
Thanks
_______________________________________________ IPCDN mailing list IPCDN <at> ietf.org https://www.ietf.org/mailman/listinfo/ipcdn
-----Original Message----- From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] Sent: Monday, May 10, 2010 4:53 PM To: ah <at> TR-Sys.de; gordon.beacham <at> motorola.com; satish.kumar <at> ti.com; Sumanth <at> cablelabs.com Cc: Romascanu, Dan (Dan); iesg <at> iesg.org; rfc-editor <at> rfc-editor.org Subject: [Errata Held for Document Update] RFC5098 (1347) The following errata report has been held for document update for RFC5098, "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5098&eid=1347 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alfred Hoenes <ah <at> TR-Sys.de> Date Reported: 2008-03-04 Held by: Dan Romascanu (IESG) Section: 5, pg.12 Original Text ------------- pktcSigDevCodecTable OBJECT-TYPE ... DESCRIPTION " ... Codec Type Maximum Number of Simultaneous Codecs PCMA 3 PCMA 2 PCMU 1 PCMA 1 | PCMU 2 PCMU 3 PCMA 1 G729 1 G729 2 PCMU 1 G729 1 Corrected Text -------------- pktcSigDevCodecTable OBJECT-TYPE ... DESCRIPTION " ... Codec Type Maximum Number of Simultaneous Codecs | PCMA 3 PCMA 2 PCMU 1 PCMA 1 PCMU 2 PCMU 3 PCMA 1 G729 1 G729 2 PCMU 1 G729 1 Notes ----- Issue: Spurious blank line distorts grouping of example line and turns example ineffective. Correction: Delete the spurious line, but add a blank line after the headline, for clarity. -------------------------------------- RFC5098 (draft-ietf-ipcdn-pktc-signaling-15) -------------------------------------- Title : Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) Publication Date : February 2008 Author(s) : G. Beacham, S. Kumar, S. Channabasappa Category : PROPOSED STANDARD Source : IP over Cable Data Network Area : Operations and Management Stream : IETF Verifying Party : IESG
-----Original Message----- From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] Sent: Monday, May 10, 2010 4:54 PM To: ah <at> TR-Sys.de; gordon.beacham <at> motorola.com; satish.kumar <at> ti.com; Sumanth <at> cablelabs.com Cc: Romascanu, Dan (Dan); iesg <at> iesg.org; rfc-editor <at> rfc-editor.org Subject: [Errata Held for Document Update] RFC5098 (1348) The following errata report has been held for document update for RFC5098, "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5098&eid=1348 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alfred Hoenes <ah <at> TR-Sys.de> Date Reported: 2008-03-04 Held by: Dan Romascanu (IESG) Section: 5, pg.20 Original Text ------------- pktcSigCapabilityVendorExt OBJECT-TYPE ... DESCRIPTION " The vendor extension allows vendors to provide a list of additional capabilities. The syntax for this MIB object in ABNF ([RFC5234]) is specified to be zero or more occurrences of vendor extensions, as follows: pktcSigCapabilityVendorExt = *(vendor-extension) | vendor-extension = (ext symbol alphanum) DQUOTE ; DQUOTE | ext = DQUOTE %x58 DQUOTE | symbol = (DQUOTE %x2D DQUOTE)/(DQUOTE %x2D DQUOTE) alphanum = 1*6(ALPHA/DIGIT) " Corrected Text -------------- pktcSigCapabilityVendorExt OBJECT-TYPE ... DESCRIPTION " The vendor extension allows vendors to provide a list of additional capabilities. The syntax for this MIB object in ABNF ([RFC5234]) is specified to be zero or more occurrences of vendor extensions, as follows: pktcSigCapabilityVendorExt = *(vendor-extension) | vendor-extension = ext symbol alphanum ";" | ext = %x58 ; uppercase only X | symbol = %x2B / %x2D ; + or - alphanum = 1*6(ALPHA/DIGIT) " Notes ----- Symptom: ABNF grossly nonsensical: ABNF comment '; DQUOTE' perhaps intended as non-comment; all DQUOTEs apparently should be removed; two identical alternatives for symbol do not make sense. Correction is based on earlier draft versions, applying the corrections necessary to obtain valid ABNF, yet specifying what probably was intended. Alternatively, the following line might be substituted above: | symbol = "+" / "-" -------------------------------------- RFC5098 (draft-ietf-ipcdn-pktc-signaling-15) -------------------------------------- Title : Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) Publication Date : February 2008 Author(s) : G. Beacham, S. Kumar, S. Channabasappa Category : PROPOSED STANDARD Source : IP over Cable Data Network Area : Operations and Management Stream : IETF Verifying Party : IESG
-----Original Message----- From: RFC Errata System [mailto:rfc-editor <at> rfc-editor.org] Sent: Monday, May 10, 2010 4:55 PM To: ah <at> TR-Sys.de; gordon.beacham <at> motorola.com; satish.kumar <at> ti.com; Sumanth <at> cablelabs.com Cc: Romascanu, Dan (Dan); iesg <at> iesg.org; rfc-editor <at> rfc-editor.org Subject: [Errata Held for Document Update] RFC5098 (1349) The following errata report has been held for document update for RFC5098, "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5098&eid=1349 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alfred Hoenes <ah <at> TR-Sys.de> Date Reported: 2008-03-04 Held by: Dan Romascanu (IESG) Section: 5,pg.31-33 Original Text ------------- - Corrected Text -------------- osi any value (not used) Notes ----- Incomplete specification: The line given as 'corrected text' is missing from the tabular listings of all (other) cases possible, in the DESCRIPTION clauses of the following three scalar MIB objects, on pp.31-33 of the RFC: pktcSigDevVmwiAfterDTAS pktcSigDevVmwiAfterRPAS pktcSigDevVmwiDTASAfterLR -------------------------------------- RFC5098 (draft-ietf-ipcdn-pktc-signaling-15) -------------------------------------- Title : Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) Publication Date : February 2008 Author(s) : G. Beacham, S. Kumar, S. Channabasappa Category : PROPOSED STANDARD Source : IP over Cable Data Network Area : Operations and Management Stream : IETF Verifying Party : IESG
The IP over Cable Data Network (ipcdn) working group in the Operations and Management Area has concluded. The IESG contact persons are Dan Romascanu and Ron Bonica. The mailing list will remain active for clarification questions and implementation discussions and reports.
A new Request for Comments is now available in online RFC libraries.
RFC 5428
Title: Management Event Management Information Base
(MIB) for PacketCable- and IPCablecom-Compliant
Devices
Author: S. Channabasappa, W. De Ketelaere,
E. Nechamkin
Status: Standards Track
Date: April 2009
Mailbox: Sumanth <at> cablelabs.com,
deketelaere <at> tComLabs.com,
enechamkin <at> broadcom.com
Pages: 37
Characters: 78139
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipcdn-pktc-eventmess-14.txt
URL: http://www.rfc-editor.org/rfc/rfc5428.txt
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a basic set of managed objects for Simple
Network Management Protocol (SNMP)-based management of events that
can be generated by PacketCable- and IPCablecom-compliant Multimedia
Terminal Adapter devices. [STANDARDS TRACK]
This document is a product of the IP over Cable Data Network Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute
Folks,
The only remaining item on the IPCDN WG charter is “Re-evaluate charter and milestones or conclude wg”. All but one of our IPCDN drafts are published, and the final draft (draft-ietf-ipcdn-pktc-eventmess-14) is in the RFC Editor’s Queue.
The IPCDN co-chairs agree that when the final draft is published as an RFC, we should conclude the working group.
Our plan is to make the working group ‘dormant’ as described in RFC 2418: keeping the mailing list but no longer conducting formal activities. We will also figure out how to maintain www.ipcdn.org as an archive.
Are there any objections to this plan?
-- Rich and Jean-Francois, IPCDN co-chairs
_______________________________________________ IPCDN mailing list IPCDN <at> ietf.org https://www.ietf.org/mailman/listinfo/ipcdn
Congratulations to the editors and to the WG for completing this milestone. Dan -----Original Message----- From: ietf-announce-bounces <at> ietf.org [mailto:ietf-announce-bounces <at> ietf.org] On Behalf Of The IESG Sent: Tuesday, August 19, 2008 1:14 AM To: IETF-Announce Cc: ipcdn chair; ipcdn mailing list; Internet Architecture Board; RFC Editor Subject: Protocol Action: 'Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices' to Proposed Standard The IESG has approved the following document: - 'Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices ' <draft-ietf-ipcdn-pktc-eventmess-14.txt> as a Proposed Standard This document is the product of the IP over Cable Data Network Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-14.t xt Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. Working Group Summary This document represents the WG consensus as a whole: the WG as a whole understands and agrees with it. Protocol Quality Dan Romascanu reviewed the document for the IESG. David Harrington reviewed it as MIB Doctors, and the MIB Doctor team debated some of the aspects of his review. Pasi Eronen performed the GenART review. The MIB module defined in this document is based on the original PacketCable 1.5 Management Event MIB. The WG expectation is that CableLabs will require implementation of the final (RFC) version of this internet-draft for PacketCable 2.0 certified user equipment. The ETSI "AT Working Group Digital" has also indicated their interest in publication of this internet-draft as an RFC. _______________________________________________ IETF-Announce mailing list IETF-Announce <at> ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
The IESG has approved the following document: - 'Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices ' <draft-ietf-ipcdn-pktc-eventmess-14.txt> as a Proposed Standard This document is the product of the IP over Cable Data Network Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-14.txt Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. Working Group Summary This document represents the WG consensus as a whole: the WG as a whole understands and agrees with it. Protocol Quality Dan Romascanu reviewed the document for the IESG. David Harrington reviewed it as MIB Doctors, and the MIB Doctor team debated some of the aspects of his review. Pasi Eronen performed the GenART review. The MIB module defined in this document is based on the original PacketCable 1.5 Management Event MIB. The WG expectation is that CableLabs will require implementation of the final (RFC) version of this internet-draft for PacketCable 2.0 certified user equipment. The ETSI "AT Working Group Digital" has also indicated their interest in publication of this internet-draft as an RFC.
Folks, We have posted version -14 of draft-ietf-ipcdn-pktc-eventmess, (http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-14. txt). This version incorporates the comments received from Pasi and Lars, based on the resolutions proposed by Rich Woundy and the co-authors. The changes are summarized at the end of this email. I have also included the results from IDNits verification and MIB compilation. - S Summary of changes: ------------------- #1: "The SYSLOG WG is obtaining a port number for SYSLOG over TLS that we will use as the DEFVAL for pktcEventSyslogPort." Specifically, the following change is suggested: DEFVAL { syslogs } -- RFC Editor - replace syslogs with the IANA-assigned -- SYSLOG over TLS port in [RFCCCC ] and remove this note #2: We also need to delete the following sentence from pktcEventSyslogAddress: 'The MTA SHOULD NOT attempt to route to a non-routable syslog IP address.' #3: Align labels for the textual convention SyslogSeverityMask with the syslog-tc-mib I-D (http://tools.ietf.org/html/draft-ietf-syslog-tc-mib-08) These labels also appear in the DESCRIPTION text of pktcEventClassSeverity and pktcEventReporting. Editorial changes: = Updated Acknowledgements to add Pasi and Lars = Updated dates IDNits: ------ Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748: --------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: --------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/ID-Checklist.html: --------------------------------------------------------------------- No issues found here. Miscellaneous warnings: --------------------------------------------------------------------- No issues found here. Checking references for intended status: Proposed Standard --------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'PKT-SP-PROV' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCABC' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCAAA' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCBBB' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCCCC' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCDDD' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCEEE' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T-J176' -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSITS101909-22' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-ENTERPRISE' Summary: 0 errors (**), 0 warnings (==), 10 comments (--). MIB compilation results (http://www.ibr.cs.tu-bs.de/bin/smitools.cgi) --------------------------------------------------------------------- = The following are related to SYSLOG-TC-MIB: mibs/PKTC-IETF-EVENT-MIB:79: [2] {bad-identifier-case} `XXX' should start with a lower case letter mibs/PKTC-IETF-EVENT-MIB:79: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element mibs/PKTC-IETF-EVENT-MIB:340: [2] {defval-syntax} default value syntax does not match object syntax = The following are related to PKTC-IETF-EVENT-MIB mibs/PKTC-IETF-EVENT-MIB:79: [2] {bad-identifier-case} `XXX' should start with a lower case letter mibs/PKTC-IETF-EVENT-MIB:79: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element mibs/PKTC-IETF-EVENT-MIB:340: [2] {defval-syntax} default value syntax does not match object syntax Note: The first two are obvious. The last one is due to the recent change to the default port to reflect tls as the transport.
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices Author(s) : S. Channabasappa, I. Property Filename : draft-ietf-ipcdn-pktc-eventmess-14.txt Pages : 38 Date : 2008-08-17 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. De Ketelaere/Nechamkin/Channabasappa Expires - February 2009 [page 1] PacketCable/IPCablecom Event management MTA MIB August 2008 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-14.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
_______________________________________________ IPCDN mailing list IPCDN <at> ietf.org https://www.ietf.org/mailman/listinfo/ipcdn
 |
|
|
|
|
|
|
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
RSS Feed1 | |
|---|---|
3 | |
4 | |
3 | |
4 | |
2 | |
2 | |
6 | |
1 | |
4 | |
2 | |
5 | |
3 | |
4 | |
4 | |
2 | |
4 | |
4 | |
8 | |
2 | |
3 | |
10 | |
20 | |
16 | |
14 | |
15 | |
20 | |
27 | |
58 | |
36 | |
27 | |
37 | |
4 | |
6 | |
7 | |
26 | |
121 | |
7 | |
20 | |
47 | |
35 | |
42 | |
53 | |
19 | |
19 | |
74 | |
16 | |
43 | |
59 | |
22 | |
22 | |
72 | |
40 | |
78 | |
50 | |
37 | |
24 | |
24 | |
37 | |
34 | |
97 | |
51 | |
23 | |
33 | |
13 | |
4 | |
10 | |
11 | |
17 |