RE: [L2CP] Working group name: decision time

"Jerome Moisand" <jmoisand@juniper.net> Tue, 04 April 2006 13:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQlzn-0004uc-J3; Tue, 04 Apr 2006 09:54:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQlzm-0004re-I5 for l2CP@ietf.org; Tue, 04 Apr 2006 09:54:58 -0400
Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQlzk-0006W8-8h for l2CP@ietf.org; Tue, 04 Apr 2006 09:54:58 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by borg.juniper.net with ESMTP; 04 Apr 2006 06:54:56 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.03,164,1141632000"; d="scan'208"; a="540930713:sNHT37357684"
Received: from antipi.jnpr.net ([10.10.2.34]) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Apr 2006 09:54:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L2CP] Working group name: decision time
Date: Tue, 04 Apr 2006 09:54:11 -0400
Message-ID: <6B8F46B46D292A438250E42591ABB59D07A6949E@antipi.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [L2CP] Working group name: decision time
Thread-Index: AcZX3m43KmZdA0z+R/i6BCIy9he6QwADjGuQ
From: Jerome Moisand <jmoisand@juniper.net>
To: l2CP@ietf.org
X-OriginalArrivalTime: 04 Apr 2006 13:54:54.0827 (UTC) FILETIME=[5A2BFBB0:01C657EF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc:
X-BeenThere: l2cp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 2 Control Protocol Discussion List <l2cp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l2cp>
List-Post: <mailto:l2cp@ietf.org>
List-Help: <mailto:l2cp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=subscribe>
Errors-To: l2cp-bounces@ietf.org

I'm comfortable with the "AN" characterization, which refers to existing
DSL-Forum terminology, while keeping it more general than DSL.

I think ANCO would be better then. Once again, it would be a bad thing
to infer that we're defining a brand new protocol. 

What bugs me a little bit is that it would be great to add a qualifier
to better express the dynamic, transactional & inband nature of the
concept. Inband (ANIC)? Dynamic (ANDC)? Real-time (ANRC)? I can't find
the right word... 

-----Original Message-----
From: Matthew.Bocci@alcatel.co.uk [mailto:Matthew.Bocci@alcatel.co.uk] 
Sent: Tuesday, April 04, 2006 7:53 AM
To: l2CP@ietf.org
Subject: [L2CP] Working group name: decision time

All,

We've had a fairly lengthy discussion on the potential names for the
working group.

There seems to be a reasonable number of people in favour of either BAMP
or
GAMP. However, there also seem to be a reasonable number of people who
would not like to see 'management' in the WG name, as it would more
accurately be described as a control protocol.

Of the other names, there were few that included control, did not clash
with other acronyms, and did not say "layer 2 control" (which was one of
the problems with L2CP).





In an attempt to come to a conclusion on this, please can you indicate
your
preference between the following:


ANCO (Access Node Control)


ANCP (Access Node Control Protocol)





Thanks,





Matthew









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

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