Re: questions about SILC's IP and DNS requirements [was: Re: Implement ExternalIp config directive]

: Can i ask why the IP matching is important in the first place?
: sections 4.1 and 4.2 of the I-D [0] suggest that valid public IP
: addresses and DNS are *requirements* of the protocol:
: 
: PTR lookups be able to make my client fail to connect to a silc
: server?  Are there good reasons to enforce IP and DNS rules that i'm
: not aware of?
: 
Well, they were written so long ago that I'm not entirely sure why they 
are there... The new drafts for the RFC procedure, not yet finished or 
released, reads as follows:

X.X. Creating Client Connection

SILC Client (from here on called client) connection to SILC Server or
SILC Router (from here on called server) are created as follows:

1. Server SHOULD perform IP address lookup and reverse IP address
   lookup.  The client SHOULD have both valid IP address and fully
   qualified domain name (FQDN).  Typical server implementation would
   also check its local configuration whether the client connection is
   allowed.

...etc...

X.X. Creating Server Connection
      
SILC Server (from here on called server) and SILC Router (from here on
called router) connections are created as follows:

1. The connecting server's or router's IP address and fully qualified 
   domain name (FQDN) SHOULD be resolved and verified.  The server and
   router SHOULD have both valid IP address and FQDN.  Typical
   implementation would also check its local configuration whether the  
   server or router connection is allowed.
   
...etc...

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/
_______________________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-announce
Archive: https://lists.silcnet.org/pipermail/silc-announce
FAQ:     http://silcnet.org/support/faq/