On 08/01/2013 09:01 AM, Erik Nordmark wrote:
On 8/1/13 2:31 PM, Keith Moore wrote:
Hosnieh clarified the slide by explaining that by using "public
addresses" she meant addresses resolvable from DNS lookups. But then
the idea that a node should not use "public addresses" is problematic
for dif
Hi,
Thank you so much.
>I recommend removing the text, or replacing it with something like "The
choice of whether to list a node's address in DNS properly depends on many
factors, including the set of >applications to be run on the host. Not
listing a node's address in the public DNS may increa
Hi,
Again Thanks for your comments.
> I do think it might be useful to recommend that DNS servers be configured
as to
> refuse requests to list DNS zones as a means to thwart attackers from
looking
> for IPv6 addresses. But assuming that such listing is disabled, I don't
know why
> listing a hos
Hi,
Thanks for your comments.
>
> > "peer" is also a nit - if you
> > want an unknown someone to be able to contact you, you need to make
> > yourself findable, whether the protocol design is p2p or not.
> > Otherwise you don't.
>
> I also object to the notion that every host or application sho
On 8/1/13 2:31 PM, Keith Moore wrote:
Hosnieh clarified the slide by explaining that by using "public
addresses" she meant addresses resolvable from DNS lookups. But then
the idea that a node should not use "public addresses" is problematic
for different reasons.
Keith,
From a terminology p
> -Original Message-
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Scott
> Brim
> "peer" is also a nit - if you
> want an unknown someone to be able to contact you, you need to make
> yourself findable, whether the protocol design is p2p or not. Otherwise
> you
I do think it might be useful to recommend that DNS servers be configured as to
refuse requests to list DNS zones as a means to thwart attackers from looking
for IPv6 addresses. But assuming that such listing is disabled, I don't know
why listing a host's address in DNS would make that host a
Thanks a lot for your comments. They were actually quite helpful and made
some good points. Here are my answers:
>There are many people (in IETF and elsewhere) who believe that applications
should never use IP addresses directly or in referrals to Other
applications. This is often cited as if it
On 02/08/2013 01:26, Scott Brim wrote:
> On 08/01/13 14:31, Keith Moore allegedly wrote:
>> There are many people (in IETF and elsewhere) who believe that
>> applications should never use IP addresses directly or in referrals to
>> other applications. This is often cited as if it were some
>> arc
Thanks a lot for your comments. They were actually quite helpful and made
some good points. Here are my answers:
>There are many people (in IETF and elsewhere) who believe that applications
should never use IP addresses directly or in referrals to Other
applications. This is often cited as if it
On Aug 1, 2013, at 4:17 PM, Scott Brim wrote:
> On 08/01/13 16:09, Keith Moore allegedly wrote:
>> I do not think it is appropriate to assume that nodes are either clients
>> or servers.Nodes can (and routinely do) support several applications
>> in which the local protocol engine acts as a cl
On 08/01/13 16:09, Keith Moore allegedly wrote:
> I do not think it is appropriate to assume that nodes are either clients
> or servers.Nodes can (and routinely do) support several applications
> in which the local protocol engine acts as a client, a server, or a
> peer, depending on the needs
On Aug 1, 2013, at 3:47 PM, Hosnieh Rafiee wrote:
>> All sources of Internet public services need to have DNS names, but that's
>> it.
>> Other than that, "names" are only needed in higher layer communications, and
>> can be handled there. For example, your laptop doesn't need a name to open
>>
Many thanks for your comments.
>
> On 08/01/13 14:31, Keith Moore allegedly wrote:
> > There are many people (in IETF and elsewhere) who believe that
> > applications should never use IP addresses directly or in referrals to
> > other applications. This is often cited as if it were some
> > arc
On 08/01/13 14:31, Keith Moore allegedly wrote:
> There are many people (in IETF and elsewhere) who believe that
> applications should never use IP addresses directly or in referrals to
> other applications. This is often cited as if it were some
> architectural principle - in fact just last nigh
On reflection I wanted to respond to this a bit more:
I was responding to slide 9, and in particular the bullet point that says "The
node Should not use public addresses".
When I initially read this, I interpreted "public addresses" with the meaning
that they tend to have in IPv4 - which is to
Hi Zhou,
Thanks for the comment.
> I don't think using CGA by replacing the public key with a timestamp or
other random string is a "higher randomzation" address generation method.
>Hash is only one technique of generating a random like string, may not be
the best one among those specified in
Hi, Rafiee,
I don't think using CGA by replacing the public key with a timestamp
or other random string is a "higher randomzation" address generation
method.
Hash is only one technique of generating a random like string, may not be
the best one among those specified in RFC4086.
ipv6-bou
18 matches
Mail list logo
