Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-Privacy] FW: [802SEC] Proposed PAR: P802c - Overview and Architecture - Amendment: Local Media Access Control (MAC) Addressing



The IEEE RAC currently sells CIDs for a one-time fee of USD$625 (see http://standards.ieee.org/develop/regauth/cid/ )

 

It sounds like there is some expectation in this group and in the more general industry community to use a CID number space on a casual basis without perhaps acquiring a value from the IEEE RAC CID pool. That does not sound consistent with IEEE RAC administration of that number space.

 

Yes, the IEEE RAC language says that numbers used in the CID number space are not guaranteed to be globally unique, but I see that the IEEE RAC does sell numbers in that CID number pool space, so you may very well see resistance on planned obviation of the IEEE RAC administration of the CID number space.

 

Then again, perhaps I misunderstand and someone can correct my ignorance.

 

Thanks,
Phillip Barber

 

From: Dan Harkins [mailto:dharkins@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, October 01, 2014 4:43 PM
To: STDS-802-PRIVACY@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-Privacy] FW: [802SEC] Proposed PAR: P802c - Overview and Architecture - Amendment: Local Media Access Control (MAC) Addressing

 

 

  Hello,

 

  I encourage everyone to read these guidelines:

 

 

It is my understanding that assignment of a CID gives the assignee ZERO 

addresses (see table 1). The CID is assigned for "non-address applications". It

states:

 

"A CID has the X bit equal to one and consequently that places any address with the

CID as its first three octets in the local address space (U/L = 1). Local addresses are

not globally unique, but a network administrator is responsible for assuring that any 

local addresses assigned are unique within the span of use. (Uniqueness of local

addresses typically does not need to extend beyond a router.)"

 

These guidelines do not seem to create any assumption that there are any limits

use of addresses from the local address space (U/L = 1) that may end up having the

CID as its first three octets.

 

  My input to this proposed 802c project is to not create any rules for using the local

address space. Specifically:

 

  1. do not allocate portions of the local address space for any specific purpose;

  2. do not attempt to "organize" the local address space;

  3. do not reserve and assign addresses out of the local address space;

  4. do not attempt to turn a CID into an OUI. The CID was assigned for

      "non-address applications" and if the assignee wants to do "address

      applications" it should get an OUI. 

 

Address applications that use an address from the local address space (U/L = 1)

are free to choose any of the 2^46 possible addresses from the local address

space pool.

 

  regards,

 

  Dan.

 

On 10/1/14 12:14 PM, "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@xxxxxxxxxxxxxxxx> wrote:

 

All,

 

As mentioned by Max, this proposed 802c PAR is relevant to the discussions we are currently having about the use of the local MAC domain. The intention of the proposed project is to describe the rules for assigning local MAC addresses:

 

From PAR:

“5.2.b. Scope of the project:

The amendment will provide recommendations and rules for using the local address space. This will allocate a portion of the address space for protocols using an IEEE Registration Authority assigned Company ID. Another portion of the local address space will be allocated for assignment by local administrators.”

 

From CSD:

“A first step in enabling protocols for claiming or assignment of Local MAC addresses is to organize the MAC address space so that entities can be assigned a block of the Local Address space through the Company ID (CID) as a default. Another part of the space will be defined for local administration.”

 

It is assumed that the Privacy group should be able to leverage from this project/specification, so we should consider providing inputs.

 

Juan Carlos

 

From: Riegel, Maximilian (NSN - DE/Munich) [mailto:maximilian.riegel@xxxxxxx]
Sent: Monday, September 29, 2014 4:10 AM
To: STDS-802-PRIVACY@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-Privacy] FW: [802SEC] Proposed PAR: P802c - Overview and Architecture - Amendment: Local Media Access Control (MAC) Addressing

 

FYI, for the case you are neither subscribed to the [802SEC] list nor to the [802.1] list.

The project may provide the basic rules and protocols for dynamically assigning MAC addresses.

And the project may appreciate input on the privacy use case. Privacy is currently not mentioned in the PAR.

 

Bye

Max

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@xxxxxxxx] On Behalf Of ext Glenn Parsons
Sent: Friday, September 26, 2014 22:07
To: STDS-802-SEC@xxxxxxxxxxxxxxxxx
Subject: [802SEC] Proposed PAR: P802c - Overview and Architecture - Amendment: Local Media Access Control (MAC) Addressing

 

 

Folks,
 
The July 802.1 plenary authorized the 802.1 interim to draft a PAR & CSD for on the local address space.  The proposed PAR for P802c is posted here:
 
http://www.ieee802.org/1/files/public/docs2014/new-addresses-thaler-local-address-par-v01.pdf 
 
The  new 'CSD' is here:
 
http://www.ieee802.org/1/files/public/docs2014/new-addresses-thaler-local-address-csd-v01.pdf 
 
These are for pre-circulation to meet the 30-day requirement for November plenary EC approval to forward to NesCom.
 
Cheers,
Glenn.

 

 

--

Glenn Parsons - Chair, IEEE 802.1

glenn.parsons@xxxxxxxxxxxx

+1-613-963-8141

 

---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.