Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs

Hi Jeff,

If you are asking how to go about asking IANA to create a name space, the 
MIB Guidelines
doc discusses this.

http://www.rfc-editor.org/rfc/rfc4181.txt

MIB guidelines also discusses how MIB docs can add new values to these IANA 
maintained TCs.

I don't see the  point in having IANA maintain a TC-MIB, which is never used 
in an
actual RFC MIB.  While this might be easier for you, there is still work by 
someone.
Typically, the IANA considerations section that requests creating a new name 
space,
is included in a MIB document that is advancing to RFC status.   I don't 
know of  acceptions, but
maybe someone else does?

Thanks,
  -Joan

----- Original Message ----- 
From: "Jeff Haas" <jhaas@juniper.net>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: <ietfmibs@ietf.org>
Sent: Saturday, January 14, 2012 11:16 AM
Subject: Re: [IETFMIBS] Extending InetAddress(Type) for BGP Multicast VPNs

> Juergen,
>
> On Jan 10, 2012, at 9:41 AM, Juergen Schoenwaelder wrote:
>> If the reachability info BGP is carrying turns out to be BGP specific,
>> then having a BGP specific TC to represent it seems quite OK. Is any
>> non-BGP protocol using the formats and the encodings I looked at
>> earlier this morning? If not, these formats seems to be rather BGP
>> specific.
>
> It seems that I will be authoring (and probably maintaining) another BGP 
> TC MIB for this purpose.
>
> Could the group share any experiences with MIB documents that note code 
> points by reference?  The BGP protocol suite continues to evolve at a very 
> steady pace and it would be nice if I could point to new code points at 
> IANA rather than having a MIB document that could never be stable enough 
> to really reach an RFC, except perhaps for a snapshot.
>
> -- Jeff
>
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs 