internet-drafts | 15 Jun 16:33 2011
Picon

I-D Action: draft-ietf-ancp-mib-an-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the Access Node Control Protocol Working Group of the IETF.

	Title           : Access Node Control Protocol (ANCP) MIB module for Access Nodes
	Author(s)       : Stefaan De Cnodder
                          Moti Morgenstern
	Filename        : draft-ietf-ancp-mib-an-06.txt
	Pages           : 37
	Date            : 2011-06-15

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols.  In particular it defines
   objects for managing access nodes that are using the Access Node
   Control Protocol (ANCP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ancp-mib-an-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ancp-mib-an-06.txt
internet-drafts | 15 Jun 18:32 2011
Picon

I-D Action: draft-ietf-ancp-mib-an-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the Access Node Control Protocol Working Group of the IETF.

	Title           : Access Node Control Protocol (ANCP) MIB module for Access Nodes
	Author(s)       : Stefaan De Cnodder
                          Moti Morgenstern
	Filename        : draft-ietf-ancp-mib-an-07.txt
	Pages           : 37
	Date            : 2011-06-15

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols.  In particular it defines
   objects for managing access nodes that are using the Access Node
   Control Protocol (ANCP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ancp-mib-an-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ancp-mib-an-07.txt
internet-drafts | 17 Jun 14:19 2011
Picon

I-D Action: draft-ietf-ancp-mc-extensions-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the Access Node Control Protocol Working Group of the IETF.

	Title           : Multicast Control Extensions for ANCP
	Author(s)       : Francois Le Faucheur
                          Roberta Maglione
                          Tom Taylor
	Filename        : draft-ietf-ancp-mc-extensions-05.txt
	Pages           : 96
	Date            : 2011-06-17

   This document specifies the extensions to the Access Node Control
   Protocol required for support of the multicast use cases defined in
   the Access Node Control Protocol framework document and one
   additional use case described in this document.  These use cases are
   organized into the following ANCP capabilities:

   o  NAS-initiated multicast replication;

   o  conditional access with white and black lists;

   o  conditional access with grey lists;

   o  bandwidth delegation;

   o  committed bandwidth reporting.

   These capabilities may be combined according to the rules given in
   this specification.

(Continue reading)

Tom Taylor | 17 Jun 14:24 2011
Picon

Fwd: New Version Notification for draft-ietf-ancp-mc-extensions-05.txt

I have updated the document to take account of the changes to the base 
protocol document. The changes from -04 include:

-- changes to section number references in the base protocol document
-- additional text in the documentation of the Port Management message
-- changed "Code" to Result Code" to avoid confusion with other "Code" types
-- updated the IANA section to follow the base protocol document (no 
substantive changes)

This should be ready for Last Call.

Tom

-------- Original Message --------
Subject: New Version Notification for draft-ietf-ancp-mc-extensions-05.txt
Date: Fri, 17 Jun 2011 05:19:19 -0700
From: internet-drafts <at> ietf.org
To: tom111.taylor <at> bell.net
CC: tom111.taylor <at> bell.net, flefauch <at> cisco.com, 
roberta.maglione <at> telecomitalia.it

A new version of I-D, draft-ietf-ancp-mc-extensions-05.txt has been 
successfully submitted by Tom Taylor and posted to the IETF repository.

Filename:	 draft-ietf-ancp-mc-extensions
Revision:	 05
Title:		 Multicast Control Extensions for ANCP
Creation date:	 2011-06-17
WG ID:		 ancp
Number of pages: 96
(Continue reading)

Bocci, Matthew (Matthew | 22 Jun 18:56 2011

Meeting slots for Quebec

Folks,

Please can you let me know if you want a slot at the ANCP meeting in Quebec City.

Regards

Matthew
_______________________________________________
ANCP mailing list
ANCP <at> ietf.org
https://www.ietf.org/mailman/listinfo/ancp
Michael Scott | 30 Jun 18:59 2011
Picon

Minor errors in ANCP draft protocol document

Hi all

While doing some work on an ANCP implementation I came across a couple 
of minor errors in the current ANCP draft. I hope this isn't seen as 
overly pedantic, I'm simply trying to help ensure the document is as 
accurate as possible.

The first is that in section 8.3 the first bullet point states

"The Result field in the request SHOULD be set to AckAll (0x1),"

however in section 3.6.1.3 AckAll is defined to be 0x2.

The second is that Figure 12 in section 4.5 contains fields marked 
"Error Message Length" and "Error Message" but the text describes them 
as "Result Message Length" and "Result Message".

Regards

Michael
Tom Taylor | 1 Jul 01:02 2011
Picon

Re: Minor errors in ANCP draft protocol document

Thanks. We'll catch them in AUTH48.

On 30/06/2011 12:59 PM, Michael Scott wrote:
> Hi all
>
> While doing some work on an ANCP implementation I came across a couple
> of minor errors in the current ANCP draft. I hope this isn't seen as
> overly pedantic, I'm simply trying to help ensure the document is as
> accurate as possible.
>
>
> The first is that in section 8.3 the first bullet point states
>
> "The Result field in the request SHOULD be set to AckAll (0x1),"
>
> however in section 3.6.1.3 AckAll is defined to be 0x2.
>
>
> The second is that Figure 12 in section 4.5 contains fields marked
> "Error Message Length" and "Error Message" but the text describes them
> as "Result Message Length" and "Result Message".
>
>
> Regards
>
> Michael
> _______________________________________________
> ANCP mailing list
> ANCP <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>
>

Gmane