Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/mhsds/mhsds-minutes-93jul.txt

Text File | 1993-09-22 | 14KB | 328 lines

CURRENT_MEETING_REPORT_

Reported by Keven Jordan/Control Data Systems

Minutes of MHS-DS Working Group (MHSDS)


Introductions and Administrivia

The meeting opened with participant introductions and statements of
interests in MHS-DS and Project Long Bud.  The minutes from the Columbus
IETF were then approved.  It was pointed out that the MHSDS Working
Group is now under the new Service Applications Area with Dave Crocker
as the SAP Area Director.


Action Items

   o Eight Internet-Drafts were updated by Steve Kille.

   o Three of the Internet-Drafts were recommended to be progressed as
     Proposed Standards, after some minor editorial changes:
     ``Representing the O/R Address hierarchy in the Directory
     Information Tree''
     ``Representing Tables and Subtrees in the Directory''
     ``Use of the Directory to support mapping between X.400 and RFC 822
     Addresses''

   o The Internet-Draft, ``MHS use of Directory to support MHS
     Routing,'' was recommended to be published as an Experimental RFC
     after minor editorial changes.
     Although there are some minor editorial and technical errors, no
     substantive errors exist in this document.  This document now needs
     some higher degree of visibility.  Two independent implementations
     already exist and provide proof of the basic concepts.  Project
     Long Bud will show if the concepts scale well by deploying MHS-DS
     in the Internet.  The working draft is stable enough to be
     published as an RFC. The Experimental status is initially
     appropriate since Long Bud feedback might result in important
     changes.  The final goal is to place the routing document onto the
     standards track.

   o The ``Simple Profile'' document is a facilitating document and it
     should be dropped once the pilot is further along and
     implementations become more mature.  Most of the content of this
     document can be merged into the routing document, specifying some
     of the functionality as mandatory and some as optional.  This has
     been done for other Internet protocol specifications.

   o It was suggested that an acronym be created for the document set
     (e.g.  MIME), as RFC numbers change, but the acronym would continue
     to be meaningful.


   o Summary of documents and the working group's recommendations for
     progression:

      -  draft-ietf-mhsds-infotree-03, ``Representing the O/R Address
         hierarchy in the Directory Information Tree,'' progress as
         Proposed Internet Standard.

      -  draft-ietf-mhsds-subtrees-03, ``Representing Tables and
         Subtrees in the Directory,'' progress as Proposed Internet
         Standard.

      -  draft-ietf-mhsds-supmapping-03, ``Use of the Directory to
         support mapping between X.400 and RFC 822 Addresses,'' progress
         as Proposed Internet Standard.

      -  draft-ietf-mhsds-routdirectory-03, ``MHS use of Directory to
         support MHS Routing,'' progress as Experimental Specification.

      -  draft-ietf-mhsds-822dir-03, ``Use of the Directory to support
         routing for RFC 822 and related,'' needs more review and
         discussion.

      -  draft-ietf-mhsds-convert-01, ``MHS use of Directory to support
         MHS Content Conversion,'' needs more review and discussion.

      -  draft-ietf-mhsds-mhsprofile-03, ``A simple profile for MHS use
         of Directory,'' informational document to be dropped
         eventually.

      -  draft-ietf-mhsds-long-bud-intro-00, ``Introducing Project Long
         Bud,'' to be edited and reposted as an Internet-Draft.  Will be
         progressed as an Informational RFC as soon as possible.


