OSI Integration Area Director(s): o David M. Piscitello: dave@sabre.bellcore.com o Erik Huizer: Erik.Huizer@surfnet.nl Area Summary reported by Dave Piscitello/Bellcore and Erik Huizer/SURFnet The OSI area contains the following working groups: NOOP Network Osi Operations MPSNMP SNMP over a Multi-protocol Innternet OSI-DS OSI Directory Services MHS-DS Message Handling Service Usage of Directory Services X.400OPS X.400 Operations MIMEMHS MIME to MHS Mapping ODA Office Documentation Architecture The OSI General Working Group has been disbanded. Related working groups: DISI Directory Information Services Infrastructure Working Group (report under User Services area) BOFs in the OSI Integration Area held in Boston. SWIP Shared Whois Information Project UDI Universal Document Identifiers Related BOF: 1 NIR Networked Information Retrieval BOF (report under User Services area) Shared Whois Information Project BOF (SWIP) This BOF was organised by Merit to discuss the possibilities for using X.500 to set up a shared whois like service between the Major network coordination centers (currently there are 3: Ripe NCC, GSI- NIC, Merit) in the Internet. This is meant for easy access and exchange of network management data. Which ip address belongs to who, what point of contact, etc. The goals of the SWIP BOF were to a) present the idea and project that Merit had conceived of to converge the network data stored by GSI-NIC, RIPE, and Merit. b) get general agreement on the idea and the method being used c) define requirements for a shared whois database d) get consensus on the need for a distributed whois database of networks and a consensus that the platform be X.500. Most of these goals were achieved. There was a very clear consensus from the attendees that a distributed whois database of networks should be implemented, should be done in X.500, and that it should be done ``right''. It was further decided that Merit should proceed with their X.500 project to converge the network data currently available from RIPE, GSI-NIC, and Merit, and for them to put into place a procedure to keep the data converged until the distributed whois database is in place and working. There is an action item to combine the two X.500 architectural models presented in the bof pertaining to a distributed model for network data. Universal Document Identifiers BOF (UDI) This Group discussed naming issues intended to support the discovery and access of resources in an Internet environment. It was agreed that the term ``Uniform Resource Locator'' (URL) would be used to refer to standardized identifiers which specify location information for resources. The discussion of other aspects of the naming problem was deferred until a later meeting. A document written by Tim Berners-Lee (timbl@info.cern.ch) proposing a standard for URLs was discussed and the syntax and general content of the document was accepted with some revisions. The revised document will be made available from info.cern.ch and circulated to the list below for further discussion. The Group decided to draw up a charter and form an IETF working group on this issue. The mailing list for discussion of URL design issues will be ``ietf-url@merit.edu''. This list will be archived on the anonymous FTP archive on ``merit.edu''. MHS-DS Working Group (MHSDS) 2 The MHS-DS Working Group met at JENC-3 in Innsbruck, Austria in May. A small group of technical experts met once to discuss editorial and technical revisions to the set of seven Internet Drafts being written by the Group. In addition, an open meeting of MHS-DS was held to present general concepts to a broad cross section of the European R&D community. An open discussion followed, and valuable comments were contributed to the Internet Drafts. The focus of the third meeting of MHS-DS (Boston) was on editing the seven Internet Drafts (listed below). We went through the documents, page by page, and contributed both simple editorial changes as well as some recommendations for minor technical revisions. As a result, three of the documents will be progressed as Experimental Standards, and the other four will be cycled through another round of review after they are revised. In addition, two new documents will be produced: a general overview of the whole set, and a document which focuses upon the subject of Content Conversion. The document status follows: 1. Representing Tables and Subtrees in the Directory status: revise and progress as Experimental Standard 2. Representing the O/R Address Hierarchy in the Directory Information Tree status: revise and progress as Experimental Standard 3. MHS use of Directory to support MHS Routing status: revise and cycle as an Internet Draft 4. Use of the Directory to support mapping between X.400 and RFC 822 Addresses status: revise and progress as Experimental Standard 5. MHS use of the Directory to support distribution lists status: revise and cycle as an Internet Draft. 6. A simple profile for MHS use of Directory status: revise and cycle as an Internet Draft (depends upon 3) 7. Use of the Directory to support routing for RFC 822 and related protocols status: revise and cycle as an Internet Draft. New documents to be produced: 1. Overview of Document Set. 2. MHS use of the Directory to support Content Conversion. As a final note: The MHS-DS Charter will be revised to add the two new documents and also to add the following two features: 3 1. MHS-DS will coordinate piloting of MHS use of the Directory. 2. MHS-DS will specify requirements for tools which facilitate interworking between X.500-capable MTA's and MTA's which are not X.500-capable. MIME-MHS Interworking Working Group (MIMEMHS) There have been two papers produced since the last meeting: 1. X.400/MIME body equivalence Harald Tveit Alvestrand, Steven Thompson. 2. Mapping between X.400 and RFC-822 Message Bodies, Harald Alvestrand et al. Several mappings have been defined, and for those without a clear X.400(88) equivalent there is a trapdoor/catchall External bodypart defined in X.400: EBP-mime-body-part. In the other direction the trapdoor in MIME is a new Mime subtype: application/x400-bp. The issues are: o How to get vendors to register OIDs as well as the equivalent MIME subtype with the IANA. o How to manage IANA registration of different versions of BPs like WP5.0 and WP5.1. o How to handle mapping in X.400(84)? - Simplest case single BP IA5. - T.61 strings in header vs RFC 1327 needs resolving. - Three-party mail issue (mime-X.400(88)-X.400(84)). o Automatic OID assignment for registered subtypes. o Appendix with OIDs defined. o Security: viruses will be gatewayed too, not solved in this paper. o Criticality of header extensions. The issues will be resolved by E-mail in the next couple of months. Both documents will be forwarded as Proposed Standard RFCs. Network OSI Operations Working Group (NOOP) The Group reviewed the status of RFC 1139, CLNP ping, and agreed to, (a) eliminate the short-term solution, and (b) align/revise the long-term, solution to match the ISO PDAM expected from ISO next week. A new RFC 4 will be produced. Since this is an integral part of the tools RFC, NOOP expects to process this rapidly. Work continues on the OSI Tools RFC. The Group also reviewed a list from RARE identifying the ten most desirable Managed Objects from the CLNP MIB, and reacted favorably to the selection of OSI connectionless transport as a means of mapping SNMP onto OSI. The Working Group reviewed the ISO Transport MIB submitted by Russ Blaesing. Following a discussion of what and how many managed objects would be useful for network operations, Dave Piscitello agreed to evaluate this MIB against MIB-II, TCP Group. He will post the results of this comparison to NOOP mailing list. NOOP will then discuss what MOs are required for operations, and will make this set known to vendors. The Working Group received a presentation of TUBA from Ross Callon; of Interop '92 spring experiences from Rich Colella; and of X Window System over OSI and the ``skinny OSI stack'' from Jim Quigley. OSI Directory Services Working Group (OSIDS) Discussion topics: o The latest1992 CCITT X.500 version is dated 25-12-1992 (The Christmas paper). o RFC-1279 (Representing DNS in the Directory) has been revised. o OIW established a new specification: IGOS (industry and Government OSI Specification), it requires a.o. many X.500 1992 extensions. o NADF split the Naming Schema document into two docs: - Naming schema set-up for countries. - Specific case for the US. o NADF security paper, protection by passwords, weak credentials. There is a defect in the replay of passwords in simple auth. (fixed in 1992 version?) o There is a road-map paper indicating all NADF publications. o None of (12) vendors in NADF was supporting strong auth, none had timelines for 1992 extensions. Documents discussed: 5 o Naming guidelines for Directory pilots paper to be progressed to an Informational RFC. o A string representation of distinguished names to Proposed Standard. o User Friendly Naming to Experimental RFC. o Strategy Document. Those who read it (ca 60document. The document will be redistributed after processing minor comments and then submitted to IESG/IAB for policy approval, and subsequent publishing as an Informational RFC. o IP address information in the Directory. The paper was discussed and several major changes were suggested. Work ongoing. Pilots: - QOS no progress yet. - JPEG ongoing. - DIT counting. - Char set ongoing. A Schema group has not yet been set up. A suggestion was made to ask the IANA to take this on. o Discussion on DUA and DSA metrics papers. Meant to set metrics for comparing DSAs and DUAs (functionality, capacity etc.) The papers will be used to describe existing implementations and results/comments on the paper will be reported back into the next meeting. Papers will then be revised and put forward as informational RFCs. o Two papers on a lightweight access protocol for the directory were discussed. Minor comments were given, after these have been worked into the paper it will be submitted to the IESG for publication as Proposed Standard. o DSA naming. This paper was discussed. The paper is seen as being still too much oriented towards one single implementation, to be publishable as an RFC. Therefore the Working Group will drop the issue until other manufacturers have commented or supplied their solution to DSA naming and knowledge distribution. Next meeting at November IETF. Office Document Architecture Working Group (ODA) Progress of products: Six products now known to the Group, most of them not yet with full vendor support. 6 Progress on pilots: Few groups put up some of products. Use is mostly internal and limited. Expectations: Over next year the int. profile FDD 26 is being ratified and will probably lead to new products and pilots. However in the next six months little progress is expected, so the IETF ODA Working Group will not meet in November 92, but will sleep until new activity pops up. SNMP over a Multi-protocol Internet Working Group (MPSNMP) The Group met and reviewed three Internet Drafts. o SNMP over OSI (CL Transport Service) o SNMP over Appletalk o SNMP over IPX All three were aligned with respect to the treatment and assignment of Object Identifiers for the transportDomain All three have at least one implementation presently. It was agreed that all three would have essentially the same boilerplate recommendation with respect to multiple transport implementations; i.e., that agents are only required to implement *one* transport mapping of SNMP, and managers were expected to implement as many as necessary to allow communication to all agents within a network. Implementations are encouraged to implement UDP. All three documents require minor rewrites; they will all be posted for a two week last call before recommending to the IESG that they be moved to Proposed RFCs. A fourth document describing ``how to write a transport mappings'' was aligned with the three Internet Drafts; this will be revised and submitted as an FYI RFC. With no further work to consider, the Working Group agreed to disband. X.400 Operations Working Group (X400OPS) Status report on the pilots (XNREN and Cosine MHS) was given. The amount of usage as well as the amount of connected MTAs is growing steadily. Work on daily update tool for outing and mapping tables is still ongoing and expected to be ready by the end of 1992. Connectivity issues: o Internet-X.400 to public X.400; o RFC-822 to public X.400; Various unstandardised gateways from 7 commercial service providers (e.g., AT&T, MCI, IBM) to the Internet were discussed. These gateways cause problems like address mangling. o In the US rather than ADMD= they have proposed an ADMD=usbb, to register nationwide-multiple-carrier PRMDs. So if a prmd subscribes to e.g., ADMD=attmail, they can choose to do so under ADMD=attmail or request from AT&T to do it under ADMD=usbb. Documents o Proposed in this text is to use the X.400/88 GeneralText option to use extended character sets. This option is not really in X.400/88, but only in the ISO version, however it is an extended bodypart and thus can be used without modifications. The paper further describes the ISO 8859 character sets that should be used. NOTE: o.a. the Dutch ligature ij is missing!! Jammerlijk maar geen ramp. Paper will be revised to the comments made and discussed with char set experts (e.g., RARE wg-char), and then it will be put forward to RARE wg-mhs and the November IETf meeting. o Coordination Procedures for RFC 1327 gateways by Cosine MHS The paper documents current procedures for reference and with the purpose of making it more globally known. There is no information in the paper on how the tables should be formatted and what can and cannot go in. This will be a separate paper. However this paper should still contain some general indications. The paper will be adapted to the comments and then put forward as informational RFC. o Operational requirements.... - Rob Hagens/Alf Hansen Minor comments were made to this document. It will be published as an Experimental Standard RFC. o Routing coordination for X.400 Urs Eppenberger The document is almost finished. However a new perspective has been brought in by GMD (Panos G.) to allow for more X.500 oriented syntaxes in the document. Panos, Steve Hardcastle-Kille and Urs will discuss this off-line. Time pressure is high. To be progressed to Experimental Standard RFC soon. o Using DNS to maintain RFC987 mapping tables - Claudio Allocchio This paper shows the various issues that have come forward out of the Trieste experiments with the use of DNS. The paper provides an independent way to distribute the table WITHOUT distributing necessarily the authority. It is proposed that the various alternatives will be put forward to the IETF DNS Group for advise, and that following that the paper will be progressed to an Experimental RFC 8 o Mapping between X.400 and Mail-11 - Claudio Allocchio There was unfortunately no time to discuss this paper. There is one implementation around, discussion will be done by E-mail. o New document: Grandfathering of ADMD=internet in the US, to be produced. o New document: The use of s=postmaster in X.400, to be produced. Next meeting at November IETF. 9