[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: defining networks/prefix and host wildcards, and IPsec.

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Carl" == Carl Ellison <cme@cybercash.com> writes:
    Carl> No, that's the older style.  One would use:

  Okay, I'm going to revise my message.

    Carl> and the [ipv4] should probably be a more complete MIME type,

  Agreed. I suspect we might need a new top level mime type, no clue
what it would be called.
 
    Carl> although I'm not a MIME bigot.  I'd be inclined to leave it
    Carl> off, but now that we're facing a world with multiple IP
    Carl> address lengths, we might need it.

    >> [IStar owns 205.233.48.0/20]

    Carl> The strings you gave are for a wider range of IP addresses.
    Carl> Where's the typo?

  #CDE93000# -> #CDE93FFF#
    | \ \             \
  205  \ 48            59
        233

  So, there are 59(+1) - 48 = 16, *256 addresses = 4096. /20 == 32 -
12. 2^12 = 4096. No problem here, I think. 
  However, Istar hasn't delegated the entire /20 to me. I have a /28.
  Tell me how you interpreted my strings?

   :!mcr!:            |  Network security programming, currently
   Michael Richardson | on contract with DataFellows F-Secure IPSec
 WWW: <A HREF="http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ottawa.on.ca</A>. PGP key available.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNAMKC6ZpLyXYhL+BAQFDEAL+LjR0rIOavFoueSzELXFc81z2YmOEqYv9
kbgiPPxc7dRixeo/N8TGDghc/QOoDp0N/gVJp4CvErB4NZy08pYcOLL6GRM3eAwG
se0uhm8PCsOl/e7D45vTiDDKllYmfmj5
=/pRc
-----END PGP SIGNATURE-----
Follow-Ups: References: