Re: [Dime] Remarks/Inquiries about rfc3588bis16 changes

[Victor Fajardo <vfajardo at tari.toshiba.com>]

Hi Jan,
> Greetings!
>
>
> I do have a few remarks and questions regarding the latest -bis16 update 
> and the protocol in general.
> Quoting bis16.
>
>
> |page 11
> |
> |Deprecated the exchange of CER/CEA message in the open state.
>
> What would happen if such an exchange in the open state produces no 
> common applications -- terminate connection, or remain in the open state?
>   

In this version of the base protocol, it is not expected that CER/CEA 
will be exchanged in the open state. It is one of the features in bis 
(diameter v2) that is not very backward compatible. Though a separate 
solution is in the works.

> |page 46
> |
> |	DiameterIdentity = FQDN/Realm
>
> Here, DiameterIdentity changed from FQDN to FQDN/Realm. One AVP where 
> DiameterIdentity is used is Origin-Host. However, since there is already 
> an AVP Origin-Realm which contais the realm, is it really necessary to 
> add the realm again, to Origin-Host?
>   

Hmm... the expansion of the context of DiameterIdentity does not include 
an assumption that concatenation of Origin-Host and Origin-Realm would 
form an FQDN. It is probably cleanest to keep Origin-Host as it is since 
there maybe future use cases where Origin-Host is re-used by itself, 
i.e. without any other realm avp accompanying it.

> |page 117
> |-bis15
> |+bis16
> |
> |-abrubtly shutdown by comparing the old value of the Origin-State-Id
> |+abrupbtly shutdown by comparing the old value of the Origin-State-Id
>
> Third try, the correct spelling is:	abruptly
>   

Ok

> |-11.5. Diameter TCP/SCTP and TLS Port Numbers
> |+11.5. Diameter TCP, SCTP and TLS/TCP Port Numbers
>
> The TLS/TCP port number should then also be assigned for TLS/SCTP.
>   

The new security changes does not support TLS/SCTP. We can clarify this.

regards,
victor

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