🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #4919

Re: IPv6 design questions

#4919
From: Remy Lebeau (TeamB)
Date: Wed, 08 Dec 2004 17:18
61 lines
3044 bytes
"Lynn Morrison" <Cranky@__whisp.com> wrote in message
news:41b71028$1@newsgroups.borland.com...

> Ok, I understand the bit about the 8 segments of 16 bit hex values. So far
> so good. What I don't understand(as described in section 2.3) is the text
> representation of the prefixes such as
>
> 12AB:0000:0000:CD30:0000:0000:0000:0000/60
>
> ... honestly, this is where they lose me. What IS the /60 for?

Take a closer look at section 2.3 of the RFC again.  It is spelled out *very
clearly* what the "/60" stands for.  You take the textual address preceeding
the "/60", convert it to its binary format, and then the specified number of
left-side bits (60 in this case) is the address's prefix.

> In section 2.5.6, it describes IPX addressing where the high 7 bits
> is stripped. This makes no sense to me at all. Ok, stripped is not the
> correct term, perhaps I should be saying that it is reserved for the
> value of 0000010. Again, I am totally confused by this construct.

Ignore it.  That section is not defined yet.

> EPRT |2|1080::8:800:200C:417A|5282|
>
>     is just too weird. I know that the 2 is saying to use IPv6, and I
> know that it is requesting port 5282, but why are there only 6 other
> segments in the middle delimited section?  And why is there a
> double colon in there?

Re-read RFC 2373 section 2.2.2 regarding the special use of the "::" syntax
in IPv6 addresses.  The address being requested is actually
"1080:0:0:0:8:800:200C:417A".

> Is this some kind of abbreviation?

Yes.

> And if so, when parsing such a response to an EPSV command,
> what do I assume with the double colon section?

There is no assumption.  The meaning of "::" is very specific in section
2.2.2.  It only has one meaning.

> Should the middle delimited section have 8 segments in 16 bit hex values?

It should be a valid IPv6 address.  Whether you use an abbreviated syntax or
not is up to you.

> Like when I see this...
>
> |0:0:0:0:0:0:0:1|
>
> I know that this is a loopback address, but at least I know it has 8
> segments to it.

In abbreviated format, that would be "::1".


Gambit
Technical Details
Message-ID: <41b7374b$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <41b71028$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,4a51e8a257c27347
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com>
Newsgroups: borland.public.cppbuilder.internet.socket
References: <41b71028$1@newsgroups.borland.com>
Subject: Re: IPv6 design questions
Date: Wed, 8 Dec 2004 09:18:17 -0800
Lines: 63
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
NNTP-Posting-Host: 68.69.17.41
Message-ID: <41b7374b$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1102526283 68.69.17.41 (8 Dec 2004 09:18:03 -0800)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail