Some comments to the x400ops aganda in Houston.
Alf Hansen <Alf.Hansen@uninett.no> Thu, 28 October 1993 15:06 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06902;
28 Oct 93 11:06 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06898;
28 Oct 93 11:06 EDT
Received: from mhs-relay.cs.wisc.edu by CNRI.Reston.VA.US id aa12339;
28 Oct 93 11:06 EDT
Received: from cs.wisc.edu by mhs-relay.cs.wisc.edu with SMTP (PP)
id <20641-0@mhs-relay.cs.wisc.edu>; Thu, 28 Oct 1993 09:50:57 +0000
Message-Id: <9310281450.AA03036@cs.wisc.edu>
Received: from domen.uninett.no by cs.wisc.edu; Thu, 28 Oct 93 09:50:52 -0500
Received: from localhost by domen.uninett.no with SMTP (PP)
id <25109-0@domen.uninett.no>; Thu, 28 Oct 1993 15:50:28 +0100
To: ietf-osi-x400ops@cs.wisc.edu
Subject: Some comments to the x400ops aganda in Houston.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 28 Oct 1993 15:50:27 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Alf Hansen <Alf.Hansen@uninett.no>
Friends,
Here are my few comments to what I think is important to achieve in
the x400ops slot in Houston:
1. opening
----------
2. Postmaster doc 20 min.
--------------------------
Allan has just distributed his last version. It is important to move
this document forward. Without progress, the "Requirements" document is
blocked.
3. Requirements doc 10 min.
---------------------------
The latest version was distributed by me some weeks ago. Can we move
this forward now?
4. DNS support for rfc1327 mapping 10 min.
------------------------------------------
Claudio has contributed to this work since after the Boulder
IETF... This is an example showing that these kind of experiments
takes time. My feeling is that this work is important and the
experiments should be carried on with.
Perhaps a new WG on this?
5. CXII discussion 1 hour
-------------------------
Actually this belongs to the CXII WG timeslot, but it is important to
look at this from the x400ops context, too. CXII will take over some of
the tasks we had in x400ops, and we have to lay the ground for their work.
6. US-ops 30 minutes
--------------------
If my understanding is right, US-ops means what we called
"x400opsII" in Amsterdam. Please correct me if I am wrong..
An action item from Amsterdam for Tony, myself and Erik, was to draft
a charter for "x400opsII". This has not been done. Perhaps we can
think about this from now on until the meeting, and present a proposed
draft in Houston?
It is not clear to me if US-ops is an IETF WG or a national US WG. Has
an initiative been taken regarding the creation of US-ops?
7. What next 20 min.
--------------------
To me it is important that the good spirit from the x400ops WG
continues in the WGs taking over the work. One important thing is to
identify which WG (if any) is doing what with X.400 operational thing
in the Internet context.
One good start could be to list the x400ops documents and try to
determine who is taking over the responibility for them, or perhaps
decide that some of the documents are not important, and should be
deleted(?).
This is the list of documents from the charter:
Internet Drafts:
Posted Revised I-D Title <Filename>
------ ------- ------------------------------------------
Mar 92 Oct 93 <draft-ietf-x400ops-mgtdomains-ops-06.txt>
Operational Requirements for X.400 Management Domains in the
GO-MHS Community
Nov 92 Jul 93 <draft-ietf-x400ops-postmaster-02.txt>
Postmaster Convention for X.400 Operations
Dec 92 Jun 93 <draft-ietf-x400ops-admd-02.txt>
Assertion of C=US; A=IMX
Jul 93 Jul 93 <draft-ietf-x400ops-tbl-dist-part1-01.txt>
Mail based file distribution Part 1: Dialog between two nodes
Jul 93 Jul 93 <draft-ietf-x400ops-tbl-dist-part2-01.txt>
Mail based file distribution Part 2: Over-all structure
Request For Comments:
RFC Stat Published Title
------- -- ---------- -----------------------------------------
RFC1405 E Jan 93 Mapping between X.400(1984/1988) and Mail-11 (DECnet
mail)
RFC1465 E May 93 Routing coordination for X.400 MHS services within a
multi protocol / multi network environment Table Format
V3 for static routing
RFC1502 PS Aug 93 X.400 Use of Extended Character Sets
8. close
--------
Tony said this in a previous message, but I just wanted to thank you all
for all the interesting discussions and your friendship.
As you may have noticed, I have not been very active on the x400ops
list lately, and this is of course because I have been tied up with
other business in UNINETT.
I trust that the other WGs (RARE/IETF) will follow up the issues
and review the situation continously.
See you in Houston!
Alf H