headers
marcelo bagnulo braun | 2 Dec 2005 11:59
Picon

Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

Hi,

we would like to submit the attached draft for the consideration of the 
Internet Area.

This is a very simple and short draft that defines a format for CGA 
extensions.

As you know, Cryptographically Generated Addresses are defined in 
RFC3972. Their main feature is that they contain a hash of a public key 
in the interface identifier part.
As currently defined, CGA allow to include additional information in 
the input of the hash i.e. in  the iid. However, the format of such 
extensions is not defined in the draft.

Lately there are a few initiatives to define such extensions, in 
particular, the Hash Based Addresses (draft-ietf-shim6-hba-01) are 
defined as a CGA extension.

The goal of the attached draft is to simply define a standard format 
for such extensions.

Probably the Internet Area list is a good place to discuss this, since 
the SEND wg (which defined the CGAs) is over and the CGAs are then a 
general tool which usage is being considered in several internet area 
wg.

I guess that the idea would be to try to go forward with this as a 
personal submission, not related to any specific wg. Hence, the 
discussion here is most welcome.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Francis Dupont | 2 Dec 2005 12:16
Picon
Picon

Re: Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

 In your previous mail you wrote:

   This is a very simple and short draft that defines a format for CGA 
   extensions.

=> IMHO the main interest of the document is its IANA consideration
section, isn't it?

Thanks

Francis.Dupont <at> enst-bretagne.fr
Permalink | Reply | 1 comment |
headers
marcelo bagnulo braun | 2 Dec 2005 12:34
Picon

Re: Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt


El 02/12/2005, a las 12:16, Francis Dupont escribió:

>  In your previous mail you wrote:
>
>    This is a very simple and short draft that defines a format for CGA
>    extensions.
>
> => IMHO the main interest of the document is its IANA consideration
> section, isn't it?
>

indeed
the draft defines a namespace for cga extensions that is to be managed 
so that if multiple extensions are defined they can be recognized and 
can be used together without interfering with each other

thanks, marcelo

> Thanks
>
> Francis.Dupont <at> enst-bretagne.fr
>
Permalink | Reply | 0 comments |
headers
Thomas Narten | 6 Dec 2005 15:09
Picon
Favicon

Re: Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

marcelo bagnulo braun <marcelo <at> it.uc3m.es> writes:

> El 02/12/2005, a las 12:16, Francis Dupont escribió:

> >  In your previous mail you wrote:
> >
> >    This is a very simple and short draft that defines a format for CGA
> >    extensions.
> >
> > => IMHO the main interest of the document is its IANA consideration
> > section, isn't it?
> >

> indeed

> the draft defines a namespace for cga extensions that is to be managed 
> so that if multiple extensions are defined they can be recognized and 
> can be used together without interfering with each other

This I don't quite understand. It sounds to me like you are trying to
associate random extensions with a particular CGA Message Type Name
Space (which may well be OK).

But exactly what protocols would carry such extensions? And wouldn't
_those_ protocols need to define the type field (as I think it would
be relative to that protocol)?

What this document seems to be doing is defining a TLV option space,
but the TLV numbering space isn't associated with any specific
protocol.  I don't understand how that would be used. Can you give an
(Continue reading)

Permalink | Reply | 2 comments |
headers
marcelo bagnulo braun | 6 Dec 2005 18:24
Picon

Re: Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

Hi Thomas,

El 06/12/2005, a las 15:09, Thomas Narten escribió:

> marcelo bagnulo braun <marcelo <at> it.uc3m.es> writes:
>
>> El 02/12/2005, a las 12:16, Francis Dupont escribió:
>
>>>  In your previous mail you wrote:
>>>
>>>    This is a very simple and short draft that defines a format for 
>>> CGA
>>>    extensions.
>>>
>>> => IMHO the main interest of the document is its IANA consideration
>>> section, isn't it?
>>>
>
>> indeed
>
>> the draft defines a namespace for cga extensions that is to be managed
>> so that if multiple extensions are defined they can be recognized and
>> can be used together without interfering with each other
>
> This I don't quite understand. It sounds to me like you are trying to
> associate random extensions with a particular CGA Message Type Name
> Space (which may well be OK).
>

i don't think this is what is done in this draft...
(Continue reading)

Permalink | Reply | 1 comment |
headers
James Kempf | 6 Dec 2005 21:40

Re: Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

FWIW, I presented an extension of CGAs, called multikey CGAs, that can be 
used in cases where more than one node can legitimately claim an address to 
Mobopts (draft-kempf-mobopts-ringsig-ndproxy-02.txt) in Paris, for example, 
multicast, anycast or Proxy ND. This would require an extension to the CGA 
Parameters field.

            jak

----- Original Message ----- 
From: "marcelo bagnulo braun" <marcelo <at> it.uc3m.es>
To: "Thomas Narten" <narten <at> us.ibm.com>
Cc: "Internet Area" <int-area <at> ietf.org>
Sent: Tuesday, December 06, 2005 9:24 AM
Subject: Re: [Int-area] Fwd: I-D ACTION:draft-bagnulo-cga-ext-00.txt

Hi Thomas,

El 06/12/2005, a las 15:09, Thomas Narten escribió:

