Assignment of OSI NSAP Addresses (osinsap) Charter_ Chair(s): Richard Colella, colella@osi3.ncsl.nist.gov Mailing Lists: General Discussion: ietf-osi-nsap@osi3.ncsl.nist.gov To Subscribe: ietf-osi-nsap-request@osi3.ncsl.nist.gov Description of Working Group: The OSI NSAP Guidelines Working Group will develop guidelines for NSAP assignment and administration (AKA, the care and feeding of your NSAPs). Assuming use of existing NSAP address standards, there are two questions facing an administration: o Do I want to be an administrative authority for allocating NSAPs? - how do I become an administrative authority? *what organizations should expect to be an ``administrative authority'' in the GOSIP version 2.0 address structure? *where do I go to become an administrative authority? - what are the administrative responsibilities involved? *defining and implementing assignment procedures? *maintaining the register of NSAP assignments. *what are the advantages/disadvantages of being an administrative authority? o Whether NSAPS are allocated from my own or some other administrative authority, what are the technical implications of allocating the substructure of NSAPs? - what should be routing domains? *implications of being a separate routing domain (how it will affect routes, optimality of routes, firewalls and information hiding). *organizing routing domains by geography versus by organization versus by network topology.... - within any routing domain, how should areas be configured? *(same implications as above). Goals and Milestones: Dec 1990 Produce a paper describing guidelines for the acquisition and administration of NSAP addresses in the Internet. 1 Dec 1990 Have the paper published as an RFC. Dec 1990 Have the paper incorporated, in whole or in part, into the ``GOSIP User Guide'' and the FNC OSI Planning Group document. 2