Re: Submission Informational RFC

Yanick <pouffary@taec.enet.dec.com> Wed, 03 May 1995 14:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03198; 3 May 95 10:19 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03194; 3 May 95 10:19 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07461; 3 May 95 10:19 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03187; 3 May 95 10:18 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03183; 3 May 95 10:18 EDT
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa07448; 3 May 95 10:18 EDT
Received: from inet-gw-2.pa.dec.com by venera.isi.edu (5.65c/5.61+local-21) id <AA08228>; Wed, 3 May 1995 07:19:38 -0700
Received: from vbormc.vbo.dec.com by inet-gw-2.pa.dec.com (5.65/24Feb95) id AA28588; Wed, 3 May 95 07:10:20 -0700
Received: by vbormc.vbo.dec.com; id AA27263; Wed, 3 May 95 15:50:21 +0200
Message-Id: <9505031350.AA27263@vbormc.vbo.dec.com>
Received: from taec.enet; by vbormc.enet; Wed, 3 May 95 16:00:22 MET DST
Date: Wed, 3 May 95 16:00:22 MET DST
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yanick <pouffary@taec.enet.dec.com>
To: harald.t.alvestrand@uninett.no
Cc: iesg@isi.edu, pouffary@taec.enet.dec.com
Apparently-To: iesg@ISI.EDU, harald.t.alvestrand@uninett.no
Subject: Re: Submission Informational RFC

Hi Harald,

Thanks for your input. I just came in the office today (I am on vacation till 
next tuesday). I want to briefly answer your questions now. We can discuss 
more when I come back from vacation May 9th.

##1) Has the port 399 been officially assigned, or is it a "grab"?

Yes it has on 19-NOV-1994. See the mail below
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From:VBORMC::"jkrey@ISI.EDU" 19-NOV-1994 01:16:13.90
To:  taec::pouffary
CC:  iana@ISI.EDU
Subj:Re: Request for Well-known TCP port number assignment

Yanick,

We have assigned port number 399 to ISO-TSAP Class 2,
with you as the point of contact.

Joyce
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#2) I would *much* prefer that the document start out with "this is the
#   documentation for how DECNET/OSI works over TCP/IP".

Well we could but really this extension is very generic. ISO transport 
identify its user by transport service access point ID (TSAP-ID). 

#- Expedited follows an idea that Marshall used for an 
#  *earlier* RFC1006 version, but abandoned; there is no guarantee that
#  the expedited PDU does not arrive *later* than normal data sent at
#  the same time, and this is required by the ISO protocol

To guaranty delivery of interrupt data the second channel is not torn 
down until the normal data channel is. The need is to have separate virtual 
data channels. Interrupt Data transmission cannot be blocked by a congested 
Normal data channel.

#- Multiplexing is recommended against, but not forbidden; this combined
#  with no explicit flow control means that multiplexing can happen
#  and will lead to some *fun* reactions on congestion

This is why we don't recommended for performance reason to do multiplexing.
But if one want to do it one can always do it.

#- The idea that one can tell from the TPDUs whether this is RFC1006
#  or this new protocol is simply wrong, unless one watches every
#  packet from session establishment onwards

That is not true. Connect-request identify the class and the end-user TSAP-ID.
Once the connection is established no one needs to monitor it.

#- There is no description on what to do if someone suggests that we
#  negotiate down to class 0 on establishment; is this allowed?

This is not allowed. Class negotiation is done according to ISO 8073 rules.
When using TP0 over TCP/IP there is only class 0 can be negotiated.
When using TP2-No-Flow-Control over TCP/IP no other class can be negotiated.
This is because 0 is not an alternate of 2 unless it is explicitly specified
in the connect request TPDU.

#All in all, I feel very good about DEC wanting to document its protocol,
#but I don't like the present submission very much.
#Would it be appropriate to suggest that he publish it as an Internet-draft,
#so that other people can take a look at it to ensure clarity before it
#is published as Informational?

It was published for six months. Sorry if you missed it.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Internet-Draft is available from the on-line Internet-Drafts
directories.

       Title     : ISO Transport Service over TCP RFC1006 extension
       Author(s) : Y. Pouffary
       Filename  : draft-pouffary-tcp-00.txt
       Pages     : 10
       Date      : 10/25/1994

Internet-Drafts are available by anonymous FTP.  Login with the
username "anonymous" and password "guest".  After logging in,
Type "cd internet-drafts".
     "get draft-pouffary-tcp-00.txt".

Internet-Drafts directories are located at:

     o  US East Coast
        Address:  ds.internic.net (198.49.45.10)

     o  US West Coast
        Address:  ftp.isi.edu (128.9.0.32)

     o  Pacific Rim
        Address:  munnari.oz.au (128.250.1.21)

     o  Europe
        Address:  nic.nordu.net (192.36.148.17)

Internet-Drafts are also available by mail.

Send a message to:  mailserv@ds.internic.net. In the body type:
     "FILE /internet-drafts/draft-pouffary-tcp-00.txt".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Looking forward to more cooperation.
Best regards
Yanick