CURRENT_MEETING_REPORT_


Reported by Richard Colella/NIST

MINUTES

This was the initial meeting of the OSI NSAP Guidelines Working Group.
The chairman, Richard Colella opened the meeting by distributing and
reviewing the working group charter.  A question was raised about the
application of the groups work to the European part of the Internet.
Although this remains an open issue the discussion in the group, at this
time, will be limited to the US Internet.  Another issue was raised
about possible duplication of work with respect to the GSA guidelines on
administration authorities.  It was determined that the group planed to
go beyond the GSA guidelines and that there should not be any major
duplication of current work.

Since the groups orientation is towards the NSAP structure specified in
GOSIP Version 2, Richard Colella presented a review of the NSAP
structure.  From the review and discussion the group agreed that all
issues dealing with the fields from the Administrative Authority to the
left are administrative and those from the Routing Domain to the right
are technical.

The group determined eight issues or questions that need to be resolved
or answered.  The issues are:

  1. The use of 47 0005 NSAPs by US Non-Government organizations.
  2. The use of 47 0005 NSAPs by Non-US organizations.
  3. The DoD NSAP structure vs the Internet structure and possible
     interoperability problems.
  4. The relationship of GSA to the Internet.
  5. Possible technical repercussions of NSAP deployment.
  6. Who gets the Administrative Authority and the authority to define
     routing domains and area?
  7. How can the Internet topology be mapped onto IS-IS routing?
  8. The lack of an inter-domain protocol.

The remaining time in the meeting was spend discussing issues 1,2,3,4
and 7.  The main points of the discussions are outlined below.

Issue 4 - Relationship of GSA to the Internet.


   o GSA is the authority for Administrative Authority field assignment
     under 47 0005.
   o Government organizations request an AA field assignment from GSA.
   o GSA returns an AA value or a reason why a value was not assigned.


Issue 1 - The use of 47 0005 by US non-Government organizations.

                                   1






   o There is no problem with US non-Government organizations using
     NSAPs under 47 0005.
   o A government agency may delegate authority for an AA to the
     Internet.  It is not known who would administer that AA but the
     group should probably make a recommendation.


Issue 2 - The use of 47 0005 by non-US organizations.


   o European countries require End Systems to have NSAPs derived from
     their country codes.
   o The AA for the US non-Government organizations could be extended
     for use by non-US organizations as long as they prescribed to the
     rules and procedures.  There are no technical problems associated
     with this solution but there may be administrative ones.
   o Need to figure out how to deal with this issue.


Issue 3 - DoD NSAP structure vs Internet structure and interoperability


   o 47 0005 will probably work for DoD fixes assets but might not work
     for mobile ones.
   o DoD has not determined what to do with 47 0006.


Issue 4 - Mapping Internet Topology onto IS-IS Routing


   o Need to take a piece of the Internet and map it into OSI. It is an
     ugly process but it needs to be done.
   o One problem is that no one has the big picture.
   o Discussed the transition from DECNET Phase 4 to Phase 5 and the
     problems associated with the transition.
   o Tony Hain presented DoE's model.


The meeting adjourned with plans to hold an informal lunch meeting to
discuss these issues further.


ATTENDEES

   Almquist, Philip           almquist@jessica.stanford.edu
   Ballard, Bare              bare%hprnd@hplabs.hp.com
   Case, Jeff                 case@utkux1.utk.edu
   Cerf, Vint                 vcerf@nri.reston.va.us
   Colella, Richard           colella@osi3.ncsl.nist.gov
   Deboo, Farokh              sun!iruucp!ntrlink!fjd
   Farinacci, Dino            dino@bridge2.3com.com
   Galvin, James              galvin@tis.com

                                   2






Gardner, Ella              epg@gateway.mitre.org
Gan, Der-Hwa               no email
Glappa, Adrianne           no email
Goguely, Herve             rvg@bridge2.3com.com
Gross, Martin              martin@protolaba.dca.mil
Hain, Tony                 hain@nmfecc.arpa
Heinanen, Juha             jh@funet.fi
Hua, Binh                  no email
Hytry, Tom                 tlh@iwlcs.att.com
Jensen, Phil               jensen@fsu1.cc.fsu.edu
Katz, Dave                 dkatz@merit.edu
Lazear,Walt                lazear@gateway.mitre.org
Love, Paul                 loveep@sds.sdsc.edu
Marcinkevicz, Mike         mdm@gumby.dsd.trw.com
McCloghrie, Keith          sytek!kzm@hplabs.hp.com
Mills, Cyndi               cmills@bbn.com
Minshall, Greg             minshall@kinetics.kinetics.com
Morris, Dennis             morrisd@imo-uvax.dca.mil
Nitzan, Becca              nitzan@nsipo.nasa.gov
Sheridan, Jim              jsherida@ibm.com
Showalter, Jim             gamma@mintaka.dca.mil
Shue, Chi                  chi@osf.org
Stursa, Scott              xndmis14@servax.bitnet
Winkler, Linda             b32357@anlvm.ctd.anl.gov
Youssef, Mary              mary@ibm.com



                                3