Alf.Hansen@pilot.cs.wisc.edu (Alf Hansen) (03/09/91)
Archive-name: mail/x400/ietf-x400-wg/0--
Archive-directory: mhs-relay.cs.wisc.edu:/pub/ [128.105.8.53]
Original-posting-by: Alf.Hansen@pilot.cs.wisc.edu (Alf Hansen)
Original-subject: IETF X.400 Operations WG, St. Louis.
Reposted-by: emv@ox.com (Edward Vielmetti)
Since everybody seems to send their agendas to this list, I will do the same.
Best regards,
Alf Hansen
==========================================================================
Call for 1st meeting in the IETF X.400 Operations Working Group,
IETF St. Louis:
TUESDAY, March 12 1991, 9:00am - 12:00pm and 1:30pm - 3:30pm
WEDNESDAY, March 13 1991, 9:00am - 12:00pm and 1:30pm - 3:30pm
HOTEL/MEETING SITE: Clayton Plaza Holiday Inn
7730 Bonhomme Avenue
St. Louis, MO 63105
(314) 863-0400 {fax:(314) 863-8513}
Rooms reserved until February 22, 1991
$60.50/single or double
Specify: IETF GROUP
General: The concrete goal of the meeting is to produce an internal outline
of the resulting document that specifies the requirements and
conventions of operational Internet PRMDs.
Before doing so, we should have an open discussion on the roles of
a PRMD, based on the available experience in the group.
The notation: **FTP: filname is a reference to relevant documents
available via anonymous ftp from the directory ~ftp/pub/ on
mhs-relay.cs.wisc.edu (128.105.8.53). Please come prepared to the meeting.
Background reading: **FTP: prospectives.txt
Provisional agenda
==================
1. Welcome, secretary, roll call of delegates, agenda. 15 min
------------------------------------------------------
2. The IETF X.400 Operations WG. 20 min
--------------------------------
- Review of Charter. **FTP: charter.txt
- Relations to other groups: IETF-DS, IETF-ODA, RARE-WG1,
R&D MHS Managers, etc.
3. Round table presentation of current X.400 service status. 1.5 hr
------------------------------------------------------------
Each PRMD (CDC, ARC, XNREN and perhaps others) present their
status. CDC and XNREN have circulated status documents. The others
should also do so before the meeting.
**FTP: status-cdc.txt
**FTP: status-xnren.txt
If representatives from ADMDs are present, status reports are appreciated.
Organizations with significant X.400 activities are also welcome to
report.
4. Overall organization of the X.400 service in the Internet.
-------------------------------------------------------------
4.1 Technical requirements. 15 min
- X.400 profiles: (84, NBS)
- Communication platform (internally: RFC 1006/TCP/IP,
externally, also TP 0/X.25, experimentally: TP 4/CLNS)
4.2 Internal organization of PRMDs. 3 hrs
Including relations to the Internet mail service (non-X.400).
- Registration of X.400 addresses.
It is not yet possible to register unique ADMDs and PRMDs
officially in the US. Reports from the 1st meeting in the
US CCITT Study Group D, subgroup NHS-MD, have been distributed.
**FTP: mhs-md-1st-meeting-rep.txt
**FTP: mhs-md-1st-meeting-slides.txt
**FTP: mhs-md-2nd-meeting-info.txt
The best we can do for the moment is to make sure that PRMDs
(and possibly also Os) are unique in the Internet. PRMD XNREN
has established an XNREN Naming Authority (NA). Should we let
this NA be a registration body for PRMDs (and Os) also for other
Internet PRMDs? **FTP: na-statutes.txt
- Responsibilities for ORG and MTA Documentation. Current documents:
**FTP: country-us.doc
**FTP: org-us.doc
**FTP: mta-us.doc
The NSF X.400 Project volunteers to maintain the documents for
all the Internet PRMDs.
- Routing strategies (both inter- and intra- PRMDs).
Proposal: "As direct as technically possible". MTA documents
are used to exchange routing info.
- Transit X.400 traffic.
Can we agree to share recourses between all Internet PRMDs? Ex: If
I have temporary problems with my direct route to a PRMD, can I
use another PRMD as a relay?
- RFC 987 gateway management.
Address mapping table coordination. The current tables:
**FTP: rfc987-mapping1.doc
**FTP: rfc987-mapping2.doc
4.3 External relations. 1 hr
4.3.1 To ADMDs.
Vint Cerf will present how CNRI can act as an initial X.400
relay between the Internet PRMDs and ADMDs in the U.S.
4.3.2 To the existing International R&D MHS Service.
Alf H will present the existing model for cooperation between
PRMD XNREN and the R&D MHS Service coordinated in Europe.
5. RFC-822/X,400 address mapping coordination. 2.5 hrs
----------------------------------------------
Starting point will be the preliminary conclusions from the IXOM meeting
in Madison Nov. 28. **FTP: ixom-minutes.txt
Case studies. We will go through the current procedures
and check if they have the flexibility we want. Please submit
mapping / address transition examples to the mailing list prior to the
meeting.
Hopefully we can conclude with one common mapping strategy for all
Internet PRMDs, based on one of the combination of alternatives
from the Madison meeting:
"In general, the high components of an O/R Address are used to identify
a gateway or community. For example,
Identifies Gateway: /C=gb/PRMD=ac.uk/O=relay/
Identifies Community: /C=us/PRMD=RFC-822/
In general, lower components of the O/R Address are used to identify
the RFC-822 user. The RFC-822 address can either be "exploded" into
O/R Address fields, or "encoded" intact inside a domain-defined
attribute field. For example,
Exploded address: /O=edu/OU=wisc/OU=cs/S=user/
Encoded address: /DD.RFC822="user(a)cs.wisc.edu"/ "
6. X.400 / Internet Mail integration issues. 30 min
--------------------------------------------
Presentation of scenarios. Initiation of discussion.
7. Future issues. 30 min
-----------------
Let us maintain a list of issues in order to be able implement
them in our service when solutions are available.
- X.400/84 <--> 88 interworking. **FTP: 88-to-84-downgrading-kille.txt
- Use of DNS for RFC 987 address mapping management
**FTP: dns-987.ps (or .txt)
- Use of an X.500 infrastructure for routing and user catalog purposes.
- National character sets.
- New body types.
8. Outline of PRMD requirements. 30 min
--------------------------------
Based on the discussions above.
9. A(ny) O(ther) B(usiness) and plan for next meetings. 15 min
-------------------------------------------------------