Summary of Actions from Last Meeting

   o Kevin Jordan to write an Internet-Draft providing an overview of
     the main set of MHS-DS RFCs.  Status:  not done, but some progress
     has finally been made.

   o Harald Alvestrand to write pseudo code for the routing document.
     Status:  not done.

   o Steve Kille to update the document set and repost as
     Internet-Drafts.  Status:  done.

   o Jim Romaguera to coordinate the writing of Project Long Bud
     definition and participation document(s).  Status:  done.  The
     ``Introduction to Project Long Bud'' document was written and
     submitted as an Internet-Draft.  Sylvain Langlois is the principal
     editor.

   o Urs Eppenberger to write specifications for a tool which can be
     used to browse and verify X.500 routing and address mapping
     information.  Status:  not done.  This tool is desirable but Urs
     can not commit the time to write its specification.

   o Panos Tsigaridas to write specifications for, and begin
     implementation of, tools for synchronizing X.500 directory
     information with GO-MHS routing and mapping tables.  Status:  done.
     A beta version of a tool for reading information from the directory
     and generating GO-MHS tables can be found on the MHS-DS file
     server.

   o Kevin Jordan and Long Bud Design Team to prepare an informal MHS-DS
     demonstration at IETF in Amsterdam.  Status:  done.  Kevin
     demonstrated live MHS-DS technology and tools in the public
     terminal room of the RAI Conference Center.


Long Bud Report

   o The meeting participants reviewed the extent of MHS-DS information
     available in the Internet DIT.

   o All of the US MTA and organizational information provided in the
     routing documents available from the University of Wisconsin has
     been added under c=US. However, it seems that most of the MTAs
     registered under PRMD=XNREN no longer exist; most do not respond to
     connection requests.  Perhaps the overall state of PRMD=XNREN needs
     to be reviewed.

   o Countries in the DIT having MHS-DS routing entries include:  the
     United States (US), Great Britain (GB), Denmark (DK), Germany (DE),
     Switzerland (CH), Spain (ES), Portugal (PT) and France (FR).


