From ancp-bounces@ietf.org Mon Jul 03 09:52:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxOqh-0004EL-1O; Mon, 03 Jul 2006 09:52:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxOqf-0004EG-AG
	for ancp@ietf.org; Mon, 03 Jul 2006 09:52:25 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxOqd-0006Bz-UR
	for ancp@ietf.org; Mon, 03 Jul 2006 09:52:25 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2006 15:52:23 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k63DqNrq007532
	for <ancp@ietf.org>; Mon, 3 Jul 2006 15:52:23 +0200 (MEST)
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 3 Jul 2006 15:52:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 3 Jul 2006 15:52:13 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4022F930B@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [L2CP] Draft ANCP agenda
Thread-Index: AcaZ+HjuWsd3nO5pRbO3IUe5iQA/eQEri6lA
X-Priority: 1
Priority: Urgent
Importance: high
From: "Wojciech Dec \(wdec\)" <wdec@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 03 Jul 2006 13:52:22.0895 (UTC)
	FILETIME=[E8CA7FF0:01C69EA7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Subject: [ANCP] RE: [L2CP] Draft ANCP agenda
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Message intended for all WG meeting presenters,

Would you kindly please email Matthew and myself the slides that you
intend to use at the meeting by 1700CET on Friday 7 July? We need to
post the slides to the WG page so as to facilitate remote participation,
and given that we're pretty much the first ones to go on Monday there
will be little time to do this on the day itself.

Thanks,
Woj.

-----Original Message-----
From: Matthew.Bocci@alcatel.co.uk [mailto:Matthew.Bocci@alcatel.co.uk]=20
Sent: 27 June 2006 16:46
To: l2CP@ietf.org
Subject: [L2CP] Draft ANCP agenda

All,

Please find attached a draft agenda for the ANCP meeting in Montreal.
This has been scheduled for 09:00-11;30 on Monday 10th July.

Plese let me know if you have any comments on the agenda.

best regards,

Matthew

Access Node Control Protocol.
-----------------------------

09:00 - 10:30, Monday 10th July.

Chairs:
Matthew Bocci (matthew.bocci@alcatel.co.uk) Wojceih Dec (wdec@cisco.com)

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

AGENDA
------
1. Introduction / agenda tweaking / Blue Sheets (Chairs - 5 mins)

2. Working Group Charter (Chairs - 10 mins)
- Changes to the charter since the BoF.
- Revised milestones
- Mailing list changes

3. ANCP Requirements (Stefaan de Cnodder - 15mins)
http://www.ietf.org/internet-drafts/draft-ooghe-ancp-framework-00.txt
Update on changes since the BoF

4. GSMP extensions for layer2 control (L2C) Topology Discovery and Line
Configuration  (Sanjay Wadhwa - 15 mins)
http://www.ietf.org/internet-drafts/draft-wadhwa-gsmp-l2control-configur
ation-01.txt
Update on changes since the BoF.

5. ANCP Graceful Restart Mechanism (Sanjay Wadhwa - 10 mins)

6. ANCP MIBs (Stefaan de Cnodder - 10 mins)

7. Discussion of outstanding working group items (Chairs - 30mins)
- Access Node Port and Functional Partitioning and multiple controllers.
- Light-weight transport protocol.
- ANCP Protocol Security.
- Multicast control.








_______________________________________________
L2cp mailing list
L2cp@ietf.org
https://www1.ietf.org/mailman/listinfo/l2cp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Tue Jul 04 02:54:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fxene-0002D6-OT; Tue, 04 Jul 2006 02:54:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxXF1-0001Ia-RB; Mon, 03 Jul 2006 18:50:07 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FxXF1-0004Rj-GU; Mon, 03 Jul 2006 18:50:07 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k63Mo19F029728
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 3 Jul 2006 22:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FxXEv-0001HC-Fw; Mon, 03 Jul 2006 18:50:01 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1FxXEv-0001HC-Fw@stiedprstage1.ietf.org>
Date: Mon, 03 Jul 2006 18:50:01 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
X-Mailman-Approved-At: Tue, 04 Jul 2006 02:54:21 -0400
Cc: ancp@ietf.org
Subject: [ANCP] WG Action: Access Node Control Protocol (ancp) 
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

A new IETF working group has been formed in the Internet Area. For 
additional information, please contact the Area Directors or the WG Chairs.

+++

Access Node Control Protocol (ancp)
====================================

Current Status: Active Working Group

Chair(s):
Matthew Bocci <matthew.bocci@alcatel.co.uk> 
Wojciech Dec <wdec@cisco.com>

Internet Area Director(s):
Mark Townsley <townsley@cisco.com>
Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
Mark Townsley <townsley@cisco.com> 

Technical Advisor(s):
Dan Romascanu <dromasca@avaya.com>

Mailing Lists:
General Discussion: ancp@ietf.org
To Subscribe: ancp-request@ietf.org
In Body: subscribe your_email_address
Archive: http://www.ietf.org/mail-archive/web/ancp/index.html

Description:

Purpose:

The purpose of the ANCP WG is to standardize an IP based Access Node 
Control Protocol (ANCP) for use in service provider Digital Subscriber 
Line (DSL) access and aggregation networks. ANCP operates between an 
Access Node (AN) and Network Access Server (NAS). 

Necessary Terminology:

Access Node (AN) - Network device, usually located at a service 
provider central office or street cabinet, that terminates acess loop 
connections from Subscribers. In DSL, this is often referred to as a 
Digital Subscriber Line Access Multiplexer (DSLAM)

Network Access Server (NAS) - Network device which aggregates 
multiplexedSubscriber traffic from a number of Access Nodes. The NAS 
plays a central role in per-subsciber policy enforcement and QoS. Often 
referred to as an Broadband Network Gateway (BNG) or Broadband Remote 
Access Server (BRAS). A detailed definition of the NAS is given in 
RFC2881.

Goals:

ANCP is intended to address the requirement for a bidirectional, IP-
based, control protocol that operates across multiple types (i.e., 
Ethernet, ATM) of DSL access and aggregation networks. The goal of an 
ANCP message exchange is to convey status and control information 
between one or more ANs and one or more NASs without going through 
intermediate element managers. 

The ANCP WG will address the following four use-cases:

1. Dynamic Access Loop Attributes
Various queuing and scheduling mechanisms are used in access networks 
to avoid congestion while dealing with multiple flows and distinct QoS 
profiles. Communicating the access-loop status, attributes and current 
DSL synchronization rate between the AN and Subscriber up to the NAS is 
desirable, particularly when the NAS is providing QoS for individual 
flows and subscribers. ANCP will provide a mechanism to communicate 
dynamic access-loop attributes from the AN to the NAS.

2. Access Loop Configuration
In additional to reporting Access Loop characteristics from the AN to 
the NAS, ANCP will allow a NAS to send loop-specific configuration 
information to an AN based on the results of subscriber authentication 
and authorization (e.g., after AAA responses have been received at the 
NAS). 

3. Remote Connectivity Test
Traditional DSL access and aggregation networks employ point-to-point 
ATM circuits between the AN and NAS for each subscriber, allowing 
troubleshooting of the local loop from the NAS via ATM OAM tools. With 
the increasing deployment of Ethernet in the access and aggregation 
network, operators require consistent methods to test and troubleshoot 
connectivity for mixed Ethernet and ATM access networks (including the 
local loop). ANCP will allow a remote procedure for a local loop 
connectivity test to be triggered from the NAS with results 
communicated back to the NAS. 

4. Multicast
When multicast replication for subscriber-bound traffic is performed at
the AN, it offloads the network between the AN and NAS. However, a
subscriber's policy and configuration for multicast traffic may only be
known at the NAS. ANCP will provide a mechanism to communicate the
necessary information exchange between the AN and NAS so as to allow 
the AN to perform subscriber bound multicast group replication in line 
with the subscriber's policy and configuration, and also allow the NAS 
to follow each subscriber's multicast group membership.

Non-Goals:

ANCP is an IP-based protocol that operates between the AN and NAS, over 
a DSL access and aggregation network. It will not address setup or 
configuration of circuits or connections in the access and aggregation 
network itself.

The focus of this WG is on one very specific application space. While 
the design of the protocol must be general as to not preclude other 
uses in the future should a need arise, it is not a goal of this WG
to address specific requirements outside of DSL access and aggregation 
networks. 

Security:

The ANCP working group will provide a threat analysis and address the 
associated security aspects of the control protocol. 

Resiliency and Scalabilty: 

A graceful restart mechanism will be defined to enable the protocol to 
be resilient to network failures between the AN and NAS.

Scalability at the NAS is of primary concern, as it may be aggregating 
traffic from a large number of ANs, which in turn may be serving a 
large number of Subscribers. ANCP traffic should not become a denial of 
service attack on the NAS control plane. Format of messages, pacing, 
transport over UDP or TCP, etc. will be considered with this in mind.

For reasons of aggregation network scalability, some use cases require 
that aspects of NAS or AN functionality may be distributed in nodes in 
the aggregation network. In these cases, ANCP can run between these 
nodes.

Deliverables:

The working group will define a basic framework and requirements 
document intended for Informational publication, focusing on the four 
use-cases outlined in this charter. This document will include a 
security threat analysis and associated requirements. The WG will then 
investigate and define a solution for an IP based control protocol 
meeting these requirements. 

There are early interoperable implementations of an ANCP-like protocol 
which are based on an extended subset of the GSMPv3 protocol. This 
running code will be the the starting point for the working group 
solution, and will be abandoned only if the WG determines it is not 
adequate to meet requirements going forward.

Coordination with other Working Groups or Organizations:

The working group will coordinate with the ADSL MIB working group so 
the the management framewoirk and MIB modules are consistent for DSL 
access environments. The working group will re-use, as far as possible, 
standard MIB modules that have already been defined.

The remote connectivity test use case may require coordination with 
ITU-T Ethernet OAM work, and with IEEE 802.1ag.

Goals and Milestones:

November 2006 Accept WG I-D for ANCP Framework and Requirements 
January 2007  Accept WG I-D for Access Node Control Protocol (ANCP)
January 2007  Framework and Requirements last call
March 2007    Accept WG I-D for ANCP MIB
April 2007    Access Node Control Protocol (ANCP) Last Call
May 2007      ANCP MIB Last Call
July 2007     Re-charter or conclude Working Group

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Tue Jul 04 08:13:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fxjmu-0005gv-Te; Tue, 04 Jul 2006 08:13:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fxjmt-0005gq-7L
	for ancp@ietf.org; Tue, 04 Jul 2006 08:13:55 -0400
Received: from mailf.telecomitalia.it ([156.54.233.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fxjmp-0003Ga-FP
	for ancp@ietf.org; Tue, 04 Jul 2006 08:13:55 -0400
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	mailf.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 4 Jul 2006 14:13:45 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 4 Jul 2006 14:13:44 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Subject: [ANCP] Wadhwa draft 01- Access-Loop-Circuit-ID comment
Date: Tue, 4 Jul 2006 14:13:44 +0200
Message-ID: <9E577E61D0108D4F8CD482029B613F5CA08CB5@PTPEVS108BA020.idc.cww.telecomitalia.it>
Importance: normal
Priority: normal
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Wadhwa draft 01- Access-Loop-Circuit-ID comment
thread-index: AcafY0jaMvXHenAxQcGWx2h1/SrS8g==
From: "Maglione Roberta" <roberta.maglione@telecomitalia.it>
To: <ancp@ietf.org>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>
X-OriginalArrivalTime: 04 Jul 2006 12:13:44.0736 (UTC)
	FILETIME=[4BB4DA00:01C69F63]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b058151374d77ee76edaac850f7449fb
Cc: Fanelli Gaetano Saverio <gaetanosaverio.fanelli@telecomitalia.it>,
	Giacobbe Giampaolo <giampaolo.giacobbe@telecomitalia.it>
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2096856439=="
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2096856439==
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C69F63.4B465E21"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C69F63.4B465E21
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sanjay and all,

               I have a comment regarding Access-Loop-Circuit-ID TLV
described in internet-draft:
'draft-wadhwa-gsmp-l2control-configuration-01'
Section 5.4.1, talking about Access-Loop-Circuit-ID, says:=20
=20
"Type (Access-Loop-Circuit-ID =3D 0x01): This is a mandatory TLV and=20
 contains an identifier of the subscriber's connection to the access=20
 node (i.e.  "local loop"). The "local loop" can be ATM based or=20
 Ethernet based. The "Access Loop Circuit ID" has local significance=20
 at the access node. The exact usage on the BRAS is beyond the scope=20
  of this document. It is desirable that the format used for "local=20
loop" identification in GSMP messages is similar to what is used by=20
the access nodes in subscriber signaling messages when the access=20
nodes act as "signaling relay agents" as outlined in [7] and [8]."
=20
>From my understanding, correct me if I'm wrong, the word "desirable" is
used to make this definition general enough to be applied to different
types of scenarios, in fact also DSL forum document WT-147 in section
5.3.1 says: "This document reuses the port addressing scheme specified
in WT-101. It should be noted however that the use of such a scheme does
not imply the actual existence of a PPPoE or DHCP session, nor on the
specific inter-working function present in the Access Node. In some
cases, no PPPoE or DHCP session may be present, while the port
addressing would still be desirable"=20
=20
However I think, IMHO, that if there is a scenario where either PPPoE
Intermediate Agent or DHCP IA is present the syntax used to identify the
Access-Loop-Circuit ID in GSMP messages must be the same used by PPPoE
IA or DHCP IA in order to simplify for the BRAS the correlation between
GSMP messages and actions to be performed when those messages are
received on different sessions identified by the same PPPoE IA.
For example if a BRAS receives a PORT-DOWN message sent by the DSLAM to
notify the the BRAS that a line went down, it makes sense that  BRAS
tears down all the PPP sessions associated to that line. In this case
having an  Access-Loop-Circuit ID in the PORT DOWN message that exactly
matches the PPPOE IA makes this operation simple because the BRAS can
associate the Access-Loop-Circuit ID, obtained from the PORTDOWN
message, with the same ID coming from PPPoE IA that identifies each
single PPP session.=20
=20

Please let me know what you think.

Thanks and best regards,

=20

Roberta

=20

=20

------------------------------------------------------------------------
----
Roberta Maglione
Telecom Italia - Broadband Network Services Innovation
Via G. Reiss Romoli, 274
10148 Torino - Italy
Phone: +39 011 228 5007
e-mail: roberta.maglione@telecomitalia.it
------------------------------------------------------------------------
------

=20

=20

=20

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

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                        
------_=_NextPart_001_01C69F63.4B465E21
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DIT link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi Sanjay and all,<o:p></o:p></span></font></p>

<pre><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
face=3DArial><span lang=3DEN-US style=3D'font-family:Arial'>I have a =
comment regarding </span></font><span
lang=3DEN-US>Access-Loop-Circuit-ID TLV</span><font face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial'> described in internet-draft: =
'draft-wadhwa-gsmp-l2control-configuration-01'</span></font><span
lang=3DEN-US><o:p></o:p></span></pre><pre><font size=3D2 face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>S</span></font><font =
face=3DArial><span
lang=3DEN-US style=3D'font-family:Arial'>ection 5.4.1, talking about =
</span></font><span
lang=3DEN-US>Access-Loop-Circuit-ID,</span><font face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial'> says: =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>&#8220;</span></font><span
lang=3DEN-US>Type (Access-Loop-Circuit-ID =3D 0x01): This is a mandatory =
TLV and <o:p></o:p></span></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>&nbsp;contains an identifier of the =
subscriber&#8217;s connection to the access =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>&nbsp;node (i.e.&nbsp; &#8220;local =
loop&#8221;). The &#8220;local loop&#8221; can be ATM based or =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>&nbsp;Ethernet based. The &#8220;Access Loop =
Circuit ID&#8221; has local significance =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>&nbsp;at the access node. The exact usage on =
the BRAS is beyond the scope</span></font><font
face=3DArial><span lang=3DEN-US style=3D'font-family:Arial'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;of this =
document.</span></font><span
lang=3DEN-US> It is <i><span =
style=3D'font-style:italic'>desirable</span></i> that </span><span
lang=3DEN-US>the format used for &#8220;local =
<o:p></o:p></span></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>loop&#8221; identification in GSMP messages =
is similar to what is used by <o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>the access nodes in subscriber signaling =
messages when the access <o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-US =
style=3D'font-size:10.0pt'>nodes act as &#8220;signaling relay =
agents&#8221; as outlined in [7] and [8]</span></font><font
face=3DArial><span lang=3DEN-US =
style=3D'font-family:Arial'>.&#8221;</span></font><font
face=3DArial><span lang=3DEN-US =
style=3D'font-family:Arial'><o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>From my understanding, =
correct me if I&#8217;m wrong, the word &#8220;desirable&#8221; is used =
to make this definition general enough to be applied to different types =
of scenarios, in fact also DSL forum document WT-147 in section 5.3.1 =
says: &#8220;</span></font><span
lang=3DEN-US>This document reuses the port addressing scheme specified =
in WT-101. It should be noted however that the use of such a scheme does =
not imply the actual existence of a PPPoE or DHCP session, nor on the =
specific inter-working function present in the Access Node. In some =
cases, no PPPoE or DHCP session may be present, while the port =
addressing would still be desirable</span><font
face=3DArial><span lang=3DEN-US style=3D'font-family:Arial'>&#8221; =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></fo=
nt></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>However I think, IMHO, that =
if there is a scenario where either PPPoE Intermediate Agent or DHCP IA =
is present the syntax used to identify the Access-Loop-Circuit ID in =
GSMP messages must be the same used by PPPoE IA or DHCP IA in order to =
simplify for the BRAS the correlation between GSMP messages and actions =
to be performed when those messages are received on different sessions =
identified by the same PPPoE =
IA.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>For example if a BRAS =
receives a PORT-DOWN message sent by the DSLAM to notify the the BRAS =
that a line went down, it makes sense that &nbsp;BRAS &nbsp;tears down =
all the PPP sessions associated to that line. In this case having an =
&nbsp;<i><span
style=3D'font-style:italic'>Access-Loop-Circuit ID</span></i> in the =
PORT DOWN message that exactly matches the PPPOE IA makes this operation =
simple because the BRAS can associate the <i><span
style=3D'font-style:italic'>Access-Loop-Circuit ID,</span></i> obtained =
from the PORTDOWN message, with the same ID coming from PPPoE IA that =
identifies each single PPP session. =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></pre>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Please let me know what you =
think.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks and best =
regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Roberta<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>-----------------------------------------------=
-----------------------------<br>
Roberta Maglione<br>
Telecom Italia - B</span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>roadband Network Services Innovation<br>
Via G. Reiss Romoli, 274<br>
10148 Torino - Italy<br>
Phone: +39 011 228 5007<br>
e-mail: <a =
href=3D"mailto:roberta.maglione@telecomitalia.it">roberta.maglione@teleco=
mitalia.it</a><br>
-------------------------------------------------------------------------=
-----</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span><o:p></o:p></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<DIV><FONT size=3D2><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
<BR>CONFIDENTIALITY=20
NOTICE<BR>This message and its attachments are addressed solely to the=20
persons<BR>above and may contain confidential information. If you have=20
received<BR>the message in error, be informed that any use of the =
content=20
hereof<BR>is prohibited. Please return it immediately to the sender and=20
delete<BR>the message. Should you have any questions, please contact us=20
by<BR>replying to </FONT><A =
href=3D"mailto:webmaster@telecomitalia.it"><FONT=20
face=3D"Courier New">webmaster@telecomitalia.it</FONT></A><FONT=20
face=3D"Courier New">.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thank=20
you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
</FONT><A href=3D"http://www.telecomitalia.it"><FONT=20
face=3D"Courier New">www.telecomitalia.it</FONT></A><BR><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
</FONT></FONT></DIV>
</body>

</html>

------_=_NextPart_001_01C69F63.4B465E21--


--===============2096856439==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============2096856439==--




From ancp-bounces@ietf.org Fri Jul 07 07:52:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyosT-0001Ml-OT; Fri, 07 Jul 2006 07:52:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyosS-0001ME-CS
	for ancp@ietf.org; Fri, 07 Jul 2006 07:52:08 -0400
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyosR-0005XM-FC
	for ancp@ietf.org; Fri, 07 Jul 2006 07:52:08 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by kremlin.juniper.net with ESMTP; 07 Jul 2006 04:52:07 -0700
X-IronPort-AV: i="4.06,215,1149490800"; 
	d="txt'?scan'208"; a="560796331:sNHT91580298"
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6A1BB.C4DB6384"
Date: Fri, 7 Jul 2006 07:52:06 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2803B758AE@proton.jnpr.net>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: ANCP Graceful Restart
Thread-Index: Acahu64Z5imiKD58QZeDfnYwVNM2MQ==
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: <ancp@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 819069d28e3cfe534e22b502261ce83f
Subject: [ANCP] ANCP Graceful Restart
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6A1BB.C4DB6384
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Please find attached an initial version of a draft on ANCP graceful =
restart that we intend to submit to the IETF repository. We would like =
to solicit your feedback/comments.

Thanks
-Sanjay & Derek

 <<draft-wadhwa-ancp-graceful-restart-00.txt>>=20





------_=_NextPart_001_01C6A1BB.C4DB6384
Content-Type: text/plain;
	name="draft-wadhwa-ancp-graceful-restart-00.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-wadhwa-ancp-graceful-restart-00.txt
Content-Disposition: attachment;
	filename="draft-wadhwa-ancp-graceful-restart-00.txt"

DQoNCg0KDQoNCg0KICAgICBXb3JraW5nIEdyb3VwIE5hbWUgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgU2FuamF5IFdhZGh3YSANCiAgICAgSW50ZXJuZXQgRHJhZnQgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEp1bmlwZXIgTmV0d29ya3MgDQogICAg
IEV4cGlyZXM6IEphbnVhcnkgMDQsIDIwMDcgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIERlcmVrIEhhcmtuZXNzIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIEp1bmlwZXIgTmV0d29ya3MgDQogICAgICANCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBKdWx5IDA0LCAyMDA2ICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICANCiAgICAgICAgICAgICAgICAgQ29udHJvbCBQbGFuZSBHcmFjZWZ1bCBSZXN0YXJ0IGV4
dGVuc2lvbnMgZm9yIEFOQ1AgICAgICAgICAgICAgICAgICANCg0KDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgZHJhZnQt
d2FkaHdhLWFuY3AtZ3JhY2VmdWwtcmVzdGFydC0wMC50eHQgDQoNCg0KICAgICAgICAgDQoNCiAg
ICAgU3RhdHVzIG9mIHRoaXMgTWVtbyANCg0KICAgICAgICAgDQoNCiAgICAgICAgQnkgc3VibWl0
dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhvciByZXByZXNlbnRzIHRoYXQgYW55
IA0KICAgICAgICBhcHBsaWNhYmxlIHBhdGVudCBvciBvdGhlciBJUFIgY2xhaW1zIG9mIHdoaWNo
IGhlIG9yIHNoZSBpcyBhd2FyZSANCiAgICAgICAgaGF2ZSBiZWVuIG9yIHdpbGwgYmUgZGlzY2xv
c2VkLCBhbmQgYW55IG9mIHdoaWNoIGhlIG9yIHNoZSBiZWNvbWVzIA0KICAgICAgICBhd2FyZSB3
aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIHNlY3Rpb24gNiBvZiBCQ1AgNzku
IA0KDQogICAgICAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhl
IEludGVybmV0IEVuZ2luZWVyaW5nIA0KICAgICAgICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFy
ZWFzLCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0IA0KICAgICAgICBvdGhlciBn
cm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0N
CiAgICAgICAgRHJhZnRzLiBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxp
ZCBmb3IgYSBtYXhpbXVtIG9mIA0KICAgICAgICBzaXggbW9udGhzIGFuZCBtYXkgYmUgdXBkYXRl
ZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciANCiAgICAgICAgZG9jdW1lbnRzIGF0
IGFueSB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFz
IA0KICAgICAgICByZWZlcmVuY2UgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4g
YXMgIndvcmsgaW4gcHJvZ3Jlc3MuIiANCg0KICAgICAgICBUaGUgbGlzdCBvZiBjdXJyZW50IElu
dGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQgICAgIA0KICAgICAgICBodHRwOi8vd3d3
LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQgDQoNCiAgICAgICAgVGhlIGxpc3Qgb2Yg
SW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdCAgICAg
DQogICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwgDQoNCiAgICAgICAgVGhp
cyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBKYW51YXJ5IDA0LCAyMDA2LiANCg0KICAg
ICBDb3B5cmlnaHQgTm90aWNlIA0KDQogICAgICAgIENvcHlyaWdodCAoQykgVGhlIEludGVybmV0
IFNvY2lldHkgKDIwMDYpLiAgQWxsIFJpZ2h0cyBSZXNlcnZlZC4gDQoNCiAgICAgQWJzdHJhY3Qg
DQoNCiAgICAgICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgcHJvcG9zZWQgZXh0ZW5zaW9ucyB0
byBBTkNQIChBY2Nlc3MgTm9kZSANCiAgICAgICAgQ29udHJvbCBQcm90b2NvbCkgZm9yIHN1cHBv
cnRpbmcgYSBncmFjZWZ1bCBzdGF0ZSByZXN5bmNocm9uaXphdGlvbiANCiAgICAgIA0KICAgICAg
DQogICAgICANCgwgICAgIFdhZGh3YSBldC5hbCAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDcs
IDIwMDcgICAgICAgICAgICAgICAgIFtQYWdlIDFdIA0KICAgICAgDQoMICAgICBJbnRlcm5ldC1E
cmFmdCAgICAgIGRyYWZ0LXdhZGh3YS1hbmNwLWdyYWNlZnVsLXJlc3RhcnQtMDAgICAgICAgIEp1
bHkgMjAwNiANCiAgICAgICAgIA0KDQogICAgICAgIGJldHdlZW4gTkFTIChuZXR3b3JrIGFjY2Vz
cyBzZXJ2ZXIpIGFuZCBBTiAoYWNjZXNzIG5vZGUpIHVwb24gY29udHJvbCANCiAgICAgICAgcGxh
bmUgcmVzdGFydC4gQmFzZSBBTkNQIGFzIGEgZGVkaWNhdGVkIGNvbnRyb2wgcHJvdG9jb2wgYmV0
d2VlbiBhIA0KICAgICAgICBOQVMgYW5kIGFuIEFOLCBhbmQgaXRzIHZhcmlvdXMgdXNlIGNhc2Vz
IGFyZSBkZWZpbmVkIGluIFsxXS4gDQoNCiAgICAgQ29udmVudGlvbnMgdXNlZCBpbiB0aGlzIGRv
Y3VtZW50IA0KDQogICAgICAgIFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVR
VUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwgDQogICAgICAgICJTSE9VTEQiLCAiU0hPVUxE
IE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzIA0KICAg
ICAgICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQy0y
MTE5IFsxXS4gDQoNCiAgICAgVGFibGUgb2YgQ29udGVudHMgDQoNCiAgICAgICAgVGFibGUgb2Yg
Q29udGVudHMgMiANCg0KICAgICAgICAxICBTcGVjaWZpY2F0aW9uIFJlcXVpcmVtZW50cyAgMyAN
Cg0KICAgICAgICAyICBJbnRyb2R1Y3Rpb24gIDMgDQoNCiAgICAgICAgMyAgR3JhY2VmdWwgUmVz
dGFydCBNZWNoYW5pc20gIDQgDQoNCiAgICAgICAgNCAgR3JhY2VmdWwgUmVzdGFydCBQcm9jZWR1
cmVzIDUgDQoNCiAgICAgICAgICAgNC4xICAgUmVzdGFydGluZyBFbGVtZW50Li4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uNSANCiAgICAgICAgICAgNC4yICAgQU5DUCBOZWln
aGJvciBvZiBSZXN0YXJ0aW5nIEVsZW1lbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uNiANCiAgICAg
ICAgIA0KDQogICAgICAgIDUgIElBTkEgQ29uc2lkZXJhdGlvbnMgIDggDQoNCiAgICAgICAgNiAg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgOCANCg0KICAgICAgICA3ICBSZWZlcmVuY2VzIDggDQoN
CiAgICAgICAgQXV0aG9yJ3MgQWRkcmVzc2VzICAgOSANCg0KICAgICAgICBJbnRlbGxlY3R1YWwg
UHJvcGVydHkgU3RhdGVtZW50IDkgDQoNCiAgICAgICAgRGlzY2xhaW1lciBvZiBWYWxpZGl0eSAg
OSANCg0KICAgICAgICBDb3B5cmlnaHQgU3RhdGVtZW50ICAxMCANCg0KICAgICAgICBBY2tub3ds
ZWRnbWVudCANICAgICAgICAgICAgICAgICAgICAxMCANCg0KICAgICAgICAgDQoNCiAgICAgICAg
IA0KDQogICAgICAgICANCiAgICAgIA0KICAgICAgDQogICAgIFdhZGh3YSBldC5hbCAgICAgICAg
ICAgRXhwaXJlcyBKYW51YXJ5IDQsIDIwMDcgICAgICAgICAgICAgICAgIFtQYWdlIDJdIA0KICAg
ICAgICAgDQoMICAgICBJbnRlcm5ldC1EcmFmdCAgICAgIGRyYWZ0LXdhZGh3YS1hbmNwLWdyYWNl
ZnVsLXJlc3RhcnQtMDAgICAgICAgIEp1bHkgMjAwNiANCiAgICAgICAgIA0KDQogICAgICAgICAN
Cg0KICAgICAgICAgDQoNCiAgICAgICAgIA0KDQogICAgICAgICANCg0KICAgICAgICAgDQoNCiAg
ICAgICAgIA0KDQogICAgICAgICANCg0KICAgICAgICAgDQoNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQogICAgICAgICANCg0KICAgICAgICAgDQoN
CiAgICAgICAgIA0KDQogICAgICAgICANCg0KICAgICAgICAgDQoNCiAgICAgMSAgU3BlY2lmaWNh
dGlvbiBSZXF1aXJlbWVudHMgDQoNCiAgICAgICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNU
IE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLCAgIA0KICAgICAgICCTU0hP
VUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIg
aW4gdGhpcyAgIA0KICAgICAgICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVz
Y3JpYmVkIGluIFJGQyAyMTE5LiANCg0KICAgICAgICAgDQoNCiAgICAgMiAgSW50cm9kdWN0aW9u
IA0KDQogICAgICAgIFR5cGljYWxseSBBTkNQIHByb3RvY29sIGlzIHJ1biBvbiB0aGUgY29udHJv
bCBwbGFuZSBvbiB0aGUgTkFTIA0KICAgICAgICAobmV0d29yayBhY2Nlc3Mgc2VydmVyKSBhbmQg
QU4gKGFjY2Vzcy1ub2RlKS4gQU5DUCBwcm92aWRlcyBmb3IgDQogICAgICAgIHZhcmlvdXMgdXNl
LWNhc2VzIGFzIGRlZmluZWQgaW4gWzFdLiBUaGUgQU4gY2FuIGR5bmFtaWNhbGx5IGluZm9ybSAN
CiAgICAgICAgdGhlIE5BUyBvZiB0aGUgdXBzdHJlYW0gYW5kIGRvd25zdHJlYW0gcmF0ZXMgYW5k
IG90aGVyIGF0dHJpYnV0ZXMgb2YgDQogICAgICAgIHRoZSBEU0wgbGluZXMuIFRoZSBOQVMgdXNl
cyBzb21lIG9mIHRoZXNlIGF0dHJpYnV0ZXMgdG8gY29udHJvbCB0aGUgDQogICAgICAgIGZvcndh
cmRpbmcgYmVoYXZpb3Igb2YgdGhlIHN1YnNjcmliZXIncyB0cmFmZmljLiBBcyBhbiBleGFtcGxl
IHRoZSANCiAgICAgICAgTkFTIHVzZXMgdGhlIGxlYXJudCBkb3duc3RyZWFtIERTTCB0cmFpbiBy
YXRlIG9mIGEgRFNMIGxpbmUgdG8gc2hhcGUgDQogICAgICAgIHRoZSB0cmFmZmljIHRoYXQgd291
bGQgdHJhdmVyc2UgdGhlIERTTCBsaW5lLCBieSBhZGp1c3RpbmcgaXRzIA0KICAgICAgICBoaWVy
YXJjaGljYWwgUU9TIHNjaGVkdWxlci4gQW5vdGhlciBleGFtcGxlIGlzIHRvIHVzZSB0aGUgZHlu
YW1pY2FsbHkgDQogICAgICANCiAgICAgIA0KICAgICBXYWRod2EgZXQuYWwgICAgICAgICAgIEV4
cGlyZXMgSmFudWFyeSA0LCAyMDA3ICAgICAgICAgICAgICAgICBbUGFnZSAzXSANCiAgICAgICAg
IA0KDCAgICAgSW50ZXJuZXQtRHJhZnQgICAgICBkcmFmdC13YWRod2EtYW5jcC1ncmFjZWZ1bC1y
ZXN0YXJ0LTAwICAgICAgICBKdWx5IDIwMDYgDQogICAgICAgICANCg0KICAgICAgICBsZWFybnQg
ZGF0YS1saW5rIHR5cGUgYW5kIHByb3RvY29sIGVuY2Fwc3VsYXRpb24gb3ZlcmhlYWQgb24gdGhl
IA0KICAgICAgICBhY2Nlc3MtbG9vcCBpbiBzaGFwaW5nIHRoZSBzdWJzY3JpYmVyJ3MgdHJhZmZp
YyBhcHByb3ByaWF0ZWx5LiANCiAgICAgICAgQW5vdGhlciB1c2UgY2FzZSBpcyB0aGF0IHRoZSBO
QVMgY29udHJvbHMgbGluZSBwYXJhbWV0ZXJzIGluIHRoZSANCiAgICAgICAgQWNjZXNzIE5vZGUu
IA0KDQogICAgICAgIFR5cGljYWxseSBBTkNQIHByb3RvY29sIGlzIHJ1biBvbiB0aGUgY29udHJv
bCBwbGFuZSBvbiB0aGUgTkFTIGFuZCANCiAgICAgICAgQU4uIEluIG1vc3Qgb2YgY3VycmVudCBO
QVMgcGxhdGZvcm1zLCBmb3J3YXJkaW5nIHBsYW5lIGlzIGRlY291cGxlZCANCiAgICAgICAgZnJv
bSB0aGUgY29udHJvbCBwbGFuZS4gSW4gc3VjaCBzeXN0ZW1zLCB0aGUgZm9yd2FyZGluZyBwbGFu
ZSBjYW4gDQogICAgICAgIGNvbnRpbnVlIHRvIG9wZXJhdGUgZXZlbiBpZiB0aGUgY29udHJvbCBw
bGFuZSByZXNldHMuIEl0IGlzIHBvc3NpYmxlIA0KICAgICAgICBmb3IgQU5DUCBwcm90b2NvbCB0
byByZXN0YXJ0IGVpdGhlciBkdWUgdG8gYSBwbGFubmVkIGNvbnRyb2wgcGxhbmUgDQogICAgICAg
IHJlc2V0IG9uIHRoZSBOQVMgb3IgZHVlIHRvIGEgY29udHJvbCBwbGFuZSByZXNldCBjYXVzZWQg
YnkgYSBzb2Z0d2FyZSANCiAgICAgICAgb3IgaGFyZHdhcmUgZmFpbHVyZSBvbiB0aGUgTkFTLiBJ
biB0aGlzIGNhc2UgdGhlIEFOQ1AgYWRqYWNlbmN5IGlzIA0KICAgICAgICBsb3N0IGJ1dCBub3Qg
YWxsIGRhdGEgcHJvdmlkZWQgYnkgdGhlIEFOIHRvIHRoZSBOQVMgbWF5IGJlIGxvc3QuIA0KICAg
ICAgICBGdXJ0aGVybW9yZSB0aGUgc3Vic2NyaWJlciBzZXNzaW9ucyBhcmUgc3RpbGwgYWN0aXZl
IGluZGVwZW5kZW50IG9mIA0KICAgICAgICB0aGUgQU5DUCBhZGphY2VuY3kgc3RhdGUuIA0KDQog
ICAgICAgIEludGVybmFsIEFOIGVycm9ycyBtYXkgY2F1c2UgdGhlIEFOQ1AgYWRqYWNlbmN5IHRv
IGJlIGxvc3Qgd2l0aG91dCBhIA0KICAgICAgICBoYXJkIHJlc2V0IG9mIHRoZSBBTiBhbmQgYXNz
b2NpYXRlZCBsb3NzIG9mIGxpbmUgc3RhdGUgaW4gdGhlIEFOIA0KICAgICAgICBjb250cm9sIHBs
YW5lLiBUaGlzIG1heSBiZSBkdWUgdG8gYSBzaW1pbGFyIGNvbnRyb2wgYW5kIGRhdGEgcGxhbmUg
DQogICAgICAgIHNlcGFyYXRpb24gaW4gdGhlIEFOLCBvciBlLmcuIGR1ZSB0byBmYWlsdXJlIG9m
IGFuIEFOIHVwbGluay4gDQogICAgICAgIEZ1cnRoZXJtb3JlLCBhIGZhaWx1cmUgb3IgcGFja2V0
IGxvc3Mgb24gYW55IGludGVybWVkaWF0ZSBub2RlIG9yIA0KICAgICAgICBuZXR3b3JrIGJldHdl
ZW4gdGhlIEFOIGFuZCB0aGUgTkFTIGNhbiBjYXVzZSB0aGUgQU5DUCBhZGphY2VuY3kgdG8gYmUg
DQogICAgICAgIGxvc3QuIA0KDQogICAgICAgIEFsbCBvZiB0aGUgYWJvdmUgd2lsbCBjYXVzZSB0
aGUgQU5DUCBhZGphY2VuY3kgdG8gYmUgcmVzZXQuIEhvd2V2ZXIsIA0KICAgICAgICB0aGUgcGFy
YW1ldGVycyBsZWFybnQgdmlhIEFOQ1AgcHJpb3IgdG8gcmVzdGFydCBhbmQgYXBwbGllZCB0byAN
CiAgICAgICAgY29udHJvbCB0aGUgZm9yd2FyZGluZyBiZWhhdmlvciBhcmUgc3RpbGwgYXBwbGlj
YWJsZSBhbmQgaW4gcGxheSANCiAgICAgICAgZHVyaW5nIGFuZCBhZnRlciB0aGUgY29udHJvbCBw
bGFuZSByZXN0YXJ0LiANCg0KICAgICAgICBUaGlzIGRyYWZ0IHByb3Bvc2VzIGV4dGVuc2lvbnMg
dG8gQU5DUCB0byBpbXBsZW1lbnQgYSBncmFjZWZ1bCBzdGF0ZSANCiAgICAgICAgcmVzeW5jaHJv
bml6YXRpb24gYmV0d2VlbiB0aGUgTkFTIGFuZCB0aGUgQU4gdXBvbiBjb250cm9sIHBsYW5lIA0K
ICAgICAgICByZXN0YXJ0LiBUaGlzIG1lY2hhbmlzbSBlbnN1cmVzIHRoYXQgdGhlIGNvbnRyb2wg
cGxhbmUgcmVzdGFydCBhbmQgDQogICAgICAgIHN1YnNlcXVlbnQgc3RhdGUgcmVzeW5jaHJvbml6
YXRpb24gaGF2ZSBubyBpbXBhY3Qgb24gdGhlIGZvcndhcmRpbmcgDQogICAgICAgIGFuZCBRT1Mg
Y29udHJvbCBvbiB0aGUgTkFTLiANCg0KICAgICAgICBUaGUgZGVmYXVsdCBiZWhhdmlvciBvbiBh
IGxvc3Mgb2YgQU5DUCBhZGphY2VuY3kgd2l0aG91dCBncmFjZWZ1bCANCiAgICAgICAgcmVzdGFy
dCBleHRlbnNpb25zIGlzIHRvIGNsZWFudXAgYW55IGR5bmFtaWMgaW5mb3JtYXRpb24gbGVhcm50
IGZyb20gDQogICAgICAgIHRoZSBBTkNQIG5laWdoYm9yLCBhbmQgcmV2ZXJ0IHRvIGRlZmF1bHQg
dmFsdWVzIGZvciBhbnkgc3VjaCANCiAgICAgICAgaW5mb3JtYXRpb24uICANCg0KICAgICAgICAg
DQogICAgIDMgIEdyYWNlZnVsIFJlc3RhcnQgTWVjaGFuaXNtIA0KDQogICAgICAgIFdoZW4gdGhl
IGNvbnRyb2wgcGxhbmUgb24gZWl0aGVyIHRoZSBOQVMgb3IgQU4gcmVzdGFydHMsIHRoZSBzdGF0
ZSANCiAgICAgICAgaW5mb3JtYXRpb24gYmV0d2VlbiB0aGUgTkFTIGFuZCBBTiBuZWVkcyB0byBy
ZS1zeW5jaHJvbml6ZWQuIFRoaXMgDQogICAgICAgIGluY2x1ZGVzIHBvdGVudGlhbGx5IHVwZGF0
aW5nIGV4aXN0aW5nIHN0YXRlIG9uIHRoZSByZXN0YXJ0aW5nIGVudGl0eSANCiAgICAgICAgdG8g
dGhlIGxhdGVzdCBpbmZvcm1hdGlvbiBhcyBrbm93biB0byB0aGUgQU5DUCBuZWlnaGJvciBvcmln
aW5hdGluZyANCiAgICAgIA0KICAgICAgDQogICAgIFdhZGh3YSBldC5hbCAgICAgICAgICAgRXhw
aXJlcyBKYW51YXJ5IDQsIDIwMDcgICAgICAgICAgICAgICAgIFtQYWdlIDRdIA0KICAgICAgICAg
DQoMICAgICBJbnRlcm5ldC1EcmFmdCAgICAgIGRyYWZ0LXdhZGh3YS1hbmNwLWdyYWNlZnVsLXJl
c3RhcnQtMDAgICAgICAgIEp1bHkgMjAwNiANCiAgICAgICAgIA0KDQogICAgICAgIHRoaXMgaW5m
b3JtYXRpb24uIEFueSBzdGF0ZSBpbmZvcm1hdGlvbiBvbiB0aGUgcmVzdGFydGluZyBlbnRpdHkg
DQogICAgICAgIGxlYXJudCBmcm9tIGl0cyBBTkNQIG5laWdoYm9yIHByaW9yIHRvIHJlc3RhcnQg
dGhhdCBpcyBubyBsb25nZXIgDQogICAgICAgIGFwcGxpY2FibGUgYWZ0ZXIgdGhlIHJlc3RhcnQg
bmVlZHMgdG8gYmUgZ2FyYmFnZS1jb2xsZWN0ZWQuIFJlc291cmNlcyANCiAgICAgICAgYXNzb2Np
YXRlZCB3aXRoIHN1Y2ggc3RhdGUgbmVlZHMgdG8gYmUgcmVjbGFpbWVkLiAgDQoNCiAgICAgICAg
VGhlIEFOQ1AgbmVpZ2hib3Igc3VwcG9ydGluZyBncmFjZWZ1bCByZXN0YXJ0IFNIT1VMRCBtYWlu
dGFpbiBhbmQgdXNlIA0KICAgICAgICBzdGF0ZSBsZWFybnQgZnJvbSB0aGUgcmVzdGFydGluZyBu
ZWlnaGJvciB0aWxsIHRoZSByZXN0YXJ0IGlzIA0KICAgICAgICBjb21wbGV0ZSBhbmQgdGhlIHN0
YXRlIGhhcyBiZWVuIHJlc3luY2hyb25pemVkLiBIb3dldmVyLCB0aGUgZHVyYXRpb24gDQogICAg
ICAgIGZvciB3aGljaCB0aGlzIHN0YXRlIFNIT1VMRCBiZSBtYWludGFpbmVkIG9uIHRoZSBBTkNQ
IG5laWdoYm9yIGFmdGVyIA0KICAgICAgICB0aGUgQU5DUCBhZGphY2VuY3kgYmV0d2VlbiB0aGUg
cmVzdGFydGluZyBlbnRpdHkgYW5kIHRoZSBBTkNQIA0KICAgICAgICBuZWlnaGJvciBpcyBsb3N0
IGlzIGNvbnRyb2xsZWQgYnkgdGhlIHJlc3RhcnRpbmcgbmVpZ2hib3IuIFRoZSANCiAgICAgICAg
cmVzdGFydGluZyBuZWlnaGJvciBTSE9VTEQgYWR2ZXJ0aXNlIHRoZSBkdXJhdGlvbiBpbiBzZWNv
bmRzIGluIGl0cyANCiAgICAgICAgZ3JhY2VmdWwgcmVzdGFydCBjYXBhYmlsaXR5IGFubm91bmNl
bWVudC4gVGhpcyBkdXJhdGlvbiBpcyByZWZlcnJlZCANCiAgICAgICAgdG8gYXMgInJlc3RhcnRp
bmcgdGltZSIgYW5kIHNpZ25pZmllcyB0aGUgYW1vdW50IG9mIHRpbWUgYW4gQU5DUCANCiAgICAg
ICAgbmVpZ2hib3Igc2hvdWxkIHdhaXQgZm9yIHNlc3Npb24gcmUtZXN0YWJsaXNobWVudCBhbmQg
c3RhdGUgcmUtDQogICAgICAgIHN5bmNocm9uaXphdGlvbiB3aXRoIHRoZSByZXN0YXJ0aW5nIGVu
dGl0eSBhZnRlciB0aGUgQU5DUCBhZGphY2VuY3kgDQogICAgICAgIGhhcyB0aW1lZCBvdXQuIFRo
ZSByZXN0YXJ0aW5nIHRpbWUgYWR2ZXJ0aXNlZCBieSB0aGUgcmVzdGFydGluZyANCiAgICAgICAg
ZW50aXR5IFNIT1VMRCBiZSBjb25maWd1cmFibGUuICANCg0KICAgICAgICAgDQoNCiAgICAgNCAg
R3JhY2VmdWwgUmVzdGFydCBQcm9jZWR1cmVzIA0KDQogICAgIDQuMSBSZXN0YXJ0aW5nIEVsZW1l
bnQgDQoNCiAgICAgICAgVHlwaWNhbGx5LCBBTkNQIHJlc3RhcnRpbmcgZWxlbWVudCBzdXBwb3J0
aW5nIGNvbnRyb2wgcGxhbmUgZ3JhY2VmdWwgDQogICAgICAgIHJlc3RhcnQgd2lsbCB1c2UgdGhl
IHN0YXRlIGxlYXJudCBmcm9tIGl0cyBBTkNQIG5laWdoYm9yIGluIHRoZSANCiAgICAgICAgZm9y
d2FyZGluZyBwbGFuZSBkdXJpbmcgYW5kIGFmdGVyIHRoZSByZXN0YXJ0LiBJbW1lZGlhdGVseSBh
ZnRlciANCiAgICAgICAgcmVzdGFydCB0aGUgcmVzdGFydGluZyBlbGVtZW50IFNIT1VMRCBtYXJr
IGFsbCB0aGUgc3RhdGUgbGVhcm50IHByaW9yIA0KICAgICAgICB0byBpdHMgcmVzdGFydCBmcm9t
IGl0cyBBTkNQIG5laWdoYm9yIGFzICJzdGFsZSIuIE9uIHJlLWVzdGFibGlzaGluZyANCiAgICAg
ICAgQU5DUCBhZGphY2VuY3kgd2l0aCBlYWNoIG9mIGl0cyBBTkNQIG5laWdoYm9ycyAoZS5nLiBz
aW5nbGUgTkFTIGNhbiANCiAgICAgICAgaGF2ZSBtdWx0aXBsZSBBTkNQIGFkamFjZW5jaWVzIGFz
IGl0IGNhbiBzZXJ2ZSBtdWx0aXBsZSBwYXJ0aXRpb25zIG9uIA0KICAgICAgICBhbiBBTiBvciBt
dWx0aXBsZSBwaHlzaWNhbCBBTnMpLCB0aGUgcmVzdGFydGluZyBlbGVtZW50IHdpbGwgcmVsZWFy
biANCiAgICAgICAgc3RhdGUgZnJvbSBpdHMgbmVpZ2hib3JzLiBUaGUgcmVzdGFydGluZyBlbGVt
ZW50IFNIT1VMRCB1cGRhdGUgdGhlIA0KICAgICAgICBsZWFybnQgc3RhdGUgYW5kIFNIT1VMRCB1
bm1hcmsgdGhlIHN0YXRlIGFzIGJlaW5nIHN0YWxlLiBFYWNoIEFOQ1AgDQogICAgICAgIG5laWdo
Ym9yIFNIT1VMRCBnZW5lcmF0ZSBhbiAiRU5ELU9GLVNUQVRFIiBhZGphY2VuY3kgbWVzc2FnZSBh
cyBzb29uIA0KICAgICAgICBhcyBhbGwgZXhpc3RpbmcgaW5mb3JtYXRpb24gb24gdGhlIEFOQ1Ag
bmVpZ2hib3IgaGFzIGJlZW4gcmVwbGF5ZWQgdG8gDQogICAgICAgIHRoZSByZXN0YXJ0aW5nIGVu
dGl0eS4gV2hlbiB0aGUgcmVzdGFydGluZyBlbnRpdHkgaGFzIHJlY2VpdmVkICJFTkQtDQogICAg
ICAgIE9GLVNUQVRFIiBmcm9tIGFuIEFOQ1AgbmVpZ2hib3IsIGl0IHNob3VsZCByZW1vdmUgYW55
IHN0YWxlIHN0YXRlIA0KICAgICAgICB0aGF0IGlzIHJlbGV2YW50IHRvIHRoYXQgbmVpZ2hib3Is
IGZyb20gYm90aCBpdHMgY29udHJvbCBhbmQgDQogICAgICAgIGZvcndhcmRpbmcgcGxhbmVzLCBh
bmQgU0hPVUxEIHJlY2xhaW0gdGhlIGFzc29jaWF0ZWQgcmVzb3VyY2VzLiBUaGUgDQogICAgICAg
IHJlc3RhcnRpbmcgZWxlbWVudCBTSE9VTEQga2VlcCB0cmFjayBvZiBpdHMgZXN0YWJsaXNoZWQg
YWRqYWNlbmNpZXMgDQogICAgICAgIGluIG5vbi12b2xhdGlsZSBzdG9yYWdlIHByaW9yIHRvIHJl
c3RhcnQuIEl0IFNIT1VMRCBhbHNvIG5vdGUgdGhlIA0KICAgICAgICBncmFjZWZ1bCByZXN0YXJ0
IGNhcGFiaWxpdHkgb2YgZWFjaCBlc3RhYmxpc2hlZCBhZGphY2VuY3kuIFRoZSANCiAgICAgICAg
cmVzdGFydCBpcyBkZWVtZWQgY29tcGxldGUgd2hlbiB0aGUgcmVzdGFydGluZyBlbGVtZW50IGhh
cyByZWNlaXZlZCANCiAgICAgICAgYW5kIGhhbmRsZWQgk0VORC1PRi1TVEFURZQgZnJvbSBlYWNo
IG9mIHRoZXNlIGFkamFjZW5jaWVzLiANCg0KICAgICAgDQogICAgICANCiAgICAgV2FkaHdhIGV0
LmFsICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgNCwgMjAwNyAgICAgICAgICAgICAgICAgW1Bh
Z2UgNV0gDQogICAgICAgICANCgwgICAgIEludGVybmV0LURyYWZ0ICAgICAgZHJhZnQtd2FkaHdh
LWFuY3AtZ3JhY2VmdWwtcmVzdGFydC0wMCAgICAgICAgSnVseSAyMDA2IA0KICAgICAgICAgDQoN
CiAgICAgICAgVGhlIHJlc3RhcnRpbmcgZWxlbWVudCBTSE9VTEQgd2FpdCBmb3Igc2Vzc2lvbiBy
ZS1lc3RhYmxpc2htZW50IGFuZCANCiAgICAgICAgc3RhdGUgcmUtc3luY2hyb25pemF0aW9uIGZy
b20gdGhlc2UgYWRqYWNlbmNpZXMgdXAgdG8gYSBtYXhpbXVtIA0KICAgICAgICBkdXJhdGlvbi4g
VGhpcyBkdXJhdGlvbiBpcyByZWZlcnJlZCB0byBhcyAid2FpdCB0aW1lIi4gQW4gYWJzb2x1dGUg
DQogICAgICAgIHZhbHVlIGZvciB3YWl0IHRpbWUgaW4gc2Vjb25kcyBTSE9VTEQgYmUgY29uZmln
dXJhYmxlIG9uIHRoZSANCiAgICAgICAgcmVzdGFydGluZyBlbGVtZW50LiBBdCB0aGUgZXhwaXJ5
IG9mIJN3YWl0IHRpbWWULCB0aGUgcmVzdGFydGluZyANCiAgICAgICAgZWxlbWVudCBTSE9VTEQg
cmVtb3ZlIGFsbCBzdGF0ZSB0aGF0IGlzIHN0aWxsIG1hcmtlZCBzdGFsZS4gQWxzbywgYXQgDQog
ICAgICAgIHRoZSBleHBpcnkgb2Ygk3dhaXQgdGltZZQsIGdyYWNlZnVsIHJlc3RhcnQgZm9yIGFu
eSBwYXJ0aWFsbHkgDQogICAgICAgIHN5bmNocm9uaXplZCBhZGphY2VuY2llcyBTSE9VTEQgYmUg
YWJvcnRlZC4gQWxsIHRoZSBzdGF0ZSBmb3IgDQogICAgICAgIHBhcnRpYWxseSBzeW5jaHJvbml6
ZWQgYWRqYWNlbmNpZXMgU0hPVUxEIGJlIHJlbW92ZWQsIGFuZCB0aGVzZSANCiAgICAgICAgYWRq
YWNlbmNpZXMgU0hPVUxEIGJlIHJlaW5pdGlhbGl6ZWQuICANCg0KICAgICAgICBBbGwgQU5DUCBl
bGVtZW50cyBjYXBhYmxlIG9mIHJlc3RhcnRpbmcgZ3JhY2VmdWxseSBTSE9VTEQgYWR2ZXJ0aXNl
IA0KICAgICAgICAiR3JhY2VmdWwgUmVzdGFydCIgY2FwYWJpbGl0eSBUTFYgaW4gaXRzIGFkamFj
ZW5jeSBtZXNzYWdlcy4gVGhlIA0KICAgICAgICBjYXBhYmlsaXR5IFNIT1VMRCBhbHNvIGNvbnRh
aW4gYSBzdWdnZXN0ZWQgdmFsdWUgZm9yIHRoZSAicmVzdGFydCANCiAgICAgICAgdGltZSIuIEdl
bmVyYWwgZm9ybWF0IGZvciBhIGNhcGFiaWxpdHkgVExWIGFuZCBnZW5lcmFsIGhhbmRsaW5nIG9m
IA0KICAgICAgICBBTkNQIGNhcGFiaWxpdHkgVExWcyBpcyBkZWZpbmVkIGluIFsxXS4gVGhlICJH
cmFjZWZ1bCBSZXN0YXJ0IiANCiAgICAgICAgY2FwYWJpbGl0eSBpcyBkZWZpbmVkIGFzIGZvbGxv
d3MuIA0KDQogICAgICAgIENhcGFiaWxpdHkgVHlwZTogR3JhY2VmdWwgUmVzdGFydCA9IDB4MDUg
DQoNCiAgICAgICAgTGVuZ3RoIChpbiBieXRlcyk6IDQgIA0KDQogICAgICAgIENhcGFiaWxpdHkg
RGF0YTogUmVzdGFydCBUaW1lIChpbiBzZWNvbmRzKSANCg0KICAgICAgICAgDQoNCiAgICAgNC4y
IEFOQ1AgTmVpZ2hib3Igb2YgUmVzdGFydGluZyBFbGVtZW50IA0KDQogICAgICAgIEFuIEFOQ1Ag
ZWxlbWVudCBjYXBhYmxlIG9mIHN1cHBvcnRpbmcgZ3JhY2VmdWwgcmVzdGFydCBvZiBhIA0KICAg
ICAgICByZXN0YXJ0aW5nIGVsZW1lbnQgU0hPVUxEIG1haW50YWluIGFuZCB1c2UgaW5mb3JtYXRp
b24gbGVhcm50IGZyb20gYW4gDQogICAgICAgIEFOQ1AgbmVpZ2hib3IgdGhhdCBoYXMgYWR2ZXJ0
aXNlZCAiR3JhY2VmdWwgUmVzdGFydCBDYXBhYmlsaXR5IiwgZXZlbiANCiAgICAgICAgYWZ0ZXIg
dGhlIEFOQ1AgYWRqYWNlbmN5IHdpdGggdGhlIG5laWdoYm9yIGhhcyBiZWVuIGxvc3QuIFRoZSAN
CiAgICAgICAgaW5mb3JtYXRpb24gU0hPVUxEIGJlIHVzZWQgYW5kIG1haW50YWluZWQgYmV5b25k
IGFkamFjZW5jeSBsb3NzLCBvbmx5IA0KICAgICAgICB1cCB0byB0aGUgInJlc3RhcnQgdGltZSIg
YWR2ZXJ0aXNlZCBpbiB0aGUgIkdyYWNlZnVsIFJlc3RhcnQiIA0KICAgICAgICBjYXBhYmlsaXR5
IFRMVi4gT24gZXhwaXJ5IG9mIHRoaXMgdGltZSwgYW55IHN0YXRlIGxlYXJudCBmcm9tIHRoZSAN
CiAgICAgICAgQU5DUCBuZWlnaGJvciBTSE9VTEQgYmUgcmVtb3ZlZC4gVGhpcyBTSE9VTEQgcmVz
dWx0IGluIHJldmVydGluZyB0byANCiAgICAgICAgZGVmYXVsdCB2YWx1ZXMgYW55IHN0YXRlIGNy
ZWF0ZWQgYXMgYSByZXN1bHQgb2YgaW5mb3JtYXRpb24gYW5ub3VuY2VkIA0KICAgICAgICBieSB0
aGUgQU5DUCBuZWlnaGJvci4gDQoNCiAgICAgICAgQW4gQU5DUCBlbGVtZW50IGNhcGFibGUgb2Yg
c3VwcG9ydGluZyBncmFjZWZ1bCByZXN0YXJ0IG9mIGEgDQogICAgICAgIHJlc3RhcnRpbmcgZWxl
bWVudCBTSE9VTEQgZ2VuZXJhdGUgYW4gYWRqYWNlbmN5IG1lc3NhZ2Ugd2l0aCBjb2RlIA0KICAg
ICAgICB0eXBlICJFTkQtT0YtU1RBVEUiIGFmdGVyIGFsbCByZWxldmFudCBleGlzdGluZyBpbmZv
cm1hdGlvbiBoYXMgYmVlbiANCiAgICAgICAgcmVwbGF5ZWQgdG8gdGhlIHJlc3RhcnRpbmcgZWxl
bWVudC4gVGhlIGNvZGUgZmllbGQgaW4gdGhlIGFkamFjZW5jeSANCiAgICAgICAgbWVzc2FnZSBh
cyBkZWZpbmVkIGluIHNlY3Rpb24gNS4zIG9mIFsxXSBpcyBiZWluZyBleHBhbmRlZCB0byBpbmNs
dWRlIA0KICAgICAgICBFTkQtT0YtU1RBVEUgKDUpIGFzIGEgbmV3IHR5cGUuIFRoZSBhZGphY2Vu
Y3kgbWVzc2FnZSBmb3JtYXQgYXMgDQogICAgICAgIGRlZmluZWQgaW4gWzFdIGlzIGFzIGZvbGxv
d3MuIA0KDQogICAgICANCiAgICAgIA0KICAgICBXYWRod2EgZXQuYWwgICAgICAgICAgIEV4cGly
ZXMgSmFudWFyeSA0LCAyMDA3ICAgICAgICAgICAgICAgICBbUGFnZSA2XSANCiAgICAgICAgIA0K
DCAgICAgSW50ZXJuZXQtRHJhZnQgICAgICBkcmFmdC13YWRod2EtYW5jcC1ncmFjZWZ1bC1yZXN0
YXJ0LTAwICAgICAgICBKdWx5IDIwMDYgDQogICAgICAgICANCg0KICAgICAgICAgDQoNCiAgICAg
ICAgIA0KDQogICAgICAgICAgICANCg0KICAgICAgICAgICAgIA0KDQogICAgICAgICAgDQoNCiAg
ICAgICAgIA0KDQogICAgICAgICAgICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAgICAgICAg
ICAgICAgMiAgICAgICAgICAgICAgICAgICAzIA0KICAgICAgICAgICAgMCAxIDIgMyA0IDUgNiA3
IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIA0KICAgICAg
ICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKyANCiAgICAgICAgICAgfCAgIFZlciB8ICBTdWIgIHwgTWVzc2FnZSBUeXBl
ICB8ICAgICBUaW1lciAgICAgfE18ICAgICBDb2RlICAgIHwgDQogICAgICAgICAgICstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
IA0KICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICBTZW5kZXIgTmFtZSAgICAg
ICAgICAgICAgICAgICAgICAgICAgfCANCiAgICAgICAgICAgKyAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICAgICAgICAg
IHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICB8IA0KICAgICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKyANCiAgICAgICAgICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgICBSZWNlaXZlciBOYW1lICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQog
ICAgICAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rIA0KICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAg
ICBTZW5kZXIgUG9ydCAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgICAgICAgICAgKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSsgDQogICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgUmVjZWl2ZXIgUG9y
dCAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgICAg
ICAgICAgfCBQVHlwZSB8IFBGbGFnIHwgICAgICAgICAgICAgICBTZW5kZXIgSW5zdGFuY2UgICAg
ICAgICAgICAgICAgIHwgDQogICAgICAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgICAgICAgICB8IFBhcnRp
dGlvbiBJRCAgfCAgICAgICAgICAgICAgUmVjZWl2ZXIgSW5zdGFuY2UgICAgICAgICAgICAgICAg
fCANCiAgICAgICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICAgICAgICAgIHwgVGVjaCBUeXBlICAgICB8ICMg
b2YgVExWcyAgICAgfCBUb3RhbCBMZW5ndGggICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAg
ICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKyANCiAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICAgIH4gICAgICAgICAg
ICAgICAgICAgQ2FwYWJpbGl0eSBUTFZzICAgICAgICAgICAgICAgICAgICAgICAgICAgICB+IA0K
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCANCiAgICAgICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICAgICAgICAgICAN
Cg0KICAgICAgICBUaGUgY29kZSBmaWVsZCBzcGVjaWZpZXMgdGhlIGZ1bmN0aW9uIG9mIHRoZSBt
ZXNzYWdlLiBXaXRoIHRoZSANCiAgICAgICAgZXhwYW5zaW9uIG9mIHRoZSBjb2RlcywgdGhlIHNl
dCBvZiBjb2RlcyB0aGF0IGNhbiBiZSBzZW50IGluIA0KICAgICAgICBhZGphY2VuY3kgbWVzc2Fn
ZXMgYXJlIGFzIGZvbGxvd3M6IA0KDQogICAgICAgIFNZTjogICAgICAgICAgQ29kZSA9IDEgDQoN
CiAgICAgICAgU1lOQUNLOiAgICAgICBDb2RlID0gMiANCg0KICAgICAgDQogICAgICANCiAgICAg
V2FkaHdhIGV0LmFsICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgNCwgMjAwNyAgICAgICAgICAg
ICAgICAgW1BhZ2UgN10gDQogICAgICAgICANCgwgICAgIEludGVybmV0LURyYWZ0ICAgICAgZHJh
ZnQtd2FkaHdhLWFuY3AtZ3JhY2VmdWwtcmVzdGFydC0wMCAgICAgICAgSnVseSAyMDA2IA0KICAg
ICAgICAgDQoNCiAgICAgICAgQUNLOiAgICAgICAgICBDb2RlID0gMyANCg0KICAgICAgICBSU1RB
Q0s6ICAgICAgIENvZGUgPSA0IA0KDQogICAgICAgIEVORC1PRi1TVEFURTogQ29kZSA9IDUgDQoN
CiAgICAgICAgIA0KDQogICAgICAgIFRoZSCTRU5ELU9GLVNUQVRFlCBub3RpZmljYXRpb24gaXMg
YWxzbyB1c2VmdWwgaWYgdGhlIEFOQ1AgbmVpZ2hib3IgDQogICAgICAgIHdhbnRzIHRvIHBlcmZv
cm0gYSBub24tZGlzcnVwdGl2ZSwgZm9yY2VkIHN0YXRlIHJlc3luY2hyb25pemF0aW9uIA0KICAg
ICAgICBvcGVyYXRpb24gd2l0aG91dCBicmluZ2luZyBkb3duIHRoZSBBTkNQIGFkamFjZW5jeS4g
IA0KDQogICAgICAgIEFuIEFOQ1AgZWxlbWVudCBjYXBhYmxlIG9mIHN1cHBvcnRpbmcgZ3JhY2Vm
dWwgcmVzdGFydCBvZiBhIA0KICAgICAgICByZXN0YXJ0aW5nIG5laWdoYm9yIFNIT1VMRCBhZHZl
cnRpc2UgIkdyYWNlZnVsIFJlc3RhcnQgSGVscGVyIiANCiAgICAgICAgY2FwYWJpbGl0eSBUTFYg
aW4gaXRzIGFkamFjZW5jeSBtZXNzYWdlcy4gVGhpcyBjYXBhYmlsaXR5IFRMViBpcyANCiAgICAg
ICAgZGVmaW5lZCBhcyBmb2xsb3dzOiAgDQoNCiAgICAgICAgQ2FwYWJpbGl0eSBUeXBlIDogR3Jh
Y2VmdWwgUmVzdGFydCBIZWxwZXIgPSAweDA2ICAgICAgICAgICAgICAgICANCg0KICAgICAgICBM
ZW5ndGggKGluIGJ5dGVzKSA6IDAgDQoNCiAgICAgICAgQ2FwYWJpbGl0eSBEYXRhIDogTlVMTCAN
Cg0KICAgICAgICBBbiBBTkNQIGVsZW1lbnQgY2FuIGJlIGEgk2dyYWNlZnVsIHJlc3RhcnQgaGVs
cGVylCB3aXRob3V0IGl0c2VsZiANCiAgICAgICAgYmVpbmcgZ3JhY2VmdWwgcmVzdGFydCBjYXBh
YmxlIGFuZCB2aWNlLXZlcnNhLiBUaGUgbm9ybWFsIEFOQ1AgDQogICAgICAgIGFkamFjZW5jeSBu
ZWdvdGlhdGlvbiBtZWNoYW5pc20gd2hpY2ggcmVzdWx0cyBpbiBuZWdvdGlhdGlvbiBvZiBsZWFz
dCANCiAgICAgICAgY29tbW9uIGNhcGFiaWxpdHkgc2V0IGlzIHJlbGF4ZWQgZm9yIGdyYWNlZnVs
IHJlc3RhcnQsIHNpbmNlIHRoZSANCiAgICAgICAgZ3JhY2VmdWwgcmVzdGFydCBwcm9jZWR1cmVz
IGNhbiBoYW5kbGUgYXN5bW1ldHJpYyBncmFjZWZ1bCByZXN0YXJ0IA0KICAgICAgICBjYXBhYmls
aXRpZXMuIA0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICANCg0KICAgICA1ICBJQU5BIENvbnNpZGVyYXRpb25zIA0K
DQogICAgICAgIE5ldyBjYXBhYmlsaXR5IHR5cGVzLCBhbmQgY29kZSB0eXBlIGZvciBhZGphY2Vu
Y3kgbWVzc2FnZSB3aWxsIG5lZWQgDQogICAgICAgIHRvIGJlIHJlc2VydmVkLiANCg0KICAgICA2
ICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyANCg0KICAgICAgICBUaGVzZSBleHRlbnNpb25zIGZv
ciBncmFjZWZ1bCByZXN0YXJ0IGRvIG5vdCByZXF1aXJlIGFueSBhZGRpdGlvbmFsIA0KICAgICAg
ICBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBiZXlvbmQgZ2VuZXJhbCBzZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBmb3IgDQogICAgICAgIEFOQ1AgYXMgc3BlY2lmaWVkIGluIFsxXS4gICANCg0KICAg
ICA3ICBSZWZlcmVuY2VzIA0KDQogICAgICAgIFsxXSAgIFdhZGh3YSBTLiBldCBhbCwgk0dTTVAg
ZXh0ZW5zaW9ucyBmb3IgTDJDlCwgZHJhZnQtd2FkaHdhLWdzbXAtDQogICAgICAgICAgICAgIDJj
b250cm9sLWNvbmZpZ3VyYXRpb24tMDEudHh0LCBNYXJjaCwgMjAwNi4gDQogICAgICANCiAgICAg
IA0KICAgICBXYWRod2EgZXQuYWwgICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSA0LCAyMDA3ICAg
ICAgICAgICAgICAgICBbUGFnZSA4XSANCiAgICAgICAgIA0KDCAgICAgSW50ZXJuZXQtRHJhZnQg
ICAgICBkcmFmdC13YWRod2EtYW5jcC1ncmFjZWZ1bC1yZXN0YXJ0LTAwICAgICAgICBKdWx5IDIw
MDYgDQogICAgICAgICANCg0KICAgICAgICAgDQoNCiAgICAgQXV0aG9yJ3MgQWRkcmVzc2VzIA0K
DQogICAgICAgIFNhbmpheSBXYWRod2EgIA0KICAgICAgICBKdW5pcGVyIE5ldHdvcmtzIA0KICAg
ICAgICAxMCBUZWNobm9sb2d5IFBhcmsgRHJpdmUgDQogICAgICAgIFdlc3Rmb3JkLCBNQSAwMTg4
NiANCiAgICAgICAgIA0KICAgICAgICBFbWFpbDogc3dhZGh3YUBqdW5pcGVyLm5ldCANCiAgICAg
ICAgIA0KICAgICAgICBEZXJlayBIYXJrbmVzcyANCiAgICAgICAgSnVuaXBlciBOZXR3b3JrcyAN
CiAgICAgICAgIA0KICAgICAgICBFbWFpbDogZGhhcmtuZXNzQGp1bmlwZXIubmV0IA0KICAgICAg
ICAgICAgDQogICAgICAgICANCiAgICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVudCAN
Cg0KICAgICAgICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZhbGlk
aXR5IG9yIHNjb3BlIG9mIGFueSANCiAgICAgICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0
cyBvciBvdGhlciByaWdodHMgdGhhdCBtaWdodCBiZSBjbGFpbWVkIHRvIA0KICAgICAgICBwZXJ0
YWluIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciB1c2Ugb2YgdGhlIHRlY2hub2xvZ3kgZGVzY3Jp
YmVkIGluIA0KICAgICAgICB0aGlzIGRvY3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55
IGxpY2Vuc2UgdW5kZXIgc3VjaCByaWdodHMgDQogICAgICAgIG1pZ2h0IG9yIG1pZ2h0IG5vdCBi
ZSBhdmFpbGFibGU7IG5vciBkb2VzIGl0IHJlcHJlc2VudCB0aGF0IGl0IGhhcyANCiAgICAgICAg
bWFkZSBhbnkgaW5kZXBlbmRlbnQgZWZmb3J0IHRvIGlkZW50aWZ5IGFueSBzdWNoIHJpZ2h0cy4g
IEluZm9ybWF0aW9uIA0KICAgICAgICBvbiB0aGUgcHJvY2VkdXJlcyB3aXRoIHJlc3BlY3QgdG8g
cmlnaHRzIGluIFJGQyBkb2N1bWVudHMgY2FuIGJlIA0KICAgICAgICBmb3VuZCBpbiBCQ1AgNzgg
YW5kIEJDUCA3OS4gDQoNCiAgICAgICAgQ29waWVzIG9mIElQUiBkaXNjbG9zdXJlcyBtYWRlIHRv
IHRoZSBJRVRGIFNlY3JldGFyaWF0IGFuZCBhbnkgDQogICAgICAgIGFzc3VyYW5jZXMgb2YgbGlj
ZW5zZXMgdG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4gDQogICAgICAg
IGF0dGVtcHQgbWFkZSB0byBvYnRhaW4gYSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVybWlzc2lvbiBm
b3IgdGhlIHVzZSBvZiANCiAgICAgICAgc3VjaCBwcm9wcmlldGFyeSByaWdodHMgYnkgaW1wbGVt
ZW50ZXJzIG9yIHVzZXJzIG9mIHRoaXMgDQogICAgICAgIHNwZWNpZmljYXRpb24gY2FuIGJlIG9i
dGFpbmVkIGZyb20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSBhdCANCiAgICAgICAg
aHR0cDovL3d3dy5pZXRmLm9yZy9pcHIuIA0KDQogICAgICAgIFRoZSBJRVRGIGludml0ZXMgYW55
IGludGVyZXN0ZWQgcGFydHkgdG8gYnJpbmcgdG8gaXRzIGF0dGVudGlvbiBhbnkgDQogICAgICAg
IGNvcHlyaWdodHMsIHBhdGVudHMgb3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3RoZXIgcHJv
cHJpZXRhcnkgDQogICAgICAgIHJpZ2h0cyB0aGF0IG1heSBjb3ZlciB0ZWNobm9sb2d5IHRoYXQg
bWF5IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVudCANCiAgICAgICAgdGhpcyBzdGFuZGFyZC4gIFBs
ZWFzZSBhZGRyZXNzIHRoZSBpbmZvcm1hdGlvbiB0byB0aGUgSUVURiBhdCANCiAgICAgICAgaWV0
Zi1pcHJAaWV0Zi5vcmcgDQoNCiAgICAgRGlzY2xhaW1lciBvZiBWYWxpZGl0eSANCg0KICAgICAg
ICBUaGlzIGRvY3VtZW50IGFuZCB0aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGhlcmVpbiBhcmUg
cHJvdmlkZWQgb24gYW4gDQogICAgICAgICJBUyBJUyIgYmFzaXMgYW5kIFRIRSBDT05UUklCVVRP
UiwgVEhFIE9SR0FOSVpBVElPTiBIRS9TSEUgUkVQUkVTRU5UUyANCiAgICAgICAgT1IgSVMgU1BP
TlNPUkVEIEJZIChJRiBBTlkpLCBUSEUgSU5URVJORVQgU09DSUVUWSBBTkQgVEhFIElOVEVSTkVU
IA0KICAgICAgICBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJSQU5USUVT
LCBFWFBSRVNTIE9SIElNUExJRUQsIA0KICAgICAgDQogICAgICANCiAgICAgV2FkaHdhIGV0LmFs
ICAgICAgICAgICBFeHBpcmVzIEphbnVhcnkgNCwgMjAwNyAgICAgICAgICAgICAgICAgW1BhZ2Ug
OV0gDQogICAgICAgICANCgwgICAgIEludGVybmV0LURyYWZ0ICAgICAgZHJhZnQtd2FkaHdhLWFu
Y3AtZ3JhY2VmdWwtcmVzdGFydC0wMCAgICAgICAgSnVseSAyMDA2IA0KICAgICAgICAgDQoNCiAg
ICAgICAgSU5DTFVESU5HIEJVVCBOT1QgTElNSVRFRCBUTyBBTlkgV0FSUkFOVFkgVEhBVCBUSEUg
VVNFIE9GIFRIRSANCiAgICAgICAgSU5GT1JNQVRJT04gSEVSRUlOIFdJTEwgTk9UIElORlJJTkdF
IEFOWSBSSUdIVFMgT1IgQU5ZIElNUExJRUQgDQogICAgICAgIFdBUlJBTlRJRVMgT0YgTUVSQ0hB
TlRBQklMSVRZIE9SIEZJVE5FU1MgRk9SIEEgUEFSVElDVUxBUiBQVVJQT1NFLiANCg0KICAgICBD
b3B5cmlnaHQgU3RhdGVtZW50IA0KDQogICAgICAgIENvcHlyaWdodCAoQykgVGhlIEludGVybmV0
IFNvY2lldHkgKDIwMDYpLiANCg0KICAgICAgICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8g
dGhlIHJpZ2h0cywgbGljZW5zZXMgYW5kIHJlc3RyaWN0aW9ucyANCiAgICAgICAgY29udGFpbmVk
IGluIEJDUCA3OCwgYW5kIGV4Y2VwdCBhcyBzZXQgZm9ydGggdGhlcmVpbiwgdGhlIGF1dGhvcnMg
DQogICAgICAgIHJldGFpbiBhbGwgdGhlaXIgcmlnaHRzLiANCg0KICAgICBBY2tub3dsZWRnbWVu
dCAgICAgDQoNCiAgICAgICAgIA0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCiAgICAgIA0KICAgICAgDQogICAgIFdhZGh3YSBl
dC5hbCAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDQsIDIwMDcgICAgICAgICAgICAgICAgW1Bh
Z2UgMTBdIA0KICAgICAgICAgDQoM

------_=_NextPart_001_01C6A1BB.C4DB6384
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

------_=_NextPart_001_01C6A1BB.C4DB6384--




From ancp-bounces@ietf.org Wed Jul 12 11:17:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0gTA-0001BZ-Lq; Wed, 12 Jul 2006 11:17:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0gT9-0001BU-TV
	for ancp@ietf.org; Wed, 12 Jul 2006 11:17:43 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0gT7-00024Q-K0
	for ancp@ietf.org; Wed, 12 Jul 2006 11:17:43 -0400
Received: from jurassic.eng.sun.com ([129.146.104.45])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k6CFHeoo012509
	for <ancp@ietf.org>; Wed, 12 Jul 2006 09:17:41 -0600 (MDT)
Received: from [192.9.61.35] (punchin-kais.SFBay.Sun.COM [192.9.61.35])
	by jurassic.eng.sun.com (8.13.6+Sun/8.13.6) with ESMTP id
	k6CFHcfX681608
	for <ancp@ietf.org>; Wed, 12 Jul 2006 08:17:40 -0700 (PDT)
Message-ID: <44B51282.20109@Sun.COM>
Date: Wed, 12 Jul 2006 08:17:22 -0700
From: Kais Belgaied <Kais.Belgaied@Sun.COM>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20060120
X-Accept-Language: ar-eg, en-us, en, ar, ar-dz, ar-bh, ar-iq, ar-jo, ar-kw,
	ar-lb, ar-ly, ar-ma, ar-om, ar-qa, ar-sa, ar-sy, ar-tn, ar-ae,
	ar-ye
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Subject: [ANCP] Question about the ANCP high-level architecture
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Folks,

My question is regarding the following picture of the high level ANCP
architecture:


                                                +--------+
                                                | Policy |
                                                | Server |
                                                +--------+
                                                     |
                                                     |
   +-----+   +-----+   +--------+                 +-----+   +----------+
   | CPE |---| HGW |---|        |                 |     |   |          |
   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
   +-----+   +-----+   +--------+                 +-----+   +----------+


The policy server is attached to the NAS only.

A couple of observations about the AN:
. it is shared between multiple HGWs that don't know/trust each other
. it is the first candidate for enforcing link sharing policies (e.g. bandwidth
  allocation) between subscribers attached to those HGWs

Such policy is applicable to HGWs connected to the same AN.
There may be other policy information still live in the NAS policy server.
The picture could look more like:

                        +--------+              +--------+
                        |   AN   |              |  NAS   |
                        | Policy |              | Policy |
                        | Server |              | Server |
                        +--------+              +--------+
                            |                        |
                            |                        |
   +-----+   +-----+   +--------+                 +-----+   +----------+
   | CPE |---| HGW |---|        |                 |     |   |          |
   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
   +-----+   +-----+   +--------+                 +-----+   +----------+

comments?


	Kais


_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Wed Jul 12 11:32:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0ghr-0006l3-DZ; Wed, 12 Jul 2006 11:32:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0ghq-0006km-Hh
	for ancp@ietf.org; Wed, 12 Jul 2006 11:32:54 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0ghp-0002eP-0j
	for ancp@ietf.org; Wed, 12 Jul 2006 11:32:54 -0400
Received: from bemail06.netfr.alcatel.fr (bemail06.netfr.alcatel.fr
	[155.132.251.30])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k6CFWqQJ009677; Wed, 12 Jul 2006 17:32:52 +0200
Received: from [172.17.253.64] ([172.17.253.64])
	by bemail06.netfr.alcatel.fr (Lotus Domino Release 5.0.13aHF163)
	with ESMTP id 2006071217324991:4627 ;
	Wed, 12 Jul 2006 17:32:49 +0200 
Message-ID: <44B51621.4040800@alcatel.be>
Date: Wed, 12 Jul 2006 17:32:49 +0200
From: stefaan.de_cnodder@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kais Belgaied <Kais.Belgaied@Sun.COM>
Subject: Re: [ANCP] Question about the ANCP high-level architecture
References: <44B51282.20109@Sun.COM>
In-Reply-To: <44B51282.20109@Sun.COM>
X-MIMETrack: Itemize by SMTP Server on BEMAIL06/BE/ALCATEL(Release
	5.0.13aHF163 | June 23, 2005) at 07/12/2006 17:32:50,
	Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.13aHF163 | June
	23, 2005) at 07/12/2006 17:32:51,
	Serialize complete at 07/12/2006 17:32:51
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org


Hi Kais,

see below...

Kais Belgaied wrote:

> Folks,
> 
> My question is regarding the following picture of the high level ANCP
> architecture:
> 
> 
>                                                +--------+
>                                                | Policy |
>                                                | Server |
>                                                +--------+
>                                                     |
>                                                     |
>   +-----+   +-----+   +--------+                 +-----+   +----------+
>   | CPE |---| HGW |---|        |                 |     |   |          |
>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>   +-----+   +-----+   +--------+                 +-----+   +----------+
> 
> 
> The policy server is attached to the NAS only.
> 
> A couple of observations about the AN:
> . it is shared between multiple HGWs that don't know/trust each other
> . it is the first candidate for enforcing link sharing policies (e.g. 
> bandwidth
>  allocation) between subscribers attached to those HGWs
> 

do you mean that bandwidth can be shared between 2 subscribers? This can 
also be done by the NAS Policy server I would think. Note that the main 
focus of the WG is DSL, and sharing bandwidth in DSL is rather difficult.

> Such policy is applicable to HGWs connected to the same AN.
> There may be other policy information still live in the NAS policy server.
> The picture could look more like:
> 
>                        +--------+              +--------+
>                        |   AN   |              |  NAS   |
>                        | Policy |              | Policy |
>                        | Server |              | Server |
>                        +--------+              +--------+
>                            |                        |
>                            |                        |
>   +-----+   +-----+   +--------+                 +-----+   +----------+
>   | CPE |---| HGW |---|        |                 |     |   |          |
>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>   +-----+   +-----+   +--------+                 +-----+   +----------+
> 
> comments?
> 

As mentioned during the meeting, the interaction with the policy server 
has to be further detailed. I do not say that the above architecture is 
invalid but I do not see how it relates to the current framework of 
ANCP. The NAS policy server gives all subscriber information to the NAS, 
which enforces the policies are gives them to the AN via ANCP. If you 
have 2 policy servers, then you must also take care of all possible 
interactions, e.g., AN policy server says that the bandwidth is x Mbps 
while the NAS says y Mbps.

Maybe an Element Management system to the AN can be added because that 
one has some interaction with ANCP.

regards,
Stefaan


> 
>     Kais
> 
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Wed Jul 12 14:16:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0jG6-0003G6-UE; Wed, 12 Jul 2006 14:16:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0jG5-0003Fz-Dt
	for ancp@ietf.org; Wed, 12 Jul 2006 14:16:25 -0400
Received: from nwkea-mail-4.sun.com ([192.18.42.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0jG3-0008RP-V6
	for ancp@ietf.org; Wed, 12 Jul 2006 14:16:25 -0400
Received: from jurassic.eng.sun.com ([129.146.68.130])
	by nwkea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k6CIGKL1028841; Wed, 12 Jul 2006 11:16:20 -0700 (PDT)
Received: from [192.9.61.35] (punchin-kais.SFBay.Sun.COM [192.9.61.35])
	by jurassic.eng.sun.com (8.13.6+Sun/8.13.6) with ESMTP id
	k6CIGJVr733357; Wed, 12 Jul 2006 11:16:19 -0700 (PDT)
Message-ID: <44B53C63.4090202@Sun.COM>
Date: Wed, 12 Jul 2006 11:16:03 -0700
From: Kais Belgaied <Kais.Belgaied@Sun.COM>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20060120
X-Accept-Language: ar-eg, en-us, en, ar, ar-dz, ar-bh, ar-iq, ar-jo, ar-kw,
	ar-lb, ar-ly, ar-ma, ar-om, ar-qa, ar-sa, ar-sy, ar-tn, ar-ae,
	ar-ye
MIME-Version: 1.0
To: stefaan.de_cnodder@alcatel.be
Subject: Re: [ANCP] Question about the ANCP high-level architecture
References: <44B51282.20109@Sun.COM> <44B51621.4040800@alcatel.be>
In-Reply-To: <44B51621.4040800@alcatel.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

stefaan.de_cnodder@alcatel.be wrote:

>
> Hi Kais,
>
> see below...
>
> Kais Belgaied wrote:
>
>> Folks,
>>
>> My question is regarding the following picture of the high level ANCP
>> architecture:
>>
>>
>>                                                +--------+
>>                                                | Policy |
>>                                                | Server |
>>                                                +--------+
>>                                                     |
>>                                                     |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>   | CPE |---| HGW |---|        |                 |     |   |          |
>>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>
>>
>> The policy server is attached to the NAS only.
>>
>> A couple of observations about the AN:
>> . it is shared between multiple HGWs that don't know/trust each other
>> . it is the first candidate for enforcing link sharing policies (e.g. 
>> bandwidth
>>  allocation) between subscribers attached to those HGWs
>>
>
> do you mean that bandwidth can be shared between 2 subscribers? This 
> can also be done by the NAS Policy server I would 


yes, that's what I mean. I understand the  information about all 
subscribers is available at the  Policy server.

> think. Note that the main focus of the WG is DSL, and sharing 
> bandwidth in DSL is rather difficult.


I'm possibly seeing more sharing in the aggregation node component than 
there actually is with DSL.
I view it as a resource shared between multiple subscribers, therefore 
the AN being the arbitrator for
accessing that resource would be a natural choice.
If in reality (and in the foreseeable future) the model for the 
aggregation node is just a collection of
independent pipes to to the NAS, then, yes the NAS is the first point 
shared access, and the policy
enforcement belongs there.

>
>> Such policy is applicable to HGWs connected to the same AN.
>> There may be other policy information still live in the NAS policy 
>> server.
>> The picture could look more like:
>>
>>                        +--------+              +--------+
>>                        |   AN   |              |  NAS   |
>>                        | Policy |              | Policy |
>>                        | Server |              | Server |
>>                        +--------+              +--------+
>>                            |                        |
>>                            |                        |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>   | CPE |---| HGW |---|        |                 |     |   |          |
>>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>
>> comments?
>>
>
> As mentioned during the meeting, the interaction with the policy 
> server has to be further detailed. I do not say that the above 
> architecture is invalid but I do not see how it relates to the current 
> framework of ANCP. The NAS policy server gives all subscriber 
> information to the NAS, which enforces the policies are gives them to 
> the AN via ANCP. If you have 2 policy servers, then you must also take 
> care of all possible interactions, e.g., AN policy server says that 
> the bandwidth is x Mbps while the NAS says y Mbps.


I should've clarified: the AN policy database is a subset of the whole 
policy database residing in the NAS policy server.
the AN server caches in the information relevant to subscribers 
connecting through it *only*.
and yes, that'll add a  requirement on the AN to keep the cached version 
in sync with the NAS',

>
> Maybe an Element Management system to the AN can be added because that 
> one has some interaction with ANCP.


makes sense.

    Kais.

>
> regards,
> Stefaan
>


_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 13 02:48:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0uzY-00010w-0c; Thu, 13 Jul 2006 02:48:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0uzX-00010M-4O
	for ancp@ietf.org; Thu, 13 Jul 2006 02:48:07 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0uzX-0008By-2E
	for ancp@ietf.org; Thu, 13 Jul 2006 02:48:07 -0400
Received: from tcmail33.telekom.de ([217.6.95.240])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G0uyW-00076R-KQ
	for ancp@ietf.org; Thu, 13 Jul 2006 02:47:06 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.dmz.telekom.de with
	ESMTP; Thu, 13 Jul 2006 08:46:56 +0200
Received: by S4DE8PSAANS.blf.telekom.de with Internet Mail Service
	(5.5.2653.19) id <3YPBTLLM>; Thu, 13 Jul 2006 08:46:56 +0200
Message-Id: <6439282641581441A36F7F6F83ED2ED2B809C6@S4DE8PSAAFQ.mitte.t-com.de>
From: "Haag, T" <Thomas.Haag@t-systems.com>
To: Kais.Belgaied@Sun.COM,
    stefaan.de_cnodder@alcatel.be
Subject: AW: [ANCP] Question about the ANCP high-level architecture
Date: Thu, 13 Jul 2006 08:47:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: -1.3 (-)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Stefaan, Kais,

Following your discussion I think we should not split between NAS policy and AN policy. The main focus should be to have one common subscriber policy server which talks via ANCP to the clients which reside in the AN. 

There are good reasons from an operational perspective. Having street cabinet installation each AN has to be connected separately to an AN Policy server which has to aggregate and to report to the NAS policy server. I expect more delay which might cause that e.g. a port up message will arrive later than a PPP - session up will arrive at the NAS.

Also other draw backs should be taken into account. Having in mind that a AN can be split in several partitions and each partition can talk to an individual NAS. In that case an AN policy server has to manage multiple connection to multiple NAS.

Regards

Thomas


Betreff: Re: [ANCP] Question about the ANCP high-level architecture

stefaan.de_cnodder@alcatel.be wrote:

>
> Hi Kais,
>
> see below...
>
> Kais Belgaied wrote:
>
>> Folks,
>>
>> My question is regarding the following picture of the high level ANCP
>> architecture:
>>
>>
>>                                                +--------+
>>                                                | Policy |
>>                                                | Server |
>>                                                +--------+
>>                                                     |
>>                                                     |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>   | CPE |---| HGW |---|        |                 |     |   |          |
>>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>
>>
>> The policy server is attached to the NAS only.
>>
>> A couple of observations about the AN:
>> . it is shared between multiple HGWs that don't know/trust each other
>> . it is the first candidate for enforcing link sharing policies (e.g. 
>> bandwidth
>>  allocation) between subscribers attached to those HGWs
>>
>
> do you mean that bandwidth can be shared between 2 subscribers? This 
> can also be done by the NAS Policy server I would 


yes, that's what I mean. I understand the  information about all 
subscribers is available at the  Policy server.

> think. Note that the main focus of the WG is DSL, and sharing 
> bandwidth in DSL is rather difficult.


I'm possibly seeing more sharing in the aggregation node component than 
there actually is with DSL.
I view it as a resource shared between multiple subscribers, therefore 
the AN being the arbitrator for
accessing that resource would be a natural choice.
If in reality (and in the foreseeable future) the model for the 
aggregation node is just a collection of
independent pipes to to the NAS, then, yes the NAS is the first point 
shared access, and the policy
enforcement belongs there.

>
>> Such policy is applicable to HGWs connected to the same AN.
>> There may be other policy information still live in the NAS policy 
>> server.
>> The picture could look more like:
>>
>>                        +--------+              +--------+
>>                        |   AN   |              |  NAS   |
>>                        | Policy |              | Policy |
>>                        | Server |              | Server |
>>                        +--------+              +--------+
>>                            |                        |
>>                            |                        |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>   | CPE |---| HGW |---|        |                 |     |   |          |
>>   +-----+   +-----+   | Access |   +---------+   |     |   | Regional |
>>                       |  Node  |---| Aggreg. |---| NAS |---| Network  |
>>   +-----+   +-----+   |        |   |  Node   |   |     |   |          |
>>   | CPE |---| HGW |---|        |   +---------+   |     |   |          |
>>   +-----+   +-----+   +--------+                 +-----+   +----------+
>>
>> comments?
>>
>
> As mentioned during the meeting, the interaction with the policy 
> server has to be further detailed. I do not say that the above 
> architecture is invalid but I do not see how it relates to the current 
> framework of ANCP. The NAS policy server gives all subscriber 
> information to the NAS, which enforces the policies are gives them to 
> the AN via ANCP. If you have 2 policy servers, then you must also take 
> care of all possible interactions, e.g., AN policy server says that 
> the bandwidth is x Mbps while the NAS says y Mbps.


I should've clarified: the AN policy database is a subset of the whole 
policy database residing in the NAS policy server.
the AN server caches in the information relevant to subscribers 
connecting through it *only*.
and yes, that'll add a  requirement on the AN to keep the cached version 
in sync with the NAS',

>
> Maybe an Element Management system to the AN can be added because that 
> one has some interaction with ANCP.


makes sense.

    Kais.

>
> regards,
> Stefaan
>


_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Mon Jul 24 09:58:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G50xC-0007rn-1F; Mon, 24 Jul 2006 09:58:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G50xA-0007rZ-5k
	for ancp@ietf.org; Mon, 24 Jul 2006 09:58:36 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G50x9-000245-ER
	for ancp@ietf.org; Mon, 24 Jul 2006 09:58:36 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 24 Jul 2006 15:58:35 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6ODwYUO009775; 
	Mon, 24 Jul 2006 15:58:34 +0200 (MEST)
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 24 Jul 2006 15:58:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6AF29.40C85BB9"
Date: Mon, 24 Jul 2006 15:58:30 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4024278B8@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: ANCP_IETF66_minutes.txt
Thread-Index: AcavJ3Ld6bOimijIQ+y4/pfd80Gt+A==
From: "Wojciech Dec \(wdec\)" <wdec@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 24 Jul 2006 13:58:34.0458 (UTC)
	FILETIME=[40EF43A0:01C6AF29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk
Subject: [ANCP] ANCP_IETF66_minutes.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6AF29.40C85BB9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

 Dear All,

Attached please find the ANCP WG meeting minutes from IETF 66.
Please let us know of any corrections that may be due.

A brief summary of the action items :

1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG
ID
2. (Chair) Create new WG mile-stone for delivery of security threat
analysis draft
3. (Chair) Formulate a question to the WG addressing the ANCP
Partitioning work item; functional, port partitioning and redundancy.

I would also like to invite all volunteers who indicated an interest in
taking on the security analysis task to come forward, if they have not
already done so.

Regards,
Woj and Matthew.
 <<ANCP_IETF66_minutes.txt>>=20

------_=_NextPart_001_01C6AF29.40C85BB9
Content-Type: text/plain;
	name="ANCP_IETF66_minutes.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="ANCP_IETF66_minutes.txt"

MS4JSW50cm9kdWN0aW9uIC8gYWdlbmRhIHR3ZWFraW5nIC8gQmx1ZSBTaGVldHMgKENoYWlycyAt
IDUgbWlucykgDQoNCjIuIFdvcmtpbmcgR3JvdXAgQ2hhcnRlciAoQ2hhaXJzIC0gMTAgbWlucykg
DQotCUNoYW5nZXMgdG8gdGhlIGNoYXJ0ZXIgc2luY2UgdGhlIEJvRi4NCi0JRGlzY3Vzc2VkIGlu
IEJPRg0KLQlSZXZpc2VkIG1pbGVzdG9uZXMNCi0JTWFpbGluZyBsaXN0IGNoYW5nZXMNCg0KQ2hh
aXI6IEFOQ1AgY2hhcnRlciByZXZpc2VkIGFuZCBmaW5hbGl6ZWQgZm9sbG93aW5nIGlucHV0IGZy
b20gYWxpYXMgYW5kIEFEcy4gTWlsZXN0b25lcyBhZGp1c3RlZCB0byByZWZsZWN0IGRlbGl2ZXJ5
IG9mIHJlcXVpcmVtZW50cyBkcmFmdCAoZW5kIG9mIDIwMDYpIGJlZm9yZSBwcm90b2NvbCBzcGVj
Lg0KTDJDUCBtYWlsaW5nIGxpc3Qgbm8gbG9uZ2VyIGFjdGl2ZSAtIGFsbCBtZW1iZXJzIG1vdmVk
IHRvIEFOQ1AgbGlzdC4NCg0KUXVlc3Rpb25zDQpFbW1hbnVlbCBEZXNtZXQ6IFdoeSBhcmUgd2Ug
dXNpbmcgTkFTIChJRVRGKSB2cyBCTkcgKERTTCBGb3J1bSkNCkNoYWlyOiBCZWNhdXNlIElFVEYg
aGFzIHRyYWRpdGlvbmFsbHkgdXNlZCB0aGUgdGVybSBOQVMuDQoNClEyICg/RUNJKS4gV2hhdCBp
cyB0aGUgY29ubmVjdGlvbiBiZXR3ZWVuIERTTCBGb3J1bSB3b3JrIGFuZCBBTkNQIFdHLg0KQTIu
IElFVEYgZGVmaW5lcyBwcm90b2NvbHMsIERTTCBGb3J1bSBkZWZpbmVzIHVzZSBjYXNlcy4gUmVx
dWlyZW1lbnRzIGNvbWUgZnJvbSBEU0wgRm9ydW0uIE5vcm1hbCBsaWFpc29uIHByb2Nlc3MgYW5k
IGNvbW1vbiBncm91cCBtZW1iZXJzaGlwIHdpbGwgYmUgdXNlZCB0byBrZWVwIHN5bmNoLiANCk1h
cmsgVG93bnNsZXkgLSBEU0wgRm9ydW0gcmVsYXRpb25zaGlwIGlzIG1lbnRpb25lZCBpbiBjaGFy
dGVyLiANCg0KDQozLiBBTkNQIFJlcXVpcmVtZW50cyAoU3RlZmFhbiBkZSBDbm9kZGVyIC0gMTVt
aW5zKQ0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtb29naGUtYW5j
cC1mcmFtZXdvcmstMDAudHh0DQpVcGRhdGUgb24gY2hhbmdlcyBzaW5jZSB0aGUgQm9GDQoNClJh
bHBoIERyb21zOiBDbGFyaWZpY2F0aW9uIG9uIGNvbm5lY3Rpdml0eSB0ZXN0cyB0byBIb21lIEdh
dGV3YXkgKEFjdHVhbGx5IE5BUyB0byBBTikuIFByb3RvY29sIHRyaWdnZXJzIHRoZSBORyB0byBw
ZXJmb3JtIGEgbGluZSB0ZXN0Lg0KDQpTaG91bGQgdGhpcyBiZWNvbWUgYSBXb3JraW5nIGdyb3Vw
IGRvY3VtZW50PyBHZW5lcmFsIGNvbnNlbnN1cyB3YXMgWUVTIGZyb20gdGhvc2Ugd2hvIHJlYWQg
dGhlIGRvY3VtZW50IGFuZCBwcmVzZW50IGluIHRoZSByb29tLg0KDQo0LiBHU01QIGV4dGVuc2lv
bnMgZm9yIGxheWVyMiBjb250cm9sIChMMkMpIFRvcG9sb2d5IERpc2NvdmVyeSBhbmQgTGluZSBD
b25maWd1cmF0aW9uICAoU2FuamF5IFdhZGh3YSAtIDE1IG1pbnMpDQpodHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC13YWRod2EtZ3NtcC1sMmNvbnRyb2wtY29uZmlndXJh
dGlvbi0wMS50eHQNClVwZGF0ZSBvbiBjaGFuZ2VzIHNpbmNlIHRoZSBCb0Y7IHN1bW1hcnkgaW4g
cG9zdGVkIHNsaWRlcw0KDQo1LiBBTkNQIEdyYWNlZnVsIFJlc3RhcnQgTWVjaGFuaXNtIChTYW5q
YXkgV2FkaHdhIC0gMTAgbWlucykNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LXdhZGh3YS1hbmNwLWdyYWNlZnVsLXJlc3RhcnQtMDAudHh0DQpOZXcgZHJhZnQNCg0K
QS4gRG9yaWE6IENoYW5nZSB0byBiYXNlIHByb3RvY29sIHNwZWM/IFNhbmpheSBZZXMsIHRoaXMg
bWVjaGFuaXNtIHJlcXVpcmVzIG1vZGlmaWNhdGlvbnMgdG8gYmFzZSBzcGVjLg0KTWFyayBULjog
Q29uc2lkZXIgYWRkaW5nIGEgbmV3IG1pbGVzdG9uZS4gVGhpcyBpcyBvaywgYXMgbG9uZyBhcyB3
b3JrIGZpdHMgd2l0aGluIHRoZSBjaGFydGVyLg0KRG9yaWE6IEV4dGVuc2lvbnMgYXJlIGRlZmlu
ZWQgaW4gY29tcGFuaW9uIHNwZWNzLiBCdXQgY29yZSBzcGVjIG11c3QgYmUgbW9kaWZpZWQgdG8g
YWxsb3cgZ3JhY2VmdWwgcmVzdGFydC4gSG93IGlzIHRoaXMgdG8gYmUgaGFuZGxlZD8gDQpEaXNj
dXNzaW9uIG9uIHdoZXRoZXIgdG8gY29sbGFwc2UgdGhlc2UgdG8gc3BlY3MuIERvcmlhIHN1Z2dl
c3QgdGhhdCBtYXliZSB0aGlzIGJlIGFwcHJvcHJpYXRlLiANCk1hcmsgVC46IENhbGwgY2FuIGJl
IG1hZGUgb25jZSB0aGUgcmVxdWlyZW1lbnQgZG9jIHByb2dyZXNzZXMuDQoNClNhbmpheTogQ2Fu
IHdlIG1ha2UgdGhpcyBkb2MgYSBXRyBJLUQ/IENoYXJ0ZXIgb25seSBoYXMgb25lIHByb3RvY29s
IHJlcXVpcmVtZW50LiBDYW4gd2UgYWRkIHRoaXMgb25lLg0KV0cgQ2hhaXI6IFRvIGVhcmx5IHRv
IGFzayBmb3Igd29ya2luZyBncm91cCBjb25zZW5zdXMgb24gZ3JhY2VmdWwgcmVzdGFydCBkb2Mu
IEtlZXAgYXMgZHJhZnQgZm9yIHdvcmtpbmcgZ3JvdXAgdG8gcmV2aWV3IGFuZCBjb25zaWRlci4N
Cg0KDQpPcGVuIGRpc2N1c3Npb24gYW5kIFF1ZXN0aW9ucyBvbiBvcmlnaW5hbCBwcm90b2NvbCBz
cGVjIGRyYWZ0IChkcmFmdC13YWRod2EtZ3NtcC1sMmNvbnRyb2wtY29uZmlndXJhdGlvbi0wMS50
eHQgYW5kIGRyYWZ0LW9vZ2hlLWFuY3AtZnJhbWV3b3JrLTAwLnR4dCkgOg0KDQpRdWVzdGlvbjog
TGF5ZXIgdHdvIGVuY2Fwcy4gRHNsIGxpbmUgY2FuIGhhdmUgc2V2ZXJhbCBsMiBlbmNhcHMsIHZs
YW5zIHcvZGlmZiBzZXJ2aWNlcy4gRG9jdW1lbnQgc2F5cyBvbmUgdmxhbiBwZXIgbGluZSBhbmQg
b25lIGVuY2Fwcy4gSG93IGFyZSBtdWx0aXBsZSB2bGFucyB0byBiZSBoYW5kbGVkPw0KQW5zd2Vy
KFNhbmpheSk6IE11bHRpcGxlIHZsYW5zIGFyZSBzdXBwb3J0ZWQuIE11bHRpcGxlIGVuY2FwcyBu
ZWVkcyBzb21lIGNvbnNpZGVyYXRpb25zLiANCkNvbW1lbnQgZnJvbSBhdWRpZW5jZTogk2VuY2Fw
IGlzIG9ubHkgaW1wb3J0YW50IGZvciBzaGFwaW5nIGZ1bmN0aW9uIG9uIE5BUyBpZiBlbmNhcCBp
cyBjaGFuZ2luZyBlZyBmcm9tIG9BIHRvIG9FlC4NCg0KUSAoP0ZUKTogU2VjdXJpdHkgb2JqZWN0
aXZlcyBpbiBjaGFydGVyLCBkb2VzIGl0IGNvbmNlcm4gc2VjdXJpdHkgYmV0d2VlbiBOQVMgYW5k
IEFOIG9yIHByb3RvY29sIHNlY3VyaXR5Pw0KQW5zd2VyIChDaGFpcik6IFJlcXVpcmVtZW50cyBk
b2Mgc2VjdXJpdHkgc2VjdGlvbiBpcyBub3QgY29tcGxldGVkLiBTZWN1cml0eSBvYmplY3RpdmUg
aXMgZm9yIHRoZSBBTkNQIHByb3RvY29sIGl0c2VsZi4gDQpNYXJrIHdvdWxkIGxpa2UgYSB0aHJl
YXQgYW5hbHlzaXMgZG9uZSBmaXJzdCB0aGVuIHByb2R1Y2Ugc2VjdXJpdHkgcmVxdWlyZW1lbnRz
Lg0KDQpRIChHLiBCYWlsZXkpOiBOYW1lIG9mIHVzZS1jYXNlIJNsaW5lIGNvbmZpZyBhbmQgdG9w
b2xvZ3kgZGlzY292ZXJ5IFdhbnRzIGl0IHJlbmFtZWQuDQpBKENoYWlyKTogVGhlcmUgaXMgYSBu
ZXcgbmFtZSBmb3IgaXQuDQoNClEgKEcuIEJhaWxleSk6IFNob3VsZCByZWZlciBiYWNrIHRvIHRo
ZSBmcmFtZXdvcmsgZG9jdW1lbnQ/DQpBIChTYW5qYXkpOiBTb21lIGRvY3VtZW50cyBuZWVkIGNs
ZWFudXAgYmVjYXVzZSByZXF1aXJlbWVudHMgY2FtZSBhZnRlciBzb21lIElEJ3MuDQoNClEgKEVD
SSk6IFdoYXQgaXMgcmVhc29uIGZvciBuZXcgcmVtb3RlIGxpbmUgaWQ/IA0KQSAoU2FuamF5KTog
SG9zdCBpZGVudGlmaWVyIGlzIGEgbWFuZGF0b3J5LiBOZXdseSBhZGRlZCBvcHRpb25hbCBwYXJh
bWV0ZXIsIGNvbXBhdGlibGUgd2l0aCBkaGNwIGFuZCBwcHBvZS4gQ291bGQgYmUgdXNlZCB0byBj
b252ZXkgaW5mbyBmcm9tIG5hcyB0byBwb2xpY3kgc2VydmVyLiBEaWZmZXJlbnQgdGhhbiCTbG9j
YWwgbG9vcCBpZGVudGlmaWNhdGlvbpQgY29udGFpbnMgbW9yZSB1c2VyIHNwZWNpZmljIGluZm9y
bWF0aW9uLiANCkNvbW1lbnQgZnJvbSBhdWRpZW5jZTogQ2lyY3VpdCBpZCBub3QgYWx3YXlzIGNv
bmZpZ3VyYWJsZSBvbiBBTiBidXQgcmVtb3RlIGlkIHVzdWFsbHkgaXMuDQoNClEgKFAuIEFyYmVy
Zyk6IE11bHRpcGxlIFZDJ3Mgb24gbGluZSwgaG93IHNob3VsZCB0aGUgY2FzZSBiZSBoYW5kbGVk
IHdoZW4gYSBWQyBpcyByZW1vdmVkIGFuZCBPQU0gaXMgYXR0ZW1wdGVkPw0KQSAoU2FuamF5KTog
T0FNIHNwZWNpZmljYXRpb24gb2YgVkMvVkxBTiBzaG91bGQgdHJpZ2dlciBhIHNwZWNpZmljIGVy
cm9yIGNvZGUgd2hlbiBWQy9WTEFOIGRvZXMgbm90IGV4aXN0KD8pDQoNCg0KNi4gQU5DUCBNSUJz
IChTdGVmYWFuIGRlIENub2RkZXIgLSAxMCBtaW5zKQ0KDQpCYXNlZCBvbiBHU01QIE1JQiAoMzI5
NSkuIA0KDQpBTkNQIE1JQiBpcyBhbiBleHRlbnNpb24gb2YgR1NNUCBNSUIuDQoNClEgKEEuIERv
cmlhKTogU3VnZ2VzdHMgZG9pbmcgYSB3aG9sZSBuZXcgR1NNUCBNSUIgYmVjYXVzZSBjdXJyZW50
IG9uZSBpcyBpbmFkZXF1YXRlLg0KDQpGaXJzdCBwcm9wb3NhbCBvZiBBY2Nlc3MgTm9kZSBwYXJ0
IHdpbGwgYmUgZG9uZSBzb29uLg0KDQpBIChTdGVmZmFuKSB3b3VsZCBsaWtlIGhlbHAgd29ya2lu
ZyBvbiBNSUJzLCBsb29raW5nIGZvciB2b2x1bnRlZXJzIGVzcGVjaWFsbHkgdG8gcHJvZ3Jlc3Mg
TkFTIE1JQnMuDQoNCkNoYWlyOiBNSUIgd29yayBoYXMgdG8gcmVtYWluIG9wZW4gdG8gY2hhbmdl
cyBpbiBiYXNlIHByb3RvY29sIHNwZWMsIGVzcGVjaWFsbHkgc2luY2Ugc2VjdXJpdHkgYW5kIHRy
YW5zcG9ydCBhc3BlY3RzIGFyZSBzdGlsbCB0byBiZSBhZGRyZXNzZWQuDQoNCg0KNy4gRGlzY3Vz
c2lvbiBvZiBvdXRzdGFuZGluZyB3b3JraW5nIGdyb3VwIGl0ZW1zIChDaGFpcnMgLSAzMG1pbnMp
DQotCUFjY2VzcyBOb2RlIFBvcnQgYW5kIEZ1bmN0aW9uYWwgUGFydGl0aW9uaW5nIGFuZCBtdWx0
aXBsZSBjb250cm9sbGVycy4NCg0KRGVzY3JpcHRpb24gb2YgY3VycmVudCAxLTEgcm9sZSBvZiBj
b250cm9sbGVyIGFuZCBpZGVhIG9mIGNvbnRyb2xsZXIgcmVkdW5kYW5jeSBhbmQgZnVuY3Rpb25h
bCBzcGxpdCBjb25jZXB0LiANClF1ZXN0aW9ucyAxLDIgYW5kIDMgb24gdGhlIGNoYWlyJ3Mgc2xp
ZGVzLiBEbyB3ZSBuZWVkIHRvIGFkZCByZWR1bmRhbmN5IHRvIGNvbnRyb2xsZXJzPyBTcGxpdCBm
dW5jdGlvbmFsaXR5IG9mIGNvbnRyb2xsZXJzIChpZTogUU9TIGFuZCBPQU0gYW5kIE11bHRpY2Fz
dCkuDQoNClNhbmpheTogU3RhcnQgd2l0aCBjb250cm9sbGVyIHJlZHVuZGFuY3kgc3BsaXQgcmF0
aGVyIHRoYW4gZnVuY3Rpb25hbCBzcGxpdC4gDQpDaGFpcjogRnVuY3Rpb25hbCBzcGxpdCBhbmQg
bXVsdGlwbGUgZWRnZSBhcmUgbm90IGV4Y2x1ZGVkIGJ5IHRoZSBjdXJyZW50IHNjb3BlLg0KRG9y
aWE6IFNpbWlsYXIgaXNzdWUgc2VlbiBpbiBGb3JjZXMgV0cuIFdoYXQgYWJvdXQgc3luYyBtZWNo
YW5pc20gYmV0d2VlbiByZWR1bmRhbnQgY29udHJvbGxlcnM/IA0KU2FuamF5OiBTdGF0ZWZ1bGwg
b3IgU3RhdGVsZXNzIENvbnRyb2xsZXIgcmVkdW5kYW5jeSBpcyB0aGUgcXVlc3Rpb24uIEZpcnN0
IGNhbiBoYW5kbGUgdGhlIHN0YXRlbGVzcyBjYXNlIGFuZCB0aGVuIG1vdmUgdG8gc3RhdGVmdWwu
DQoNCk1vcmUgc2hvdyBvZiBoYW5kcyBmb3IgaW50ZXJlc3QgaW4gY29udHJvbGxlciBzcGxpdCB0
aGFuIGZ1bmN0aW9uYWwgc3BsaXQuIE1ham9yaXR5IG9mIHJvb20gd2l0aCBubyBvcGluaW9uLiBW
ZXJ5IGxpdHRsZSBjb21tZW50cyBmcm9tIGF1ZGllbmNlLiANClRvIGJlIGJyb3VnaHQgdG8gdGhl
IFdHIG1haWxpbmcgbGlzdCBmb3IgZGlzY3Vzc2lvbi4NCg0KTWFyayBUOiBsZXRzIHRha2UgdGhl
IHF1ZXN0aW9ucyB0byB0aGUgbGlzdCBmb3IgZnVydGhlciBjb25zaWRlcmF0aW9uLg0KDQotCUxp
Z2h0LXdlaWdodCB0cmFuc3BvcnQgcHJvdG9jb2wuIA0KDQpDaGFpcjogTGlnaHQgd2VpZ2h0IHRy
YW5zcG9ydCBpcyBpbnRlbmRlZCB0byBtYWtlIEFOQ1Agc2NhbGUgdG8gbGFyZ2UgZGVwbG95bWVu
dHMgd2l0aCAxMDBzLTEwMDBzIG9mIG5vZGVzLg0KQ2hhaXIgUXVlc3Rpb24gMTogd2hhdCBhcmUg
dGhlIGFjdHVhbCB0cmFuc3BvcnQgcmVxdWlyZW1lbnRzPyANCg0KU2FuamF5OiBBTkNQIHJlcXVp
cmVtZW50cyBzaG91bGQgYmUgZ2VuZXJpYy4gUmVxdWlyZW1lbnRzIHNwZWMgc2hvbGQgbm90IGlk
ZW50aWZ5IGEgdHJhbnNwb3J0IHByb3RvY29sLiAgUHJvdG9jb2wgc3BlYyBjYW4gY29udGFpbiB0
aGlzIGxldmVsIG9mIGRldGFpbC4gUmVxdWlyZW1lbnRzIHNob3VsZCBpbmRpY2F0ZSB0aGF0IHRo
aXMgdXNlIGNhc2UgcmVxdWlyZXMgdGhpcyB0cmFuc3BvcnQgcmVxdWlyZW1lbnQuDQpDaGFpcjog
QWdyZWUuDQoNCkNoYWlyIFF1ZXN0aW9uMjogZG9lcyBsaWdodCB3ZWlnaHQgdHJhbnNwb3J0IGJl
Y29tZSB0aGUgbG9uZyB0ZXJtIGdvYWwgb3ZlciBUQ1A/DQpSb3VnaCBvcGluaW9uIGZyb20gZmxv
b3I6IFdvdWxkIHByZWZlciBsaWdodCB3ZWlnaHQgcHJvdG9jb2wuIA0KTW9yZSBkaXNjdXNzaW9u
IG5lZWRlZC4NCg0KQ2hhaXIgUXVlc3Rpb24gMzogRG8gd2UgbG9vayBmb3IgYW4gZXhpc3Rpbmcg
bGlnaHQtd2VpZ2h0IHRyYW5zcG9ydD8gUHJlZmVyZW5jZSBpcyBjbGVhcmx5IGZvciBub3QgaW52
ZW50aW5nIGEgbmV3IHRyYW5zcG9ydCBwcm90b2NvbC4gQnV0IGJlZm9yZSBhbnkgc2VsZWN0aW9u
IGNhbiBiZSBtYWRlIHJlcXVpcmVtZW50cyBuZWVkIHRvIGJlIGRyYWZ0ZWQuIEN1cnJlbnQgcHJv
dG9jb2wgcmVxdWlyZW1lbnRzIGRvYyBkb2VzIG5vdCBzdWZmaWNpZW50bHkgYWRkcmVzcyB0cmFu
c3BvcnQgcmVxdWlyZW1lbnRzLg0KDQpEcm9tczogV2hhdCBpcyB0aGUgSUVTRy9JQUIgZ3VpZGFu
Y2UgcmVnYXJkaW5nIHRyYW5zcG9ydCBwcm90b2NvbCBzZWxlY3Rpb24/DQpNYXJrIFQ6IE5vdCBn
b2luZyB0byB0YWxrIHRvIHRyYW5zcG9ydCBBRHMgb3IgZG8gcHJvdG9jb2wgc2VsZWN0aW9udW50
aWwgd2UgaGF2ZSByZXF1aXJlbWVudHMuIE9uY2UgdGhhdCdzIHRoZXJlIGNvbnN1bHRhdGlvbiB3
aWxsIGJlIG1hZGUuDQoNCkNoYWlyOiBXRyBuZWVkcyB0byBjb250cmlidXRlIHRyYW5zcG9ydCBy
ZXF1aXJlbWVudHMgaW50byBleGlzdGluZyByZXF1aXJlbWVudHMgZHJhZnQgdG8gYW5zd2VyIHF1
ZXN0aW9uIDEuDQoNCi0JQU5DUCBQcm90b2NvbCBTZWN1cml0eS4gDQoNCkNoYWlyOiBObyBwcm9n
cmVzcyBvbiBjcml0aWNhbCBpdGVtIGZvciB0aGUgcHJvdG9jb2wuIFZhcmlvdXMgYXNwZWN0cyBo
YXZlIGltcGFjdCBvbiBzZWN1cml0eSwgZWcgY2hvaWNlIG9mIHRyYW5zcG9ydC4gVGhyZWFkIG1v
ZGVsIGlzIG5lZWQuIA0KTWFyayBUOiBzdWdnZXN0cyBub3QgdXNpbmcgVENQIE1ENS4NCg0KQ2hh
aXIgaXMgbG9va2luZyBmb3Igdm9sdW50ZWVycyB0byBkZXZlbG9wIGEgdGhyZWF0IG1vZGVsIGFu
ZCBkZXJpdmUgcmVxdWlyZW1lbnRzLiANCg0KLSBNdWx0aWNhc3QgY29udHJvbC4NCg0KQ2hhaXI6
IFR3byBtYWluIGZ1bmN0aW9ucyBtZW50aW9uZWQgZm9yIG11bHRpY2FzdCBzbyBmYXIgaSkgY29u
dHJvbCBvZiByZXBsaWNhdGlvbiBvciBtdWx0aWNhc3QgZGF0YSBwbGFuZSBhbmQgaWkpIG11bHRp
Y2FzdCBncm91cCBhbmQgc3RhdGlzdGljcyByZXBvcnRpbmcuIFVzZSBjYXNlcyByZW1haW4gdG8g
YmUgZmlybWVkIHVwLiBXb3VsZCBsaWtlIHRvIGludm9sdmUgbXVsdGljYXN0IFdHcyBpbiB0aGlz
Lg0KU2VzaGVlbGE6IE1ib25lZCBoYXMgbXVsdGljYXN0IHNlc3Npb24gY29udHJvbCBhbmQgYWRt
aXNzaW9uIHdvcmsgZ29pbmcgb24gdGhhdCBjYW4gZ28gYWxvbmcgd2l0aCB0aGlzLg0KDQoNCg==

------_=_NextPart_001_01C6AF29.40C85BB9
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

------_=_NextPart_001_01C6AF29.40C85BB9--




From ancp-bounces@ietf.org Mon Jul 24 10:24:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G51MA-0001ef-J9; Mon, 24 Jul 2006 10:24:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G51M9-0001eZ-1L
	for ancp@ietf.org; Mon, 24 Jul 2006 10:24:25 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G51M8-0005Ku-5k
	for ancp@ietf.org; Mon, 24 Jul 2006 10:24:25 -0400
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D4024278B8@xmb-ams-33b.emea.cisco.com>
To: "Wojciech Dec \(wdec\)" <wdec@cisco.com>
Subject: Re: [ANCP] ANCP_IETF66_minutes.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OFBC14A7C9.3403E214-ONC22571B5.004E00B4-C22571B5.004F22A0@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Mon, 24 Jul 2006 17:24:20 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/24/2006 17:32:45
Content-Type: multipart/mixed; boundary="=_mixed 004F2298C22571B5_="
X-Spam-Score: 0.3 (/)
X-Scan-Signature: fec852dbea6d068499ed3250edf328e2
Cc: Matthew.Bocci@alcatel.co.uk, alex.zinin@alcatel.com, ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

--=_mixed 004F2298C22571B5_=
Content-Type: multipart/alternative;
	boundary="=_alternative 004F229AC22571B5_="


--=_alternative 004F229AC22571B5_=
Content-Type: text/plain; charset="US-ASCII"

Hi Wojciech,

        Regarding the minutes:

        1. I am the (?ECI) person.

        2, Regarding the statement  "DSL Forum relationship is mentioned 
in the charter". I don't see any mention of the
DSL Forum in the charter, would someone be kind enough to point out in 
which paragraph it is mentioned.

 
Best Regards,
Menachem Dodge





"Wojciech Dec \(wdec\)" <wdec@cisco.com> 
24/07/2006 16:58

To
<ancp@ietf.org>
cc
alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk
Subject
[ANCP] ANCP_IETF66_minutes.txt






 Dear All,

Attached please find the ANCP WG meeting minutes from IETF 66.
Please let us know of any corrections that may be due.

A brief summary of the action items :

1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG
ID
2. (Chair) Create new WG mile-stone for delivery of security threat
analysis draft
3. (Chair) Formulate a question to the WG addressing the ANCP
Partitioning work item; functional, port partitioning and redundancy.

I would also like to invite all volunteers who indicated an interest in
taking on the security analysis task to come forward, if they have not
already done so.

Regards,
Woj and Matthew.
 <<ANCP_IETF66_minutes.txt>> 
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp


--=_alternative 004F229AC22571B5_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Wojciech,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Regarding
the minutes:</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 1.
I am the (?ECI) person.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 2,
Regarding the statement &nbsp;&quot;DSL Forum relationship is mentioned
in the charter&quot;. I don't see any mention of the</font>
<br><font size=2 face="sans-serif">DSL Forum in the charter, would someone
be kind enough to point out in which paragraph it is mentioned.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem Dodge<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Wojciech Dec \(wdec\)&quot;
&lt;wdec@cisco.com&gt;</b> </font>
<p><font size=1 face="sans-serif">24/07/2006 16:58</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&lt;ancp@ietf.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[ANCP] ANCP_IETF66_minutes.txt</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>&nbsp;Dear All,<br>
<br>
Attached please find the ANCP WG meeting minutes from IETF 66.<br>
Please let us know of any corrections that may be due.<br>
<br>
A brief summary of the action items :<br>
<br>
1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG<br>
ID<br>
2. (Chair) Create new WG mile-stone for delivery of security threat<br>
analysis draft<br>
3. (Chair) Formulate a question to the WG addressing the ANCP<br>
Partitioning work item; functional, port partitioning and redundancy.<br>
<br>
I would also like to invite all volunteers who indicated an interest in<br>
taking on the security analysis task to come forward, if they have not<br>
already done so.<br>
<br>
Regards,<br>
Woj and Matthew.<br>
 &lt;&lt;ANCP_IETF66_minutes.txt&gt;&gt; <br>
_______________________________________________<br>
ANCP mailing list<br>
ANCP@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/ancp<br>
</tt></font>
<br>
--=_alternative 004F229AC22571B5_=--
--=_mixed 004F2298C22571B5_=
Content-Type: text/plain; name="ANCP_IETF66_minutes.txt"
Content-Disposition: attachment; filename="ANCP_IETF66_minutes.txt"
Content-Transfer-Encoding: quoted-printable

1.	Introduction / agenda tweaking / Blue Sheets (Chairs - 5 mins)=20

2. Working Group Charter (Chairs - 10 mins)=20
-	Changes to the charter since the BoF.
-	Discussed in BOF
-	Revised milestones
-	Mailing list changes

Chair: ANCP charter revised and finalized following input from alias and AD=
s. Milestones adjusted to reflect delivery of requirements draft (end of 20=
06) before protocol spec.
L2CP mailing list no longer active - all members moved to ANCP list.

Questions
Emmanuel Desmet: Why are we using NAS (IETF) vs BNG (DSL Forum)
Chair: Because IETF has traditionally used the term NAS.

Q2 (?ECI). What is the connection between DSL Forum work and ANCP WG.
A2. IETF defines protocols, DSL Forum defines use cases. Requirements come =
from DSL Forum. Normal liaison process and common group membership will be =
used to keep synch.=20
Mark Townsley - DSL Forum relationship is mentioned in charter.=20


3. ANCP Requirements (Stefaan de Cnodder - 15mins)
http://www.ietf.org/internet-drafts/draft-ooghe-ancp-framework-00.txt
Update on changes since the BoF

Ralph Droms: Clarification on connectivity tests to Home Gateway (Actually =
NAS to AN). Protocol triggers the NG to perform a line test.

Should this become a Working group document? General consensus was YES from=
 those who read the document and present in the room.

4. GSMP extensions for layer2 control (L2C) Topology Discovery and Line Con=
figuration  (Sanjay Wadhwa - 15 mins)
http://www.ietf.org/internet-drafts/draft-wadhwa-gsmp-l2control-configurati=
on-01.txt
Update on changes since the BoF; summary in posted slides

5. ANCP Graceful Restart Mechanism (Sanjay Wadhwa - 10 mins)
http://www.ietf.org/internet-drafts/draft-wadhwa-ancp-graceful-restart-00.t=
xt
New draft

A. Doria: Change to base protocol spec? Sanjay Yes, this mechanism requires=
 modifications to base spec.
Mark T.: Consider adding a new milestone. This is ok, as long as work fits =
within the charter.
Doria: Extensions are defined in companion specs. But core spec must be mod=
ified to allow graceful restart. How is this to be handled?=20
Discussion on whether to collapse these to specs. Doria suggest that maybe =
this be appropriate.=20
Mark T.: Call can be made once the requirement doc progresses.

Sanjay: Can we make this doc a WG I-D? Charter only has one protocol requir=
ement. Can we add this one.
WG Chair: To early to ask for working group consensus on graceful restart d=
oc. Keep as draft for working group to review and consider.


Open discussion and Questions on original protocol spec draft (draft-wadhwa=
-gsmp-l2control-configuration-01.txt and draft-ooghe-ancp-framework-00.txt)=
 :

Question: Layer two encaps. Dsl line can have several l2 encaps, vlans w/di=
ff services. Document says one vlan per line and one encaps. How are multip=
le vlans to be handled?
Answer(Sanjay): Multiple vlans are supported. Multiple encaps needs some co=
nsiderations.=20
Comment from audience: =93encap is only important for shaping function on N=
AS if encap is changing eg from oA to oE=94.

Q (?FT): Security objectives in charter, does it concern security between N=
AS and AN or protocol security?
Answer (Chair): Requirements doc security section is not completed. Securit=
y objective is for the ANCP protocol itself.=20
Mark would like a threat analysis done first then produce security requirem=
ents.

Q (G. Bailey): Name of use-case =93line config and topology discovery Wants=
 it renamed.
A(Chair): There is a new name for it.

Q (G. Bailey): Should refer back to the framework document?
A (Sanjay): Some documents need cleanup because requirements came after som=
e ID's.

Q (ECI): What is reason for new remote line id?=20
A (Sanjay): Host identifier is a mandatory. Newly added optional parameter,=
 compatible with dhcp and pppoe. Could be used to convey info from nas to p=
olicy server. Different than =93local loop identification=94 contains more =
user specific information.=20
Comment from audience: Circuit id not always configurable on AN but remote =
id usually is.

Q (P. Arberg): Multiple VC's on line, how should the case be handled when a=
 VC is removed and OAM is attempted?
A (Sanjay): OAM specification of VC/VLAN should trigger a specific error co=
de when VC/VLAN does not exist(?)


6. ANCP MIBs (Stefaan de Cnodder - 10 mins)

Based on GSMP MIB (3295).=20

ANCP MIB is an extension of GSMP MIB.

Q (A. Doria): Suggests doing a whole new GSMP MIB because current one is in=
adequate.

First proposal of Access Node part will be done soon.

A (Steffan) would like help working on MIBs, looking for volunteers especia=
lly to progress NAS MIBs.

Chair: MIB work has to remain open to changes in base protocol spec, especi=
ally since security and transport aspects are still to be addressed.


7. Discussion of outstanding working group items (Chairs - 30mins)
-	Access Node Port and Functional Partitioning and multiple controllers.

Description of current 1-1 role of controller and idea of controller redund=
ancy and functional split concept.=20
Questions 1,2 and 3 on the chair's slides. Do we need to add redundancy to =
controllers? Split functionality of controllers (ie: QOS and OAM and Multic=
ast).

Sanjay: Start with controller redundancy split rather than functional split=
.=20
Chair: Functional split and multiple edge are not excluded by the current s=
cope.
Doria: Similar issue seen in Forces WG. What about sync mechanism between r=
edundant controllers?=20
Sanjay: Statefull or Stateless Controller redundancy is the question. First=
 can handle the stateless case and then move to stateful.

More show of hands for interest in controller split than functional split. =
Majority of room with no opinion. Very little comments from audience.=20
To be brought to the WG mailing list for discussion.

Mark T: lets take the questions to the list for further consideration.

-	Light-weight transport protocol.=20

Chair: Light weight transport is intended to make ANCP scale to large deplo=
yments with 100s-1000s of nodes.
Chair Question 1: what are the actual transport requirements?=20

Sanjay: ANCP requirements should be generic. Requirements spec shold not id=
entify a transport protocol.  Protocol spec can contain this level of detai=
l. Requirements should indicate that this use case requires this transport =
requirement.
Chair: Agree.

Chair Question2: does light weight transport become the long term goal over=
 TCP?
Rough opinion from floor: Would prefer light weight protocol.=20
More discussion needed.

Chair Question 3: Do we look for an existing light-weight transport? Prefer=
ence is clearly for not inventing a new transport protocol. But before any =
selection can be made requirements need to be drafted. Current protocol req=
uirements doc does not sufficiently address transport requirements.

Droms: What is the IESG/IAB guidance regarding transport protocol selection?
Mark T: Not going to talk to transport ADs or do protocol selectionuntil we=
 have requirements. Once that's there consultation will be made.

Chair: WG needs to contribute transport requirements into existing requirem=
ents draft to answer question 1.

-	ANCP Protocol Security.=20

Chair: No progress on critical item for the protocol. Various aspects have =
impact on security, eg choice of transport. Thread model is need.=20
Mark T: suggests not using TCP MD5.

Chair is looking for volunteers to develop a threat model and derive requir=
ements.=20

- Multicast control.

Chair: Two main functions mentioned for multicast so far i) control of repl=
ication or multicast data plane and ii) multicast group and statistics repo=
rting. Use cases remain to be firmed up. Would like to involve multicast WG=
s in this.
Sesheela: Mboned has multicast session control and admission work going on =
that can go along with this.


--=_mixed 004F2298C22571B5_=
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--=_mixed 004F2298C22571B5_=--




From ancp-bounces@ietf.org Mon Jul 24 10:38:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G51aC-0008QE-2J; Mon, 24 Jul 2006 10:38:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G51aB-0008Q9-ET
	for ancp@ietf.org; Mon, 24 Jul 2006 10:38:55 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G51a9-0007yU-NW
	for ancp@ietf.org; Mon, 24 Jul 2006 10:38:55 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 24 Jul 2006 16:38:53 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6OEcqUO027616; 
	Mon, 24 Jul 2006 16:38:52 +0200 (MEST)
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 24 Jul 2006 16:38:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ANCP] ANCP_IETF66_minutes.txt
Date: Mon, 24 Jul 2006 16:38:46 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D40242792F@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP_IETF66_minutes.txt
Thread-Index: AcavLOsnYJGGeLuaSnWDugF9QFoGiAAAYU+A
From: "Wojciech Dec \(wdec\)" <wdec@cisco.com>
To: <Menachem.Dodge@ecitele.com>
X-OriginalArrivalTime: 24 Jul 2006 14:38:52.0459 (UTC)
	FILETIME=[E22CEFB0:01C6AF2E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: Matthew.Bocci@alcatel.co.uk, alex.zinin@alcatel.com, ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0817636480=="
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0817636480==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6AF2E.E2202631"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6AF2E.E2202631
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Menachem, we'll make the change.
=20
You are correct, the charter does not mention explicitly the DSL Forum
relationship; the minutes contain what was said at the meeting. Despite
this, as I stated during the meeting, it's our goal to closely
collaborate with the DSL Forum via the normal liaison process as well as
joint individual membership between the WG and the DSL forum A&T group.
=20
Regards,
Woj.

________________________________

From: Menachem.Dodge@ecitele.com [mailto:Menachem.Dodge@ecitele.com]=20
Sent: 24 July 2006 16:24
To: Wojciech Dec (wdec)
Cc: alex.zinin@alcatel.com; ancp@ietf.org; Matthew.Bocci@alcatel.co.uk
Subject: Re: [ANCP] ANCP_IETF66_minutes.txt



Hi Wojciech,=20

        Regarding the minutes:=20

        1. I am the (?ECI) person.=20

        2, Regarding the statement  "DSL Forum relationship is mentioned
in the charter". I don't see any mention of the=20
DSL Forum in the charter, would someone be kind enough to point out in
which paragraph it is mentioned.=20

       =20
Best Regards,=20
Menachem Dodge





"Wojciech Dec \(wdec\)" <wdec@cisco.com>=20

24/07/2006 16:58=20

To
<ancp@ietf.org>=20
cc
alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk=20
Subject
[ANCP] ANCP_IETF66_minutes.txt

=09




 Dear All,

Attached please find the ANCP WG meeting minutes from IETF 66.
Please let us know of any corrections that may be due.

A brief summary of the action items :

1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG
ID
2. (Chair) Create new WG mile-stone for delivery of security threat
analysis draft
3. (Chair) Formulate a question to the WG addressing the ANCP
Partitioning work item; functional, port partitioning and redundancy.

I would also like to invite all volunteers who indicated an interest in
taking on the security analysis task to come forward, if they have not
already done so.

Regards,
Woj and Matthew.
<<ANCP_IETF66_minutes.txt>>=20
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



------_=_NextPart_001_01C6AF2E.E2202631
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2>Thanks Menachem, we'll make the change.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2>You are correct, the charter does not mention explicitly the =
DSL Forum=20
relationship; the minutes contain what was said at the meeting. Despite =
this, as=20
I stated during the meeting, it's our goal to closely collaborate with =
the DSL=20
Forum via the normal liaison process as well as joint individual =
membership=20
between the WG and the DSL forum A&amp;T group.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D583413514-24072006><FONT =
face=3DArial=20
size=3D2>Woj.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Menachem.Dodge@ecitele.com=20
[mailto:Menachem.Dodge@ecitele.com] <BR><B>Sent:</B> 24 July 2006=20
16:24<BR><B>To:</B> Wojciech Dec (wdec)<BR><B>Cc:</B> =
alex.zinin@alcatel.com;=20
ancp@ietf.org; Matthew.Bocci@alcatel.co.uk<BR><B>Subject:</B> Re: [ANCP] =

ANCP_IETF66_minutes.txt<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hi Wojciech,</FONT> =
<BR><BR><FONT=20
face=3Dsans-serif size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; Regarding the =
minutes:</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; 1. =
I am the=20
(?ECI) person.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>&nbsp; =
&nbsp; &nbsp;=20
&nbsp; 2, Regarding the statement &nbsp;"DSL Forum relationship is =
mentioned in=20
the charter". I don't see any mention of the</FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D2>DSL Forum in the charter, would someone be kind enough to point =
out in=20
which paragraph it is mentioned.</FONT> <BR><BR><FONT face=3Dsans-serif=20
size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; </FONT><BR><FONT face=3Dsans-serif =
size=3D2>Best=20
Regards,</FONT> <BR><FONT face=3Dsans-serif size=3D2>Menachem=20
Dodge<BR><BR></FONT><BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>"Wojciech Dec =
\(wdec\)"=20
      &lt;wdec@cisco.com&gt;</B> </FONT>
      <P><FONT face=3Dsans-serif size=3D1>24/07/2006 16:58</FONT> </P>
    <TD width=3D"59%">
      <TABLE width=3D"100%">
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
          <TD><FONT face=3Dsans-serif =
size=3D1>&lt;ancp@ietf.org&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
          <TD><FONT face=3Dsans-serif size=3D1>alex.zinin@alcatel.com,=20
            Matthew.Bocci@alcatel.co.uk</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
          <TD><FONT face=3Dsans-serif size=3D1>[ANCP]=20
            ANCP_IETF66_minutes.txt</FONT></TR></TBODY></TABLE><BR>
      <TABLE>
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
          =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT=20
size=3D2><TT>&nbsp;Dear All,<BR><BR>Attached please find the ANCP WG =
meeting=20
minutes from IETF 66.<BR>Please let us know of any corrections that may =
be=20
due.<BR><BR>A brief summary of the action items :<BR><BR>1. (Chair) =
Follow-up=20
request on making draft-ooghe-ancp-framework a WG<BR>ID<BR>2. (Chair) =
Create new=20
WG mile-stone for delivery of security threat<BR>analysis draft<BR>3. =
(Chair)=20
Formulate a question to the WG addressing the ANCP<BR>Partitioning work =
item;=20
functional, port partitioning and redundancy.<BR><BR>I would also like =
to invite=20
all volunteers who indicated an interest in<BR>taking on the security =
analysis=20
task to come forward, if they have not<BR>already done=20
so.<BR><BR>Regards,<BR>Woj and=20
Matthew.<BR>&lt;&lt;ANCP_IETF66_minutes.txt&gt;&gt;=20
<BR>_______________________________________________<BR>ANCP mailing=20
list<BR>ANCP@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/ancp<BR><=
/TT></FONT><BR></BODY></HTML>

------_=_NextPart_001_01C6AF2E.E2202631--


--===============0817636480==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============0817636480==--




From ancp-bounces@ietf.org Mon Jul 24 11:12:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G526i-0006bY-V2; Mon, 24 Jul 2006 11:12:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G526h-0006SD-MT
	for ancp@ietf.org; Mon, 24 Jul 2006 11:12:31 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G526g-00060d-04
	for ancp@ietf.org; Mon, 24 Jul 2006 11:12:31 -0400
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D40242792F@xmb-ams-33b.emea.cisco.com>
To: "Wojciech Dec \(wdec\)" <wdec@cisco.com>
Subject: RE: [ANCP] ANCP_IETF66_minutes.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OFF5C5F0B8.3210C16C-ONC22571B5.00533577-C22571B5.005389F5@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Mon, 24 Jul 2006 18:12:27 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/24/2006 18:20:52,
	Serialize complete at 07/24/2006 18:20:52
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 515708a075ffdf0a79d1c83b601e2afd
Cc: Matthew.Bocci@alcatel.co.uk, alex.zinin@alcatel.com, ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1111362918=="
Errors-To: ancp-bounces@ietf.org

This is a multipart message in MIME format.
--===============1111362918==
Content-Type: multipart/alternative;
	boundary="=_alternative 005389F2C22571B5_="

This is a multipart message in MIME format.
--=_alternative 005389F2C22571B5_=
Content-Type: text/plain; charset="US-ASCII"

Hi Wojciech, 


Thank you kindly. 


Best Regards,
Menachem 




"Wojciech Dec \(wdec\)" <wdec@cisco.com> 
24/07/2006 17:38

To
<Menachem.Dodge@ecitele.com>
cc
<alex.zinin@alcatel.com>, <ancp@ietf.org>, <Matthew.Bocci@alcatel.co.uk>
Subject
RE: [ANCP] ANCP_IETF66_minutes.txt






Thanks Menachem, we'll make the change.
 
You are correct, the charter does not mention explicitly the DSL Forum 
relationship; the minutes contain what was said at the meeting. Despite 
this, as I stated during the meeting, it's our goal to closely collaborate 
with the DSL Forum via the normal liaison process as well as joint 
individual membership between the WG and the DSL forum A&T group.
 
Regards,
Woj.

From: Menachem.Dodge@ecitele.com [mailto:Menachem.Dodge@ecitele.com] 
Sent: 24 July 2006 16:24
To: Wojciech Dec (wdec)
Cc: alex.zinin@alcatel.com; ancp@ietf.org; Matthew.Bocci@alcatel.co.uk
Subject: Re: [ANCP] ANCP_IETF66_minutes.txt


Hi Wojciech, 

        Regarding the minutes: 

        1. I am the (?ECI) person. 

        2, Regarding the statement  "DSL Forum relationship is mentioned 
in the charter". I don't see any mention of the 
DSL Forum in the charter, would someone be kind enough to point out in 
which paragraph it is mentioned. 

 
Best Regards, 
Menachem Dodge




"Wojciech Dec \(wdec\)" <wdec@cisco.com> 
24/07/2006 16:58 


To
<ancp@ietf.org> 
cc
alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk 
Subject
[ANCP] ANCP_IETF66_minutes.txt








 Dear All,

Attached please find the ANCP WG meeting minutes from IETF 66.
Please let us know of any corrections that may be due.

A brief summary of the action items :

1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG
ID
2. (Chair) Create new WG mile-stone for delivery of security threat
analysis draft
3. (Chair) Formulate a question to the WG addressing the ANCP
Partitioning work item; functional, port partitioning and redundancy.

I would also like to invite all volunteers who indicated an interest in
taking on the security analysis task to come forward, if they have not
already done so.

Regards,
Woj and Matthew.
<<ANCP_IETF66_minutes.txt>> 
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp


--=_alternative 005389F2C22571B5_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Wojciech,</font><font size=3> </font>
<br>
<br>
<br><font size=2 face="sans-serif">Thank you kindly. </font>
<br>
<br>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem </font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Wojciech Dec \(wdec\)&quot;
&lt;wdec@cisco.com&gt;</b> </font>
<p><font size=1 face="sans-serif">24/07/2006 17:38</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&lt;Menachem.Dodge@ecitele.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">&lt;alex.zinin@alcatel.com&gt;, &lt;ancp@ietf.org&gt;,
&lt;Matthew.Bocci@alcatel.co.uk&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [ANCP] ANCP_IETF66_minutes.txt</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="Arial">Thanks Menachem, we'll make the change.</font>
<br><font size=3>&nbsp;</font>
<br><font size=2 face="Arial">You are correct, the charter does not mention
explicitly the DSL Forum relationship; the minutes contain what was said
at the meeting. Despite this, as I stated during the meeting, it's our
goal to closely collaborate with the DSL Forum via the normal liaison process
as well as joint individual membership between the WG and the DSL forum
A&amp;T group.</font>
<br><font size=3>&nbsp;</font>
<br><font size=2 face="Arial">Regards,</font>
<br><font size=2 face="Arial">Woj.</font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> Menachem.Dodge@ecitele.com
[mailto:Menachem.Dodge@ecitele.com] <b><br>
Sent:</b> 24 July 2006 16:24<b><br>
To:</b> Wojciech Dec (wdec)<b><br>
Cc:</b> alex.zinin@alcatel.com; ancp@ietf.org; Matthew.Bocci@alcatel.co.uk<b><br>
Subject:</b> Re: [ANCP] ANCP_IETF66_minutes.txt</font><font size=3><br>
</font>
<br><font size=2 face="sans-serif"><br>
Hi Wojciech,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;Regarding the minutes:</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;1. I am the (?ECI) person.</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;2, Regarding the statement &nbsp;&quot;DSL
Forum relationship is mentioned in the charter&quot;. I don't see any mention
of the</font><font size=3> </font><font size=2 face="sans-serif"><br>
DSL Forum in the charter, would someone be kind enough to point out in
which paragraph it is mentioned.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
 &nbsp; &nbsp; &nbsp; &nbsp;<br>
Best Regards,</font><font size=3> </font><font size=2 face="sans-serif"><br>
Menachem Dodge<br>
</font><font size=3><br>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=46%><font size=1 face="sans-serif"><b>&quot;Wojciech Dec \(wdec\)&quot;
&lt;wdec@cisco.com&gt;</b> </font>
<p><font size=1 face="sans-serif">24/07/2006 16:58</font><font size=3>
</font>
<td width=53%>
<br>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=86%><font size=1 face="sans-serif">&lt;ancp@ietf.org&gt;</font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">alex.zinin@alcatel.com, Matthew.Bocci@alcatel.co.uk</font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[ANCP] ANCP_IETF66_minutes.txt</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=49%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
</font><font size=2><tt><br>
 Dear All,<br>
<br>
Attached please find the ANCP WG meeting minutes from IETF 66.<br>
Please let us know of any corrections that may be due.<br>
<br>
A brief summary of the action items :<br>
<br>
1. (Chair) Follow-up request on making draft-ooghe-ancp-framework a WG<br>
ID<br>
2. (Chair) Create new WG mile-stone for delivery of security threat<br>
analysis draft<br>
3. (Chair) Formulate a question to the WG addressing the ANCP<br>
Partitioning work item; functional, port partitioning and redundancy.<br>
<br>
I would also like to invite all volunteers who indicated an interest in<br>
taking on the security analysis task to come forward, if they have not<br>
already done so.<br>
<br>
Regards,<br>
Woj and Matthew.<br>
&lt;&lt;ANCP_IETF66_minutes.txt&gt;&gt; <br>
_______________________________________________<br>
ANCP mailing list<br>
ANCP@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/ancp</tt></font><font size=3><br>
</font>
<br>
--=_alternative 005389F2C22571B5_=--


--===============1111362918==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============1111362918==--




From ancp-bounces@ietf.org Mon Jul 24 11:13:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G527v-0007qA-Ku; Mon, 24 Jul 2006 11:13:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G527u-0007ph-Va
	for ancp@ietf.org; Mon, 24 Jul 2006 11:13:46 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G527t-0006Kd-DZ
	for ancp@ietf.org; Mon, 24 Jul 2006 11:13:46 -0400
To: ancp@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OFA27DCCEA.283212B3-ONC22571B5.004F84D6-C22571B5.0053A777@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Mon, 24 Jul 2006 18:13:43 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/24/2006 18:22:07,
	Serialize complete at 07/24/2006 18:22:07
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: [ANCP] Layer 2 Parameters in the Protocol document
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1853055692=="
Errors-To: ancp-bounces@ietf.org

This is a multipart message in MIME format.
--===============1853055692==
Content-Type: multipart/alternative;
	boundary="=_alternative 0053A775C22571B5_="

This is a multipart message in MIME format.
--=_alternative 0053A775C22571B5_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

        Regarding the document: 
"draft-wadhwa-gsmp-l2control-configuration" and following the questions I 
raised at the meeting in Montreal,
 I would like to request an explanation of how to handle:

        1.  Multiple Vlans in a single encapsulation.
        2.  Multiple Vlans and Multiple encapsulations.



        1. Multiple Vlans in a single encapsulation.

                 a. Should an Access-Loop-Circuit-Id be defined for each 
Vlan which means that this is a many-to-one relationship?
                 b. Should there be more than one Access-Loop-Remote-Id's 
or is one sufficient? If more are needed, how are they associated with an
                     Access-Loop-Circuit-Id?
                 c. Should there be an 
Access-Aggregation-Circuit-Id-Binary and 
Access-Aggregation-Circuit-Id-ASCII for each 
 Access-Loop-Circuit-Id defined?
                         d. I assume there are only one set of "DSL Line 
Attributes" defined which are common to the physical line.

               2. Multiple Vlans and Multiple encapsulations. 
                a.  If the Vlan's are related to different "Access Loop 
Encapsulations" how is this association between Vlan and encapsulation 
shown?
 

Best Regards,
Menachem

--=_alternative 0053A775C22571B5_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Regarding
the document: &quot;draft-wadhwa-gsmp-l2control-configuration&quot; and
following the questions I raised at the meeting in Montreal,</font>
<br><font size=2 face="sans-serif">&nbsp;I would like to request an explanation
of how to handle:</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 1.
&nbsp;Multiple Vlans in a single encapsulation.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 2.
&nbsp;Multiple Vlans and Multiple encapsulations.</font>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; 1.
Multiple Vlans in a single encapsulation.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;a. Should an Access-Loop-Circuit-Id
be defined for each Vlan which means that this is a many-to-one relationship?</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;b. Should there be more than one Access-Loop-Remote-Id's
or is one sufficient? If more are needed, how are they associated with
an</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Access-Loop-Circuit-Id?</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp;c. Should there be an Access-Aggregation-Circuit-Id-Binary
and Access-Aggregation-Circuit-Id-ASCII for each </font>
<br><font size=2 face="sans-serif">&nbsp;Access-Loop-Circuit-Id defined?</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;d. I assume there
are only one set of &quot;DSL Line Attributes&quot; defined which are common
to the physical line.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;2. Multiple Vlans and Multiple encapsulations. </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; a. &nbsp;If the Vlan's are related to different
&quot;Access Loop Encapsulations&quot; how is this association between
Vlan and encapsulation shown?</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br>
<br><font size=2 face="sans-serif">Best Regards,</font>
<br><font size=2 face="sans-serif">Menachem<br>
</font>
--=_alternative 0053A775C22571B5_=--


--===============1853055692==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============1853055692==--




From ancp-bounces@ietf.org Tue Jul 25 12:02:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5PMi-0001Er-T2; Tue, 25 Jul 2006 12:02:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5PMh-0001Em-6f
	for ancp@ietf.org; Tue, 25 Jul 2006 12:02:35 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5PMf-0000at-Oc
	for ancp@ietf.org; Tue, 25 Jul 2006 12:02:35 -0400
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k6PG2VGl011524 for <ancp@ietf.org>; Tue, 25 Jul 2006 18:02:31 +0200
To: ancp@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF5D026CE1.F23848C4-ON802571B6.00576E35-802571B6.0058001F@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel.co.uk
Date: Tue, 25 Jul 2006 17:01:12 +0100
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/25/2006 17:02:30
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Tue Jul 25 12:08:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5PSH-0002OP-Lx; Tue, 25 Jul 2006 12:08:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5PSG-0002OK-DM
	for ancp@ietf.org; Tue, 25 Jul 2006 12:08:20 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5PSE-0001Jz-UC
	for ancp@ietf.org; Tue, 25 Jul 2006 12:08:20 -0400
Received: from bemail01.netfr.alcatel.fr (bemail01.netfr.alcatel.fr
	[155.132.251.32])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k6PG8I4g014662 for <ancp@ietf.org>; Tue, 25 Jul 2006 18:08:18 +0200
In-Reply-To: <OF5D026CE1.F23848C4-ON802571B6.00576E35-802571B6.0058001F@netfr.alcatel.fr>
Subject: Re: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
To: ancp@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF4F5E067F.1D04A433-ONC12571B6.00588FDD-C12571B6.0058A5D8@netfr.alcatel.fr>
From: Emmanuel.Desmet@alcatel.be
Date: Tue, 25 Jul 2006 18:08:16 +0200
X-MIMETrack: Serialize by Router on BEMAIL01/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/25/2006 18:08:17
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Matthew.Bocci@alcatel.co.uk
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Supportive to move this I-D to WG draft,

@+ manu



                                                                                                                                     
                      Matthew                                                                                                        
                      BOCCI/GB/ALCATEL         To:      ancp@ietf.org                                                                
                      @ALCATEL                 cc:                                                                                   
                                               Subject: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?                           
                      25/07/2006 18:01                                                                                               
                                                                                                                                     




At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp





_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 27 06:39:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G63Gy-0006qs-9a; Thu, 27 Jul 2006 06:39:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G63Gw-0006qm-GX
	for ancp@ietf.org; Thu, 27 Jul 2006 06:39:18 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G63Gu-0005Xi-TW
	for ancp@ietf.org; Thu, 27 Jul 2006 06:39:18 -0400
In-Reply-To: <OF5D026CE1.F23848C4-ON802571B6.00576E35-802571B6.0058001F@netfr.alcatel.fr>
To: Matthew.Bocci@alcatel.co.uk
Subject: Re: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF79558D64.C6CD8532-ONC22571B8.00389824-C22571B8.0038CA17@ecitele.com>
From: Menachem.Dodge@ecitele.com
Date: Thu, 27 Jul 2006 13:20:17 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/27/2006 13:47:40,
	Serialize complete at 07/27/2006 13:47:40
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0526527343=="
Errors-To: ancp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0526527343==
Content-Type: multipart/alternative;
	boundary="=_alternative 0038CA13C22571B8_="

This is a multipart message in MIME format.
--=_alternative 0038CA13C22571B8_=
Content-Type: text/plain; charset="US-ASCII"

Hello Matthew,


I support making this draft - draft-ooghe-ancp-framework-00.txt - a 
Working Group document.


Regards,
Menachem Dodge






Matthew.Bocci@alcatel.co.uk 
25/07/2006 19:01

To
ancp@ietf.org
cc

Subject
[ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?






At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward 
as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. 
Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp


--=_alternative 0038CA13C22571B8_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hello Matthew,</font>
<br>
<br>
<br><font size=2 face="sans-serif">I support making this draft - </font><font size=2><tt>draft-ooghe-ancp-framework-00.txt
</tt></font><font size=2 face="sans-serif">- a Working Group document.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Menachem Dodge<br>
</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Matthew.Bocci@alcatel.co.uk</b>
</font>
<p><font size=1 face="sans-serif">25/07/2006 19:01</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">ancp@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[ANCP] draft-ooghe-ancp-framework-00.txt
to WG ID?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>At IETF 66 in Montreal, a significant number of people
at the ANCP working<br>
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward
as<br>
a working group document.<br>
<br>
This e-mail begins a call on whether to make this I-D a WG document. Please<br>
indicate to the list, by Friday 11th August, if you do or do not support<br>
making this a WG document.<br>
<br>
Regards,<br>
<br>
Matthew<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
ANCP mailing list<br>
ANCP@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/ancp<br>
</tt></font>
<br>
--=_alternative 0038CA13C22571B8_=--


--===============0526527343==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============0526527343==--




From ancp-bounces@ietf.org Thu Jul 27 07:34:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G648G-0001rm-T5; Thu, 27 Jul 2006 07:34:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G648F-0001rh-4x
	for ancp@ietf.org; Thu, 27 Jul 2006 07:34:23 -0400
Received: from tcmail33.telekom.de ([217.6.95.240])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G648D-0002DQ-OI
	for ancp@ietf.org; Thu, 27 Jul 2006 07:34:23 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.dmz.telekom.de with
	ESMTP; Thu, 27 Jul 2006 13:34:20 +0200
Received: by S4DE8PSAANS.blf.telekom.de with Internet Mail Service
	(5.5.2653.19) id <PQT9FY2L>; Thu, 27 Jul 2006 13:34:20 +0200
Message-Id: <6439282641581441A36F7F6F83ED2ED2C9E175@S4DE8PSAAFQ.mitte.t-com.de>
From: "Haag, T" <Thomas.Haag@t-systems.com>
To: Matthew.Bocci@alcatel.co.uk
Subject: AW: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Date: Thu, 27 Jul 2006 13:35:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Hello Matthew,=20


I also support making this draft "draft-ooghe-ancp-framework-00.txt" a =
Working Group document.

Regards

Thomas Haag


-----Urspr=FCngliche Nachricht-----
Von: Matthew.Bocci@alcatel.co.uk [mailto:Matthew.Bocci@alcatel.co.uk]=20
Gesendet: Dienstag, 25. Juli 2006 18:01
An: ancp@ietf.org
Betreff: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?

At IETF 66 in Montreal, a significant number of people at the ANCP =
working
group meeting supported moving draft-ooghe-ancp-framework-00.txt =
forward as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. =
Please
indicate to the list, by Friday 11th August, if you do or do not =
support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 27 07:46:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64Jr-0000Yn-3L; Thu, 27 Jul 2006 07:46:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G64Jp-0000Yh-GY
	for ancp@ietf.org; Thu, 27 Jul 2006 07:46:21 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64Jo-00049c-4M
	for ancp@ietf.org; Thu, 27 Jul 2006 07:46:21 -0400
To: ancp@ietf.org
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF4E6F72A0.9FAB3764-ONC22571B8.0037DB13-C22571B8.0040AA0A@ecitele.com>
From: Moti.Morgenstern@ecitele.com
Date: Thu, 27 Jul 2006 14:46:17 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/27/2006 14:54:43
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [ANCP] ANCP_IETF66_minutes
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Hi all,

Regarding item #6 (ANCP MIBs) in the minutes, I wish to suggest my help to
Stefaan in developing the MIB.
I'm currently the editor of ADSL2 MIB and VDSL2 in the ADSL MIB WG.
Please advise in what way I can assist.

Thanks,
Moti Morgenstern

Senior Systems Engineer
ECI Telecom Ltd.


_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 27 08:14:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64kw-0001Gt-RP; Thu, 27 Jul 2006 08:14:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G64kw-0001Go-2F
	for ancp@ietf.org; Thu, 27 Jul 2006 08:14:22 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64kt-0000ST-JR
	for ancp@ietf.org; Thu, 27 Jul 2006 08:14:22 -0400
Received: from mail2.siemens.de (localhost [127.0.0.1])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id k6RCEDsl019038;
	Thu, 27 Jul 2006 14:14:13 +0200
Received: from mchp7wta.ww002.siemens.net (mchp7wta.ww002.siemens.net
	[139.25.131.193])
	by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id k6RCE6id020043;
	Thu, 27 Jul 2006 14:14:13 +0200
Received: from MCHP7RCA.ww002.siemens.net ([139.25.131.170]) by
	mchp7wta.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Jul 2006 14:12:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Date: Thu, 27 Jul 2006 14:12:17 +0200
Message-ID: <B4AB8706B31D6943B60D8D04DEFAE5D2962642@MCHP7RCA.ww002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Thread-Index: AcaxcNfG9UmQO5WVSB+QQD/3Nj3iiAABD+uQ
From: "Voigt, Norbert" <norbert.voigt@siemens.com>
To: <Matthew.Bocci@alcatel.co.uk>
X-OriginalArrivalTime: 27 Jul 2006 12:12:18.0070 (UTC)
	FILETIME=[E78CEB60:01C6B175]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Hi Matthew,=20
I'm also supportive to move this I-D to WG document.

Regards,
Norbert Voigt.


-----Urspr=FCngliche Nachricht-----
Von: Matthew.Bocci@alcatel.co.uk [mailto:Matthew.Bocci@alcatel.co.uk]=20
Gesendet: Dienstag, 25. Juli 2006 18:01
An: ancp@ietf.org
Betreff: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?

At IETF 66 in Montreal, a significant number of people at the ANCP =
working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward =
as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. =
Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew


_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 27 08:18:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64p9-0003rW-8k; Thu, 27 Jul 2006 08:18:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G64p8-0003rQ-2J
	for ancp@ietf.org; Thu, 27 Jul 2006 08:18:42 -0400
Received: from tcmail33.telekom.de ([217.6.95.240])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64p6-0000sy-LO
	for ancp@ietf.org; Thu, 27 Jul 2006 08:18:42 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.dmz.telekom.de with
	ESMTP; Thu, 27 Jul 2006 14:18:35 +0200
Received: by S4DE8PSAANS.blf.telekom.de with Internet Mail Service
	(5.5.2653.19) id <PQT9F78P>; Thu, 27 Jul 2006 14:18:35 +0200
Message-Id: <6439282641581441A36F7F6F83ED2ED2C456B0@S4DE8PSAAFQ.mitte.t-com.de>
From: "Busser, M" <Michael.Busser@t-systems.com>
To: Matthew.Bocci@alcatel.co.uk
Subject: AW: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Date: Thu, 27 Jul 2006 14:18:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Errors-To: ancp-bounces@ietf.org

Hello Matthew,=20

I also support making this draft "draft-ooghe-ancp-framework-00.txt" a =
Working Group document.

Regards

Michael Busser


-----Urspr=FCngliche Nachricht-----
Von: Matthew.Bocci@alcatel.co.uk [mailto:Matthew.Bocci@alcatel.co.uk]=20
Gesendet: Dienstag, 25. Juli 2006 18:01
An: ancp@ietf.org
Betreff: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?

At IETF 66 in Montreal, a significant number of people at the ANCP =
working group meeting supported moving =
draft-ooghe-ancp-framework-00.txt forward as a working group document.

This e-mail begins a call on whether to make this I-D a WG document. =
Please indicate to the list, by Friday 11th August, if you do or do not =
support making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp



From ancp-bounces@ietf.org Thu Jul 27 08:29:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64za-0001lB-TW; Thu, 27 Jul 2006 08:29:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G64zZ-0001l5-TM
	for ancp@ietf.org; Thu, 27 Jul 2006 08:29:29 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64zZ-00029C-RE
	for ancp@ietf.org; Thu, 27 Jul 2006 08:29:29 -0400
Received: from ilsmtp01.ecitele.com ([147.234.1.11])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G64zH-0001wm-9w
	for ancp@ietf.org; Thu, 27 Jul 2006 08:29:12 -0400
In-Reply-To: <OF5D026CE1.F23848C4-ON802571B6.00576E35-802571B6.0058001F@netfr.alcatel.fr>
To: Matthew.Bocci@alcatel.co.uk
Subject: Re: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004
Message-ID: <OF8B3246CB.BDFF9364-ONC22571B8.00447707-C22571B8.004497B0@ecitele.com>
From: Michel.Platnic@ecitele.com
Date: Thu, 27 Jul 2006 15:29:10 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5.3FP1 |
	December 22, 2004) at 07/27/2006 15:37:34,
	Serialize complete at 07/27/2006 15:37:34
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0353542280=="
Errors-To: ancp-bounces@ietf.org

This is a multipart message in MIME format.
--===============0353542280==
Content-Type: multipart/alternative;
	boundary="=_alternative 004497ACC22571B8_="

This is a multipart message in MIME format.
--=_alternative 004497ACC22571B8_=
Content-Type: text/plain; charset="US-ASCII"

Hello Matthew, 
I support moving the draft - draft-ooghe-ancp-framework-00.txt - to a 
Working Group document
Thanks,
Michel. 




Matthew.Bocci@alcatel.co.uk 
25/07/2006 19:01

To
ancp@ietf.org
cc

Subject
[ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?






At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward 
as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. 
Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp


--=_alternative 004497ACC22571B8_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hello Matthew, <br>
I support moving the draft - draft-ooghe-ancp-framework-00.txt - to a Working
Group document</font>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Michel.</font><font size=3> </font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Matthew.Bocci@alcatel.co.uk</b>
</font>
<p><font size=1 face="sans-serif">25/07/2006 19:01</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">ancp@ietf.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[ANCP] draft-ooghe-ancp-framework-00.txt
to WG ID?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>At IETF 66 in Montreal, a significant number of people
at the ANCP working<br>
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward
as<br>
a working group document.<br>
<br>
This e-mail begins a call on whether to make this I-D a WG document. Please<br>
indicate to the list, by Friday 11th August, if you do or do not support<br>
making this a WG document.<br>
<br>
Regards,<br>
<br>
Matthew<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
ANCP mailing list<br>
ANCP@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/ancp<br>
</tt></font>
<br>
--=_alternative 004497ACC22571B8_=--


--===============0353542280==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============0353542280==--




From ancp-bounces@ietf.org Sat Jul 29 00:02:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6g2D-0002aa-L5; Sat, 29 Jul 2006 00:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6g2B-0002aS-Qi
	for ancp@ietf.org; Sat, 29 Jul 2006 00:02:39 -0400
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6g2A-0002i8-AP
	for ancp@ietf.org; Sat, 29 Jul 2006 00:02:39 -0400
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id C0D512D0343;
	Fri, 28 Jul 2006 21:02:37 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 07141-08; Fri, 28 Jul 2006 21:02:37 -0700 (PDT)
Received: from PARBETM2XP (login003.redback.com [155.53.12.55])
	by prattle.redback.com (Postfix) with ESMTP id 5E5212D0345;
	Fri, 28 Jul 2006 21:02:37 -0700 (PDT)
From: "Peter Arberg" <parberg@redback.com>
To: <Matthew.Bocci@alcatel.co.uk>
Subject: RE: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Date: Fri, 28 Jul 2006 21:02:33 -0700
Organization: Redback Networks
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <OF8B3246CB.BDFF9364-ONC22571B8.00447707-C22571B8.004497B0@ecitele.com>
Thread-Index: AcaxeFEDUe4/iW+sT420PhiYu4ugKgBS3ZVw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-Id: <20060729040237.5E5212D0345@prattle.redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: parberg@redback.com
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1414687385=="
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1414687385==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00BE_01C6B289.25A48340"

This is a multi-part message in MIME format.

------=_NextPart_000_00BE_01C6B289.25A48340
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

same for me.
peter


  _____  

From: Michel.Platnic@ecitele.com [mailto:Michel.Platnic@ecitele.com] 
Sent: 27. juli 2006 05:29
To: Matthew.Bocci@alcatel.co.uk
Cc: ancp@ietf.org
Subject: Re: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?



Hello Matthew, 
I support moving the draft - draft-ooghe-ancp-framework-00.txt - to a
Working Group document 
Thanks, 
Michel. 




Matthew.Bocci@alcatel.co.uk 


25/07/2006 19:01 


To
ancp@ietf.org 

cc

Subject
[ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?

	




At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document. Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp




------=_NextPart_000_00BE_01C6B289.25A48340
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D028160204-29072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>same for me.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D028160204-29072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Michel.Platnic@ecitele.com=20
  [mailto:Michel.Platnic@ecitele.com] <BR><B>Sent:</B> 27. juli 2006=20
  05:29<BR><B>To:</B> Matthew.Bocci@alcatel.co.uk<BR><B>Cc:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
draft-ooghe-ancp-framework-00.txt=20
  to WG ID?<BR></FONT><BR></DIV>
  <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hello Matthew, <BR>I =
support=20
  moving the draft - draft-ooghe-ancp-framework-00.txt - to a Working =
Group=20
  document</FONT> <BR><FONT face=3Dsans-serif size=3D2>Thanks,</FONT> =
<BR><FONT=20
  face=3Dsans-serif size=3D2>Michel.</FONT><FONT size=3D3> =
</FONT><BR><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif=20
        size=3D1><B>Matthew.Bocci@alcatel.co.uk</B> </FONT>
        <P><FONT face=3Dsans-serif size=3D1>25/07/2006 19:01</FONT> </P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>ancp@ietf.org</FONT>=20
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>[ANCP]=20
              draft-ooghe-ancp-framework-00.txt to WG=20
        ID?</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT=20
  size=3D2><TT>At IETF 66 in Montreal, a significant number of people at =
the ANCP=20
  working<BR>group meeting supported moving =
draft-ooghe-ancp-framework-00.txt=20
  forward as<BR>a working group document.<BR><BR>This e-mail begins a =
call on=20
  whether to make this I-D a WG document. Please<BR>indicate to the =
list, by=20
  Friday 11th August, if you do or do not support<BR>making this a WG=20
  =
document.<BR><BR>Regards,<BR><BR>Matthew<BR><BR><BR><BR><BR>_____________=
__________________________________<BR>ANCP=20
  mailing=20
  =
list<BR>ANCP@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/ancp<BR><=
/TT></FONT><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00BE_01C6B289.25A48340--




--===============1414687385==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============1414687385==--






From ancp-bounces@ietf.org Sat Jul 29 03:51:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6jbw-0005fk-7D; Sat, 29 Jul 2006 03:51:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6jbv-0005ff-Ks
	for ancp@ietf.org; Sat, 29 Jul 2006 03:51:47 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6jbu-0001Ht-3K
	for ancp@ietf.org; Sat, 29 Jul 2006 03:51:47 -0400
Received: from bemail06.netfr.alcatel.fr (bemail06.netfr.alcatel.fr
	[155.132.251.30])
	by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k6T7pjKG024672; Sat, 29 Jul 2006 09:51:45 +0200
Subject: RE: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?
Date: Sat, 29 Jul 2006 09:51:41 +0200
MIME-Version: 1.0
To: parberg@redback.com, Matthew.Bocci@alcatel.co.uk
From: wim.henderickx@alcatel.be
X-Mailer: Microsoft Outlook v 11.00.8010, MSOC v 2.00.4007.00
Message-ID: <OF7D33438E.6BF46E76-ON422571BA.002B2938@netfr.alcatel.fr>
X-MIMETrack: Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 07/29/2006 09:51:44,
	Serialize complete at 07/29/2006 09:51:44
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Cc: ancp@ietf.org
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0392336272=="
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0392336272==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01D5_01C6B2F4.9907D6F0"

This is a multi-part message in MIME format.

------=_NextPart_000_01D5_01C6B2F4.9907D6F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I also agree to make it a WG document

  _____  

From: Peter Arberg [mailto:parberg@redback.com] 
Sent: zaterdag 29 juli 2006 6:03
To: Matthew BOCCI
Cc: ancp@ietf.org
Subject: RE: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?


same for me.
peter


  _____  

From: Michel.Platnic@ecitele.com [mailto:Michel.Platnic@ecitele.com] 
Sent: 27. juli 2006 05:29
To: Matthew.Bocci@alcatel.co.uk
Cc: ancp@ietf.org
Subject: Re: [ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?



Hello Matthew, 
I support moving the draft - draft-ooghe-ancp-framework-00.txt - to a
Working Group document 
Thanks, 
Michel. 




Matthew.Bocci@alcatel.co.uk 


25/07/2006 19:01 


To
ancp@ietf.org 

cc

Subject
[ANCP] draft-ooghe-ancp-framework-00.txt to WG ID?	

		




At IETF 66 in Montreal, a significant number of people at the ANCP working
group meeting supported moving draft-ooghe-ancp-framework-00.txt forward
as
a working group document.

This e-mail begins a call on whether to make this I-D a WG document.
Please
indicate to the list, by Friday 11th August, if you do or do not support
making this a WG document.

Regards,

Matthew




_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp




------=_NextPart_000_01D5_01C6B2F4.9907D6F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D912265107-29072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I also agree to make it a WG=20
document</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Peter Arberg =
[mailto:parberg@redback.com]=20
<BR><B>Sent:</B> zaterdag 29 juli 2006 6:03<BR><B>To:</B> Matthew=20
BOCCI<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP]=20
draft-ooghe-ancp-framework-00.txt to WG ID?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D028160204-29072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>same for me.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D028160204-29072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Michel.Platnic@ecitele.com=20
  [mailto:Michel.Platnic@ecitele.com] <BR><B>Sent:</B> 27. juli 2006=20
  05:29<BR><B>To:</B> Matthew.Bocci@alcatel.co.uk<BR><B>Cc:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
draft-ooghe-ancp-framework-00.txt=20
  to WG ID?<BR></FONT><BR></DIV>
  <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Hello Matthew, <BR>I =
support=20
  moving the draft - draft-ooghe-ancp-framework-00.txt - to a Working =
Group=20
  document</FONT> <BR><FONT face=3Dsans-serif size=3D2>Thanks,</FONT> =
<BR><FONT=20
  face=3Dsans-serif size=3D2>Michel.</FONT><FONT size=3D3> =
</FONT><BR><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif=20
        size=3D1><B>Matthew.Bocci@alcatel.co.uk</B> </FONT>
        <P><FONT face=3Dsans-serif size=3D1>25/07/2006 19:01</FONT> </P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>ancp@ietf.org</FONT>=20
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD>
          <TR vAlign=3Dtop>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD><FONT face=3Dsans-serif size=3D1>[ANCP]=20
              draft-ooghe-ancp-framework-00.txt to WG=20
        ID?</FONT></TD></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><=
FONT=20
  size=3D2><TT>At IETF 66 in Montreal, a significant number of people at =
the ANCP=20
  working<BR>group meeting supported moving =
draft-ooghe-ancp-framework-00.txt=20
  forward as<BR>a working group document.<BR><BR>This e-mail begins a =
call on=20
  whether to make this I-D a WG document. Please<BR>indicate to the =
list, by=20
  Friday 11th August, if you do or do not support<BR>making this a WG=20
  =
document.<BR><BR>Regards,<BR><BR>Matthew<BR><BR><BR><BR><BR>_____________=
__________________________________<BR>ANCP=20
  mailing=20
  =
list<BR>ANCP@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/ancp<BR><=
/TT></FONT><BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_01D5_01C6B2F4.9907D6F0--



--===============0392336272==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www1.ietf.org/mailman/listinfo/ancp

--===============0392336272==--