> marcelo bagnulo braun <marcelo <at> it.uc3m.es> writes:
>
>> El 02/12/2005, a las 12:16, Francis Dupont escribió:
>
>>>  In your previous mail you wrote:
>>>
>>>    This is a very simple and short draft that defines a format for CGA
>>>    extensions.
>>>
>>> => IMHO the main interest of the document is its IANA consideration
>>> section, isn't it?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alia Atlas | 13 Dec 2005 02:22
Picon

Fwd: I-D ACTION:draft-atlas-icmp-unnumbered-00.txt

I'd be very interested in any comments on this draft.  It suggests
extending primarily ICMP TTL Exceeded messages for better
troubleshooting with unnumbered interfaces.  The additional
information potentially included are an interface ifIndex and an
interface description string.

Thanks!
Alia

---------- Forwarded message ----------
From: Internet-Drafts <at> ietf.org <Internet-Drafts <at> ietf.org>
Date: Dec 12, 2005 3:50 PM
Subject: I-D ACTION:draft-atlas-icmp-unnumbered-00.txt
To: i-d-announce <at> ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.

        Title           : ICMP Extensions for Unnumbered Interfaces
        Author(s)       : A. Atlas, et al.
        Filename        : draft-atlas-icmp-unnumbered-00.txt
        Pages           : 8
        Date            : 2005-12-12

   This memo defines extensions to ICMP that permit identification of
   unnumbered interfaces.  The interface the IP packet was received upon
   can be identified by appending an ifIndex and/or a string describing
   the interface.  These extensions are defined to facilitate
   troubleshooting in network with unnumbered interfaces and parallel
   links.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Pekka Savola | 13 Dec 2005 07:01
Picon

Re: Fwd: I-D ACTION:draft-atlas-icmp-unnumbered-00.txt

On Mon, 12 Dec 2005, Alia Atlas wrote:
> I'd be very interested in any comments on this draft.  It suggests
> extending primarily ICMP TTL Exceeded messages for better
> troubleshooting with unnumbered interfaces.  The additional
> information potentially included are an interface ifIndex and an
> interface description string.

Application area is going to ask, "how do you internationalize the 
description string?"  That's also part of 
http://www.ietf.org/ID-Checklist.html.

> ---------- Forwarded message ----------
> From: Internet-Drafts <at> ietf.org <Internet-Drafts <at> ietf.org>
> Date: Dec 12, 2005 3:50 PM
> Subject: I-D ACTION:draft-atlas-icmp-unnumbered-00.txt
> To: i-d-announce <at> ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>        Title           : ICMP Extensions for Unnumbered Interfaces
>        Author(s)       : A. Atlas, et al.
>        Filename        : draft-atlas-icmp-unnumbered-00.txt
>        Pages           : 8
>        Date            : 2005-12-12
>
>   This memo defines extensions to ICMP that permit identification of
>   unnumbered interfaces.  The interface the IP packet was received upon
>   can be identified by appending an ifIndex and/or a string describing
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alia Atlas | 13 Dec 2005 07:07
Picon

Re: Fwd: I-D ACTION:draft-atlas-icmp-unnumbered-00.txt

On 12/12/05, Pekka Savola <pekkas <at> netcore.fi> wrote:
> On Mon, 12 Dec 2005, Alia Atlas wrote:
> > I'd be very interested in any comments on this draft.  It suggests
> > extending primarily ICMP TTL Exceeded messages for better
> > troubleshooting with unnumbered interfaces.  The additional
> > information potentially included are an interface ifIndex and an
> > interface description string.
>
> Application area is going to ask, "how do you internationalize the
> description string?"  That's also part of
> http://www.ietf.org/ID-Checklist.html.

I am assuming that one could use different C-types; for instance, one
C-type could be UTF-8 or such as appropriate.  I didn't add that in
because I'm not really familiar with the issues in this area.  Do you
have any recommendations?

Thanks,
Alia
Permalink | Reply | 0 comments |
headers
Mark Townsley | 20 Dec 2005 05:08
Picon
Favicon

BoF requests for Dallas


Apologies in advance for the cross-posting.

We are getting a lot of BoF requests in the int-area. That's not a bad 
thing, but in order to better manage them we would like to enforce the 
following deadlines for the next IETF meeting:

Jan 20 - Creation of a public mailing list for discussion of the BoF 
topic at hand. Please include Margaret and I on this list so that we can 
monitor the discussion.

Feb 3 - Formal request to the ietf-secretary and ADs, cc'd to the 
public mailing list, for the BoF itself. Included in the request should 
be a draft BoF Agenda, if the goal is the formation of a WG a draft 
charter, and a pointer to at least one Internet Draft as reference 
material for the BoF itself. 

Also, please take a look at Thomas' document on how to run a successful 
BoF. This is a brand new document, and Thomas is asking for review and 
discussion (which you can do on the int-area, iab, iesg or ietf list as you 
like) and volunteers to help iterate on the text and ready it for 
publication.

http://www.ietf.org/internet-drafts/draft-narten-successful-bof-00.txt

Thanks!

- Mark and Margaret

PS. Should we make int-chairs a member of int-area and clean-up duplicates (making int-chairs a forced
(Continue reading)

Permalink | Reply | 0 comments |

Gmane