RE: Applying to IANA for KMIP ports

["Frindell,Alan" <Alan.Frindell@safenet-inc.com>]

Indra asked me to reopen this topic for discussion, in order to resolve the TBDs in the specification and user guide.  Are we ready to initiate the port application process?  

Thanks

-Alan

> -----Original Message-----
> From: Wierenga, Steven [mailto:steve.wierenga@hp.com] 
> Sent: Wednesday, July 22, 2009 7:49 PM
> To: Frindell,Alan; kmip@lists.oasis-open.org
> Subject: RE: Applying to IANA for KMIP ports
> 
> Alan,
> I don't think we're quite ready to apply to IANA, but IMO,
> 1. - yes.  I think this will simplify (vs. complicate) 
> implementations.
> 2. - yes.  I believe the "server to client" operations 
> constitute a different service, and that both security and 
> economy (eg port listeners) suggest separate port numbers.
> 
> --Steve Wierenga
> HP
> 
> -----Original Message-----
> From: Frindell,Alan [mailto:Alan.Frindell@safenet-inc.com] 
> Sent: Wednesday, July 22, 2009 4:42 PM
> To: kmip@lists.oasis-open.org
> Subject: [kmip] Applying to IANA for KMIP ports
> 
> In the HTTPS proposal, I left the recommended ports for 
> running KMIP over HTTPS as TBD.  Does the group feel we 
> should apply to IANA for one or more ports for KMIP?  If so, 
> I have a couple additional questions:
> 
> 1.  Should raw KMIP over TLS have a different port than KMIP 
> over HTTPS?
> 
> 2.  Should there be different ports for serving 
> client-to-server operations versus server-to-client operations?
> 
> 
> Some information about the registration process can be found here:
> 
> http://www.iana.org/cgi-bin/usr-port-number.pl
> 
> As this discussion may take some time to resolve, I'm 
> inclined to ask for a vote this week on the most recent 
> version of the HTTPS proposal, which has the port numbers TBD.
> 
> Thanks
> 
> -Alan
> 
> The information contained in this electronic mail 
> transmission may be privileged and confidential, and 
> therefore, protected from disclosure. If you have received 
> this communication in error, please notify us immediately by 
> replying to this message and deleting it from your computer 
> without copying or disclosing it.
> 
>  
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS 
> TC that generates this mail.  Follow this link to all your 
> TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php 
> 
> The information contained in this electronic mail transmission 
may be privileged and confidential, and therefore, protected 
from disclosure. If you have received this communication in 
error, please notify us immediately by replying to this 
message and deleting it from your computer without copying 
or disclosing it.