Re: Potential lead for MHS management "MHS Routing Framework" by Cristian Constantinof
Alf Hansen <Alf.Hansen@delab.sintef.no> Tue, 11 August 1992 09:08 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa00668; 11 Aug 92 5:08 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa00660; 11 Aug 92 5:08 EDT
Received: from mhs-relay.cs.wisc.edu by NRI.Reston.VA.US id ac02479; 11 Aug 92 5:09 EDT
X400-Received: by mta mhs-relay.cs.wisc.edu in /PRMD=XNREN/ADMD= /C=US/; Relayed; Tue, 11 Aug 1992 02:25:54 +0000
Date: Tue, 11 Aug 1992 02:25:54 +0000
X400-Originator: cargille@cs.wisc.edu
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=XNREN/ADMD= /C=US/; mhs-relay..667:11.07.92.07.25.54]
Priority: Non-Urgent
DL-Expansion-History: ietf-osi-x400ops@cs.wisc.edu ; Tue, 11 Aug 1992 02:25:53 +0000;
From: Alf Hansen <Alf.Hansen@delab.sintef.no>
Message-ID: <2761*/G=Alf/S=Hansen/OU=delab/O=sintef/PRMD=uninett/C=no/@MHS>
To: pjb <pjb@mbunix.mitre.org>
Cc: Stef <Stef@nma.com>, pjb <pjb@mbunix.mitre.org>, Cristian Constantinof <chrisc@bnr.ca>, Bernhard Plattner <plattner@komsys.tik.ethz.ch>, ?rald Neufeld <neufeld@cs.ubc.ca>, "Ann.V.McLaughlin" <Ann.V.McLaughlin@bistromath.mitre.org>, bmurrill <bmurrill@attmail.com>, mitre-osi <mitre-osi@bistromath.mitre.org>, nadism <nadism@mbunix.mitre.org>, ink <ink@gateway.mitre.org>, nmsig <nmsig@ics.uci.edu>, ietf-osi-x400ops <ietf-osi-x400ops@cs.wisc.edu>, adamse <adamse@attmail.com>
In-Reply-To: <9208101855.AA25072@mbunix.mitre.org>
Subject: Re: Potential lead for MHS management "MHS Routing Framework" by Cristian Constantinof
Paul, > Stef et al, > > Could someone please provide me some background as to what > X.400 management information definition work is going on in the IETF > When did it start? Who is leading and supporting this work? What are > the goals and schedules of this work > > Thanks, > Paul For your information I am enclosing the current charter for the IETF X.400 OPS WG. Please note that this charter will be revised shortly. In Europe this work is supported by the EUREKA project: COSINE MHS, and the paricipating national networks. In the U.S. the work is supported by NSF (The Internet X.400 Project) and the participating agencies. Best regards, Alf H IETF X.400 OPS Co-chair ==================== Charter OSI Integration Area X.400 Operations Working Group Co-chairs: Alf Hansen, Alf.Hansen@delab.sintef.no C=no;ADMD=" ";PRMD=uninett;O=SINTEF;OU=DELAB;S=Hansen;G=Alf Robert Hagens, <hagens@ans.net> C=us;ADMD=" ";PRMD=Internet;DD.RFC-822=hagens(a)ans.net Mailing Lists: ietf-osi-x400ops@cs.wisc.edu C=us;ADMD= ;PRMD=xnren;O=UW-Madison;OU=cs;S=ietf-osi-x400ops ietf-osi-x400ops-request@cs.wisc.edu C=us;ADMD= ;PRMD=xnren;O=UW-Madison;OU=cs;S=ietf-osi-x400ops-request Description of Working Group: X.400 management domains are being deployed today on the Internet. There is a need for coordination of the various efforts to insure that they can interoperate and collectively provide an Internet-wide X.400 message transfer service connected to the existing Internet mail service. The work in this WG is closely related to work in IETF-OSI-MHS-DS and RARE WG-MSG These WGs cover additional aspects of X.400 Service Integration. Goals and Milestones: The overall goal of this group is to insure interoperability between Internet X.400 management domains and to the existing Internet mail service. The specific task of this group is to produce and monitor the new documents needed for such interoperation. The following documents are identified for this WG: OPS-1: "Operational Requirements for X.400 Management Domains in the GO-MHS Community". OPS-2: "Using the Internet DNS to maintain RFC987/RFC1148 Address Mapping Tables and X.400 Routing Informations" OPS-3: "Routing coordination for X.400 MHS services within a multi protocol / multi network environment". OPS-4: "Mapping between X.400(1984/1988) and Mail-11 (DECnet mail)" OPS-5: "X.400 use of extended character sets" OPS-6: "Address mapping table update procedures" The tentative timetable for this group is Feb 1991: Initial meeting, produce internal outline of OPS-1. Aug 1991: Working draft OPS-1, circulate to interested people. Spring 1992: Internet draft available of OPS-1. Identify and work on new documents. Summer 1992: OPS-1 ready for publication. Autumn 1992/ Spring 1993: Monitor and work on the other documents, and identify new ones.
- Re: Potential lead for MHS management "MHS Routin… Einar Stefferud
- Re: Potential lead for MHS management "MHS Routin… pjb
- Re: Potential lead for MHS management "MHS Routin… Einar Stefferud
- Re: Potential lead for MHS management "MHS Routin… Alf Hansen