Re: [Dime] [Fwd: draft-ietf-dime-rfc3588bis review (1/3)]

[Jan Engelhardt <jengelh at medozas.de>]

On Sunday 2008-11-02 14:53, Victor Fajardo wrote:

> Hi Hannes,
>
> I've incorporated majority of the editorial items you mentioned below. Others
> I've commented below. The changes here should be incorporated into
> draft*-13.txt

So let me chime in here then, because I have noticed a number of 
oddities too.


>> s/The base Diameter protocol is run on port 3868 of both TCP [RFC793] 
>> and SCTP [RFC2960] transport protocols./The base Diameter protocol is 
>> run on port 3868 of both TCP [RFC793] and SCTP [RFC2960].
>>
>> Delete "Future versions of this specification MAY
>>   mandate that clients support SCTP."
>>
>> I also do not understand why we require that agents and servers must 
>> support SCTP. That does not sound realistic if I consider our interop 
>> testing experience.
>
> It seems expected that during the interop most folks would support TCP 
> since that would be the easiest/most natural to implement first. I 
> could not remember if there was consensus for requiring SCTP for 
> servers was impractical.

The only problem I see here is operating systems lacking support for 
SCTP right now. Windows might fall under that. To my knowledge, Solaris 
(10) does too somewhat -- because it does not seem to autoload the 
module like a Linux kernel would do. Mac OS X I do not know, but if it 
has, autoload is not happening either. And then of course every Linux 
kernel installation which has SCTP compiled out.

_______________________________________________
DiME mailing list
DiME at ietf.org
https://www.ietf.org/mailman/listinfo/dime