Review of ``Introduction to Project Long Bud''

   o A question was asked concerning whether Long Bud participants
     should use static tables as the primary source of routing
     information and fall back on X.500, or whether X.500 should be the
     primary source of routing information with fall-back to static
     tables.  The group concluded that the real aim of Project Long Bud
     is to prove the MHS-DS technology.  Therefore, participants should
     use the Open Community Routing Tree in the X.500 DIT as the primary
     source of routing information.  This tree, possibly combined with
     private routing trees, can also provide default routes to the rest
     of the GO-MHS community to provide full connectivity.

   o It was explained that a routing entry within the DIT could point to
     a relay MTA that knows about the WEPs, and the WEPs can reach
     everyone.

   o Initially, Long Bud participants probably should not configure WEPs
     as Long Bud MTAs, as Long Bud is a pilot project whose purpose is
     ``proof of concept.''  Consequently, it is experimental in nature,
     and WEPs should be providing a reliable, production-level service.

   o The `Benefits' section of the Long Bud Internet-Draft should not be
     the last section in the document.  It should be moved to the
     beginning because it is one of the most important aspects of the
     document.

   o The Long Bud Internet-Draft will be updated to document the
     existence of the Project Long Bud `Status Report'.

   o If a country or ADMD cannot establish its own entry in the DIT then
     a skeletal entry will be added and managed until the rightful owner
     asks to administer its own entry.  Some people questioned whether
     this could really be done, in general, for country entries.

   o The `Open Tree' must be populated with entries for MTAs that are
     willing to accept calls from any other MTAs in the Long Bud
     community.

   o Policy - People who are responsible for parts of the DIT must take
     responsibility for managing the data and for providing a good
     quality of service.

   o The Long Bud Internet-Draft will be updated and redistributed by
     the middle of August.

   o The MHS-DS file-server will be updated to include all Long Bud
     documentation and public domain tools.

   o It was suggested that MHS-DS object class and attribute definitions
     for Quipu oidtable files be included on the file server.


Implementations and Tools

The current status of MHS-DS implementations and tools was reviewed.
The Long Bud Status Report will provide details.  The Status Report will
also be updated periodically to reflect the current status.


DIT QOS

Reliability of the DSAs:


   o MHS-DS requires the Internet DSA network to provide a good quality
     of service.

   o The current QOS provided by the Internet DSA network is marginal at
     best.  The US root-level DSAs seem to be particularly problematic,
     especially the DSAs which hold the top-level US domains under
     O=Internet.

   o These problems might be solved by moving responsibility for
     top-level information to an organization which is funded well
     enough to provide good QOS. InterNIC probably qualifies, and has
     expressed an interest in providing this service.


Updated MHS-DS Internet-Drafts

Steve Kille briefly described what changes had been made to the MHS-DS
Internet-Drafts since the previous revisions.  Most of the changes were
editorial in nature.  A very few were more substantial.  For example:


   o Diagram change in the routing document.

   o The representation for personal name was changed.  An RDN with
     multiple AVAs is now used instead of the RFC 1327 representation
     used previously.

   o O/R address syntax has been aligned to ISO syntax.


Some issues were raised on the routing document:


   o The need for shared bilateral tables was introduced as a new
     concept.  It was recommended that the bilateralTable attribute be
     changed to a sequence of DNs.  This would allow a community of
     MTAs, e.g.  the GO-MHS community, to share a potentially large
     table of information about MTAs.  This could be used, for example,
     to establish a basis for deciding whether or not a connection
     request should be accepted or rejected.  If an MTA outside of the
     community attempts to create a connection to an MTA within the
     community, the internal MTA could reject the connection after
     discovering that the caller is not registered in the shared
     bilateral table.
     In addition to using the shared table, some MTAs might also have a
     need for maintaining a bilateral table which records agreements
     which are truly bilateral.
     Thus, there appears to be a legitimate need for defining the
     bilateralTable attribute as a sequence of DNs.  It was decided that
     this should be discussed further on the mailing list.

   o `Next Tree First' routing failure action when the top of a private
     routing tree is reached needs further discussion.  This change
     needs to be discussed off-line.  Steve, Harald, Kevin and Julian
     (in absentia) will discuss this.

   o It was pointed out that an `Initiator Calling Address' attribute
     may be needed.  This will be discussed further on the mailing list.



Tutorial BOF

A tutorial BOF was scheduled for late in the afternoon.  Thanks to Kevin
for giving the tutorial on such short notice.  It was well received.



Planning for the Next Meeting

   o MHS-DS will schedule two time slots at the Houston IETF meeting.

   o Four of the Internet-Drafts should have been progressed as RFCs by
     then.

   o Progress on Long Bud will be reviewed.

   o A new revision of the ``Introduction to Project Long Bud''
     Internet-Draft will have been distributed, and its disposition will
     be discussed.

   o The remaining four MHS-DS Internet-Drafts will be discussed.


Attendees

Harald Alvestrand        [e-mail]
Per Andersson            [e-mail]
Piet Bovenga             [e-mail]
C. Allan Cargille        [e-mail]
Robert Cooney            [e-mail]
David Crocker            [e-mail]
Urs Eppenberger          [e-mail]
Tony Genovese            [e-mail]
Jan Hansen               [e-mail]
Steven Horowitz          [e-mail]
Jeroen Houttuin          [e-mail]
Erik Huizer              [e-mail]
Ola Johansson            [e-mail]
Kevin Jordan             [e-mail]
Peter Jurg               [e-mail]
Anders Karlsson          [e-mail]
Steve Kille              [e-mail]
Paul Klarenberg          [e-mail]
Bruno Koechlin           [e-mail]
Arnold Krechel           [e-mail]
Sylvain Langlois         [e-mail]
Erik Lawaetz             [e-mail]
Paul Lustgarten          [e-mail]
Ignacio Martinez         [e-mail]
Linda Millington         [e-mail]
Paul-Andre Pays          [e-mail]
Catherine Pierre-Radenac [e-mail]
Jim Romaguera            [e-mail]
Marjo Rottschaefer
Panos-Gavriil Tsigaridas [e-mail]
Eftimios Tsigros         [e-mail]
Paul Vetter
Peter Yee                [e-mail]
Steve Zeber              [e-mail]