- db-wg - mailman.ripe.net

Re: Internet Draft Submission (fwd)
by Gabor Kiss 23 Feb '96

23 Feb '96

> > George Eddy writes : > >From eddy(a)ISI.EDU Thu Feb 22 22:12:26 1996 > Date: Thu, 22 Feb 96 13:07:22 PST > Posted-Date: Thu, 22 Feb 96 13:07:22 PST > Message-Id: <9602222107.AA16189(a)kit.isi.edu> > From: George Eddy <eddy(a)ISI.EDU> > To: rps(a)ISI.EDU > Subject: Internet Draft Submission > Geographic Location Extension to Ripe-181 > 3.2 Direct and Indirect Location > > This method proposes the addition of a ``location'' attribute to the > aut-num as in 3.1. This attribute could directly hold the LocString, or > the name of a ``location'' object. The location object could be defined > as: > > location: [mandatory] [single] > loc-string: [mandatory] [single] > descr: [optional] [multiple] > notify: [optional] [multiple] > mnt-by: [optional] [multiple] > changed: [mandatory] [multiple] > source: [mandatory] [single] > > Using the example in section 3.1, we would have the following: > > aut-num: AS8800 > location: IrvineCA > ... > > and the object ``IrvineCA'' would be: > > location: IrvineCA > loc-string: 33 40 10n 117 49 20w 10m > descr: Example location object in Irvine, CA. > notify: eddy(a)isi.edu > mnt-by: MAINT-EXAMPLE > changed: eddy(a)isi.edu 960220 > source: EXAMPLE > > The loc-name could be any string desired by the creator. Dear Eddy, Can two or more AS-es share the same location object? How to coordinate the loc-name assignments. In Europe tipically there are more then one AS within the same city. They will race for the simple name of the city. Just like for domain names. :-/ Maybe the RIPE predefine location objects for the main cities. Regards Gabor

2 1

Internet Draft Submission (fwd)
by David.Kessens＠ripe.net 23 Feb '96

23 Feb '96

> George Eddy writes :

2 1

Internet Draft Submission
by George Eddy 22 Feb '96

22 Feb '96

Internet Draft Rusty Eddy Expires August 27, 1996 USC/ISI draft-ietf-rps-location-00.txt February, 1996 Geographic Location Extension to Ripe-181 Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as ``work in progress.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 1. Introduction This document describes two proposals for specifying geographic location of a database objects such as an Autonomous System (AS). This information could be used by mapping tools that provide geographic maps of the Internet topology. Two alternatives are documented here, the first proposal uses a new attribute added to a database object. The attribute provides longitude, latitude and size information. The second method also uses a new location attribute added to the database object, this new attribute contains the name of a location object that we propose. The two methods describe direct and indirect location information respectively. 2. Format of Location String The format of the geographic ``location string'' or LocString will be a single string consisting of the latitude, longitude and optionally the size. The latitude and longitude are each represented by one to three integers corresponding to degrees, minutes and seconds, with a direction appended to the final integers of the latitude and longitude. If minutes and/or seconds are not provided values of 0 will be assumed and size will default to 0, a point. The directions are north, south, east and west. Rusty Eddy Expires August 27, 1996 [Page 1] Internet Draft Geographic Location Extension to Ripe-181 February, 1996 For example, the LocString for Irvine, California is: 33 40 10n 117 49 20w 10m Representing 33 degrees, 40 minutes and 10 seconds north latitude, and 117 degrees, 49 minutes and 20 seconds west longitude with a 10 meter encompassing circle. Informally the LocString would be of the form: "LA [MM [SS]](n|s) LO [MM [SS]](e|w) [SIm]" Where, LA and LO are integers representing the degrees latitude and longitude, respectively. MM is an integer representing the number of minutes. SS is an integer representing the number of seconds. The characters 'n', 's', 'e', 'w' and 'm' are literals corresponding to north, south, east, west and meters, respectively. 3. Proposals for AS Geographic Location The following proposals are similar, the first suggests a new attribute to the Ripe-181[1] aut-num object, the second also suggests new aut-num attribute and a new ``location'' object. The following examples use the aut-num object, however, they may be equally applied to the as-macro, inet-rtr or route objects as well. Attributing locations to these other database objects would provide the geographic topology internal to an AS, which may represent reality more accurately. 3.1 Direct Location This method proposes a new aut-num attribute, ``location''. This attribute is a single, optional attribute: aut-num: [mandatory] [single] ... location: [optional] [single] The ``location'' attribute will contain a LocString. For example, say AS8800 is an ISP in Irvine, California, it's aut-num could contain the following: aut-num: AS8800 location: 33 40 10n 117 49 20w ... 3.2 Direct and Indirect Location This method proposes the addition of a ``location'' attribute to the aut-num as in 3.1. This attribute could directly hold the LocString, or Rusty Eddy Expires August 27, 1996 [Page 2] Internet Draft Geographic Location Extension to Ripe-181 February, 1996 the name of a ``location'' object. The location object could be defined as: location: [mandatory] [single] loc-string: [mandatory] [single] descr: [optional] [multiple] notify: [optional] [multiple] mnt-by: [optional] [multiple] changed: [mandatory] [multiple] source: [mandatory] [single] Using the example in section 3.1, we would have the following: aut-num: AS8800 location: IrvineCA ... and the object ``IrvineCA'' would be: location: IrvineCA loc-string: 33 40 10n 117 49 20w 10m descr: Example location object in Irvine, CA. notify: eddy(a)isi.edu mnt-by: MAINT-EXAMPLE changed: eddy(a)isi.edu 960220 source: EXAMPLE The loc-name could be any string desired by the creator. 4. Problems One obvious problem with using geographic layout inherent to networks, is that they often span large geographic areas, this is true of many ISPs. When attributing a location to an AS, one must pick a single location to be representative of the AS. The internal topology of an AS may be mapped geographically when a location attribute has been added to the inet-rtr or route objects. 5. Conclusion The motivation for providing geographic locations was prompted by the development of the Internet Routing Registry (IRR) visualization tool (IRRv) as a possible method for topological layout. Methods for obtaining the LocString are beyond the scope of this document, however, it should be noted that RFC 1876[2] specifies a means for containing location information in Domain Name System. Also worth noting is a ``Geographic Nameserver'' at http://www.mit.edu:8001/geo, that derives its information from the Geographic Nameserver database on martini.eecs.umich.edu. Rusty Eddy Expires August 27, 1996 [Page 3] Internet Draft Geographic Location Extension to Ripe-181 February, 1996 Work in this area will proceed if the community finds this feature useful. 6. Thanks Although we have never spoke, I would like to thank, Juergen Schoenwaelder (schoenw(a)ibr.cs.tu-bs.de) for the development of scotty/tkined, which IRRv is based on and the example geographic layout script. Thanks also to Cengiz Alaettinoglu for suggestions that led to these proposals. [1] T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, and J. Yu. Representation of IP Routing Policies in a Routing Registry. Technical Report ripe-181, RIPE, RIPE NCC, Amsterdam, Netherlands, October 1994. [2] C. Davis, P. Vixie, T. Goodwin, and I. Dickinson. A Means for Expressing Location Information in the Domain Name System, RFC 1876, January 1996. Author's Present Address Rusty Eddy Information Sciences Institute University of Southern California Marina del Rey, CA 90292 e-mail: eddy(a)isi.edu

1 0

Re: draft NOC/role object proposal
by M.H.Behringer＠dante.org.uk 26 Jan '96

26 Jan '96

David, Thanks for starting the discussion on this. I have some input to this, see below. Unfortunately I won't be able to come to the RIPE WG-sessions, but Steven Bakker will be there. At 5:17 pm 26/1/1996, David.Kessens(a)ripe.net wrote: >Dear all, > >We have the creation of NOC/role object as one of the action points for >the RIPE NCC. However, after consulting numerous people we seemed to have >agreed upon something where we don't have any specification for ;-(. >Therefore, I am now doing a proposal for how the object could look like. >Note that this proposal is a real draft due to my personal ignorance of >your real needs in this area and the time that went by when we last >discussed the contents of this object for the last time... > > >Problem description: > >We see more and more person objects in the database that are apparently >not persons but referrals to help desks or ISP NOCs. The problem with the >usage of person objects for this matter is that the person object isn't >really designed for this and that in certain cases we require certain >objects to point to real persons for accountability reasons. Usage of >non-persons in person objects undermines therefore the usability of the >RIPE database. However, it is quite obvious that there is a need for such >an object, especially for larger organizations. > > >Proposal: > > >Since the object will be derived from the 'person:' object I will only >describe *all* the differences between the 'person:' object and the >'role:' object. > > >Attributes that are not used: > > >person: - for obvious reasons >nic-hdl: - a NIC handle is by definition assigned to persons and not > to organizations. Since we don't expect too many people > using this object it seems reasonable that we don't use a > number as a unique identifier. If we will need it in the > future we can add it. > > >Additional attributes: > >role: - the name of the object itself > >admin-c: - as in 'mntner' objects >tech-c: - as in 'mntner' objects > > We could decide to leave the 'tech-c:' out, since what's > the point in having a technical contact for a > administrative object only anyway ? I think we should not distinguish. A "person:" attribute would do, I think (however you call it, eg tech-c; the point is: *one* such object). Besides, this is mainly for NOCs and such (at least this is what we would use it for), so it would be technical people on it anyway only. But I think we need more attributes. Basically the role object needs to reflect what you need to know about something like a NOC: Who's in it (as you say), how to contact (might be derived from the other attributes), but also: What are the out-of-hours procedures. There are several possible ways to include that. I would propose something like: role: [mandatory] [single] address: [mandatory] [multiple] (as in person) phone: [mandatory] [multiple] ( " ) fax-no: [optional] [multiple] ( " ) e-mail: [optional] [multiple] ( " ) trouble: [optional] [multiple] (this is needed for trouble contact) (see below) person: [mandatory] [multiple] (this should be handles, obviously) (I see you used tech-c for this purpose, that is basically the same) remarks: [optional] [multiple] (as in person) notify: [optional] [multiple] ( " ) mnt-by: [optional] [multiple] ( " ) changed: [mandatory] [multiple] ( " ) source: [mandatory] [single] ( " ) What was actually the difference between notify and mnt-by? Do we need both? If feel quite strongly that we need something where you can specify the procedure to get in touch with the "role". This could be for example: trouble: Working days 0900-1700 CET: phone: xxx trouble: Working days 0900-1700 CET: e-mail: xxx trouble: Working days 0900-1700 CET: fax: xxx trouble: other times: phone: xxx trouble: other times: pager: xxx trouble: other times: mobile phone: xxx trouble: if all fails: phone: xxx trouble: NOTE: Please always try the phone before paging us! ... and so on. I don't think it is adviseable to be too precise in the specification, as there are certainly folks out there who want to put in notes like above. Thus one attribute like this "trouble" with free content would do. The reason why I think we still need such an attribute: We would like to be able to automatically derive contact procedures from the RIPE DB, to use it as a list. Of course we can also put it in the remarks, but I think one of the reasons for this object is to have this sort of attribute. > > >How to reference the 'role:' object from an object: > > >Here we can opt for two different solutions: > >1) We can allow people to use the 'role:' object in tech-c/zone-c > attributes (not in admin-c, this one can only point to a human due to > our current assignment criteria) > >2) Use a special attribute. The attribute will be an optional, single > line attribute for all objects that currently have an > 'admin-c:/tech-c:/zone-c:' attribute defined (including the role/NOC > object if desired. Note that this can cause undesired loops...): > > Example: > > preferred-contact: > > Please advise on better and shorter names, but that makes clear that > it is intended that a customer first checks with NOC/role object > people. I strongly feel that we should go away from specifying individuals in the other objects such as "route" or "as-num". But obviously not everybody will do that. Therefore I would suggest to use the tech-c: attribute for that. It makes perfect sense to say "tech-c: DFN-NOC" for example. Admin can stay, I don't have a strong view on that. The special attribute you propose in 2) makes it only more complicated, and it doesn't actually give us anything, does it? Hopefully people will not do something like specifying persons *and* a role as tech-c's in one object, but it shouldn't create problems either, you only might get a person twice as output. > > >How does the lookup work: > >The RIPE database can be configured for objects that have references to >other objects in such a way that it will also show the referenced objects >when querying an object with referenced other objects. Since the NOC >object itself can have references to persons/roles, it seems best to do >such a recursive lookup only one level deep whenever we find a NOC/person >object referenced. > >Examples: > >$ whois 193/8 > > inetnum: 193.0.0.0 > admin-c: DK13-RIPE > tech-c: RIPE-NOC > [...] > > person: David Kessens > nic-hdl: DK13-RIPE > [...] > > role: RIPE-NOC > tech-c: DK58 > [...] > >and > >$ whois RIPE-NOC > > role: RIPE-NOC > tech-c: DK58 > [...] > > person: Daniel Karrenberg > nic-hdl: DK58 > [...] Agree. Looks fine. Basically with the role object the goal is to get away from individuals, so the one-level limited recursion makes perfect sense, imo. > > >We hope that this draft is useful enough for you all to let us define a >sound proposal for the NOC/role object. Please make as many >amendments/added features as you want and that you think is needed for >the object, > >Kind regards, > >David Kessens >RIPE NCC What do others think? Michael

1 0

draft NOC/role object proposal
by David.Kessens＠ripe.net 26 Jan '96

26 Jan '96

Dear all, We have the creation of NOC/role object as one of the action points for the RIPE NCC. However, after consulting numerous people we seemed to have agreed upon something where we don't have any specification for ;-(. Therefore, I am now doing a proposal for how the object could look like. Note that this proposal is a real draft due to my personal ignorance of your real needs in this area and the time that went by when we last discussed the contents of this object for the last time... Problem description: We see more and more person objects in the database that are apparently not persons but referrals to help desks or ISP NOCs. The problem with the usage of person objects for this matter is that the person object isn't really designed for this and that in certain cases we require certain objects to point to real persons for accountability reasons. Usage of non-persons in person objects undermines therefore the usability of the RIPE database. However, it is quite obvious that there is a need for such an object, especially for larger organizations. Proposal: Since the object will be derived from the 'person:' object I will only describe *all* the differences between the 'person:' object and the 'role:' object. Attributes that are not used: person: - for obvious reasons nic-hdl: - a NIC handle is by definition assigned to persons and not to organizations. Since we don't expect too many people using this object it seems reasonable that we don't use a number as a unique identifier. If we will need it in the future we can add it. Additional attributes: role: - the name of the object itself admin-c: - as in 'mntner' objects tech-c: - as in 'mntner' objects We could decide to leave the 'tech-c:' out, since what's the point in having a technical contact for a administrative object only anyway ? How to reference the 'role:' object from an object: Here we can opt for two different solutions: 1) We can allow people to use the 'role:' object in tech-c/zone-c attributes (not in admin-c, this one can only point to a human due to our current assignment criteria) 2) Use a special attribute. The attribute will be an optional, single line attribute for all objects that currently have an 'admin-c:/tech-c:/zone-c:' attribute defined (including the role/NOC object if desired. Note that this can cause undesired loops...): Example: preferred-contact: Please advise on better and shorter names, but that makes clear that it is intended that a customer first checks with NOC/role object people. How does the lookup work: The RIPE database can be configured for objects that have references to other objects in such a way that it will also show the referenced objects when querying an object with referenced other objects. Since the NOC object itself can have references to persons/roles, it seems best to do such a recursive lookup only one level deep whenever we find a NOC/person object referenced. Examples: $ whois 193/8 inetnum: 193.0.0.0 admin-c: DK13-RIPE tech-c: RIPE-NOC [...] person: David Kessens nic-hdl: DK13-RIPE [...] role: RIPE-NOC tech-c: DK58 [...] and $ whois RIPE-NOC role: RIPE-NOC tech-c: DK58 [...] person: Daniel Karrenberg nic-hdl: DK58 [...] We hope that this draft is useful enough for you all to let us define a sound proposal for the NOC/role object. Please make as many amendments/added features as you want and that you think is needed for the object, Kind regards, David Kessens RIPE NCC

1 0

Hierarchical authorization proposal
by David.Kessens＠ripe.net 26 Jan '96

26 Jan '96

Dear all, We are already talking for quite some time about a hierarchical authorization scheme for objects in the RIPE database that need protection against creating objects in somebody else's address/domain space. Hereby, I want to describe the requirements for such a new feature and two possible solutions. Problem description: Currently, we see more and more problems with objects that are (usually by accident) created in another registries address space or problems with domain objects where people think that a domain is delegated to them when they have send a domain object to the RIPE database. It seems that, since we are using to much time for this kind of issues, the time has arrived that we need to solve the problem. Requirements: Objects that are directly located in a predefined hierarchy under a certain object need an extra authorization step before they can be created. The authorization step should be defined by the object that is located in the hierarchy directly above the object. The authorization step will be done on all objects that are located directly above the object if we have more then one object directly above the object (this should generally not be the case). The hierarchical authorization step seems not to be needed (yet) for updating/deleting an object in the hierarchy. However, the design should be able to be extended in such a way that this feature can be added in the future if the need arises. Currently we are dealing with three hierarchies: 1) Domain space hierarchy The definition of the domain hierarchy is straight forward: A domain consists of text strings concatenated with dots An domain is 'above' another domain when all text strings match with the other domain from the right and they are not the same. An domain is 'directly above' another domain when it is above the other domain and differs only with one text string. The definition for '(directly) below' another domain follows from the definition for above: An domain is '(directly) below' another domain when the other domain is above the domain. Example: 'x1.office.ripe.net' is below 'ripe.net' 'x1.office.ripe.net' is directly below 'office.ripe.net' 'ripe.net' is above 'x1.office.ripe.net' 'office.ripe.net' is directly above 'x1.office.ripe.net' 2) IP address space range hierarchy for 'inetnum:' objects An IP address space range is a little bit more complicated since we can have overlapping ranges: A range is 'above' another range when the range is larger then the other range and it overlaps it completely. A range is 'directly above' another range when it is the smallest possible range that is still above the object. The definition for '(directly) below' another range follows from the definition for above: A range is '(directly) below' another range when the other range is above the range. People might consider that there exists a problem when we are dealing with partially overlapping ranges (not possible with prefix notation ranges but are possible with normal IP address space range notation). However, the definition handles this problem gracefully: a range can only below or above another range when they overlap each other *completely*. Example: In IP address space range notation: '194.0.0.0 - 194.255.255.255' is 'above' '194.5.20.0 - 194.5.20.255' '194.5.20.0 - 194.5.23.255' is only 'directly above' '194.5.20.0 - 194.5.20.255' when there are no other ranges that are bigger and also 'above' '194.5.20.0 - 194.5.20.255'. '194.5.20.0 - 194.5.20.255' is 'below' '194.0.0.0 - 194.255.255.255' '194.5.20.0 - 194.5.20.255' is only 'directly below' '194.5.20.0 - 194.5.23.255' when there are no other ranges that are 'above' '194.5.20.0 - 194.5.20.255' and 'below' '194.5.20.0 - 194.5.23.255'. In prefix notation ranges: '194/8' is 'above' '194.5.20/24' '194.5.20/22' is only 'directly above' '194.5.20/24' when there are no other ranges that are bigger and also 'above' '194.5.20/24'. '194.5.20/24' is 'below' '194/8' '194.5.20/24' is only 'directly below' '194.5.20/22' when there are no other ranges that are 'above' '194.5.20/24' and 'below' '194.5.20/22'. 3) Route object hierarchy At first sight a 'route:' object has the same hierarchy as for 'inetnum:' objects. However, a 'route:' object has in fact a two level hierarchy: The origin AS object is always the object directly above a certain 'route:' object. An all route objects with a given origin are always directly below the origin AS object. Proposed solutions: 1) New attribute for hierarchical organized objects: Add an optional multiple line attribute to hierarchical organized objects that points to the maintainer object which authorization scheme will be used when an object will be created 'directly below' the object. mnt-lower: MAINTAINER [ ( CREATE & CHANGE & DELETE ) ] MAINTAINER - The maintainer that defines the authorization scheme to be used when an object 'directly below' in the hierarchy from the object, that has defined this attribute, will be created in addition to the authorization schemes that are defined in the to be created object itself. The maintainer will optionally be followed by a specification upon which events the authorization needs to be used: CREATE - perform the authorization step when an object is created 'directly below' the object. CHANGE - perform the authorization step when an object is changed 'directly below' the object. DELETE - perform the authorization step when an object is deleted 'directly below' the object. When no events are specified, the default behavior will be used, that is: perform the authorization only upon creation of objects directly below the object. This attribute is optional for objects that have a hierarchy defined. Currently, there is a hierarchy defined for: 'domain', 'route' and 'inetnum' objects. Multiple attributes may be defined and will mean that at least one of the authorization methods as mentioned in the referenced maintainers should allow the database update. Example: RIPE can have the following object: inetnum: 194.0.0.0 - 194.255.255.255 descr: RIPE - ALLOCATED BLOCK mnt-by: RIPE-NCC-MNT mnt-lower: RIPE-NCC-MNT (CREATE | DELETE) RIPE can allocate address space to a local registry and hand over the authority for the address space below. Note that the registry can not delete or create it's allocated address space object but may change it's contents. inetnum: 194.10.0.0 - 194.10.255.255 descr: ALLOCATED BLOCK to LOCAL REGISTRY mnt-by: LOCAL-REGISTRY-MNT mnt-lower: LOCAL-REGISTRY-MNT (CREATE | DELETE) Then the registry can register it's customers as follows: inetnum: 194.10.3.0 - 194.10.3.255 descr: CUSTOMER of local registry The customer may change their object but cannot create/delete it: 2) New attribute for maintainer object: Another solution would be to add an optional multiple line 'scope:' attribute to the maintainer object that will specify that the authorization scheme should be used when objects are created, changed or deleted 'directly below' the object that references the maintainer. At first glance, this solution looks attractive but will not allow for hand-over of authority as can be done in the first proposal. scope: WORKINGAREA [ ( CREATE & CHANGE & DELETE ) ] WORKINGAREA - Can be LOCAL or LOWER. LOCAL is the default behavior and is the same as the 'maintainer' object currently works. LOWER would do the authorization step when objects are created, changed or deleted directly below the hierarchical object that references the maintainer. CREATE, CHANGE, DELETE will work as specified in the previous proposal. Note that it will also extend the possibilities for the maintainers when used in LOCAL mode (the way maintainers work now): 'LOCAL (CREATE & CHANGE & DELETE)' matches the current maintainer behavior. The attribute is optional for maintainer objects. We could decide to allow the use of this attribute also for the hierarchical organized objects. It will then override the default behavior as specified in the maintainer object. The attribute can be used twice: one time for the LOCAL scope and one time for the hierarchical authorization method (LOWER). Example: RIPE can have the following object: inetnum: 194.0.0.0 - 194.255.255.255 descr: RIPE - ALLOCATED BLOCK mnt-by: RIPE-NCC-MNT mntner: RIPE-NCC-MNT scope: LOCAL (CREATE & CHANGE & DELETE) scope: LOWER (CREATE & DELETE) RIPE can allocate address space to a local registry and hand over the authority for the address space as below. Note that the registry can not delete or create it's allocated address space object but may change it's contents. inetnum: 194.10.0.0 - 194.10.255.255 descr: ALLOCATED BLOCK to LOCAL REGISTRY mnt-by: LOCAL-REGISTRY-MNT mntner: LOCAL-REGISTRY-MNT scope: LOCAL (CREATE & CHANGE & DELETE) scope: LOWER (CREATE & DELETE) Then the registry can register it's customers as follows: inetnum: 194.10.3.0 - 194.10.3.255 descr: CUSTOMER of LOCAL registry The customer may change their object but cannot create/delete it: Discussion: Both proposals solve the problem. Both proposals will have the same implementation complexity. But there of course also some differences: Proposal 1: This solution is probably clearest and easiest to the user by using a special attribute in the objects in the hierarchy itself instead of hiding it in the maintainer object. Of course this is also the weakness: a maintainer object that looks the same may behave differently depending on the context in which it is used. Also, when we introduce the new scheme many objects need an update (this might be an advantage or an disadvantage depending on how you view things...). Furthermore, most objects will again get an extra attribute defined. Proposal 2: The mechanism is hidden for the user and therefore might be less clear. The maintainer object will be the only object that defines authorization policies. We can introduce the mechanism rapidly by just adding an attribute to the maintainer object (In RIPE's case: we only need to add an attribute to our maintainer object to protect the whole RIPE database against unauthorized allocations/assignments in our space). We don't get extra attributes defined for the normal objects. Note that we think that we should choose the best mechanism, even if introducing might be somewhat more complex. The extra workload for proposal one seems not that much more. Expected implementation problems: Implementation for the IP address space notation ranges that are used in 'inetnum' objects will not be trivial due to the internal workings of the database for 'classless' lookups. You probably don't know the details but for the people that are interested: The IP address space ranges are internally converted to prefix notation. When, they don't fit in one prefix, more prefixes are generated. In that case we can get in trouble with overlapping objects that might be found as directly above instead of the correct object. I think it is possible to solve but it will needs some more work then expected at first sight. Please let us know if there exist better solutions or that changes are needed, or just make your choice! David Kessens RIPE NCC

1 0

RIPE Action 21.9: Fwd: E-J B: Draft doc m.cast router in routing reg.
by Wilfried Woeber, UniVie/ACOnet 25 Jan '96

25 Jan '96

FYI, this is the original proposal as circulated by Erik-Jan Bos. -Wilfried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Subject: Draft document multicast router in routing registry From: Erik-Jan Bos <erik-jan.bos(a)surfnet.nl> Date: Sun, 07 May 1995 11:49:46 +0200 Mbone-EU, please find below a first version of a document describing a multicast router in a routing registry. I would like to have your comments and we can discuss it at the next Mbone WG meeting. I realize some of you might not have a chance to read it before the meeting. Well... here it is, I'll try to bring copies to the meeting. See you in Rome. --- Start of document A Multicast Router in the Routing Registry Erik-Jan Bos Document ID: ripe-nnn May, 1995 **** DRAFT ** WORK IN PROGRESS ** DRAFT **** ABSTRACT This document describes an addition to ripe-122 (Specifying an "Internet Router" in the Routing Registry) in which it is possible to define a multicast capable Internet routing within a routing registry. 1. Introduction With the growing of the Mbone worldwide, managing the Mbone becomes a complex task. The multicast-bone is starting to suffer from problems that used to be present in the unicast-bone several years ago, such as routing coordination. Today, registries are available for administering policies and routes and routers [1]. Tools are availble [2,3] for checking and analyzing the real world against what is registered. The Mbone could and should benefit from these technologies coming from the unicast world. The features of the specification described in this document will be usable e.g. in the RIPE Data Base, after review by the RIPE Data Base WG. After implementation tools could be developed for mapping and analyzing the Mbone. Furthermore, administrative details (such as contact person) are easily administered by well known procedures and easily retrievable. 2. Multicast routers versus unicast routers An "Internet Router" or a "gateway" in the current version of IP (IPv4) can be defined as follows [4]: "Gateways in the Internet form a cooperative, interconnected structure. Datagrams pass from gateway to gateway until they reach a gateway that can deliver the datagram directly." This definition can be applied to both unicast and multicast routers. Since both a unicast and multicast router are fulfilling the "Internet Router" function for different natures of traffic, there is no need for a special routing registry data base object. Moreover, both functions could be present in the same box. 3. Multicast router specification Since an Internet Router can perform both types of routing, this fact should be registerable in the routing registry. Each router is uniquely defined by by its object name, also known as the fully qualified domain name. Below is an example of a internet router object, specifying a multicast router: inet-rtr: broodjeham.surfnet.nl localas: AS1103 ifaddr: 192.87.106.102 255.255.255.0 ifaddr: 192.87.4.99 255.255.255.0 mpeer: 192.87.108.13 16 1 admin-c: Erik-Jan Bos tech-c: Henk Steenman notify: netmaster(a)surfnet.nl remarks: SURFnet Multicast router changed: Erik-Jan.Bos(a)surfnet.nl 950505 source: RIPE Several pieces of important information are present in this object. First of all there is the FQDN of the router, acting as object name. The Home Autonomous System Number is shown, which for a multicast router is merely for identification purposes only. Furthermore, the ifaddr:-lines show that this router has two interfaces, in two different networks. Finally, the DVMRP peers are shown with IP address, treshold and metric. All other attributes are common to other objects already defined for a routing registry [1]. For exact syntax definition see next chapter. 4. Multicast router Syntax Definition The multicast capable router object is defined here. Each of the possible attributes are shown, on a single line. The second column defined whether the attribute must be present [mandatory] of could be present [optional]. The third column defines whether exactly one line is allowed [single] or that more than one line of the same attribute is allowed [multiple]. In case an attribute has more lines than one, the name of the attribute must be repeated on each line. inet-rtr: [mandatory] [single] localas: [mandatory] [single] ifaddr: [mandatory] [multiple] mpeer: [mandatory] [multiple] admin-c: [mandatory] [multiple] tech-c: [mandatory] [multiple] notify: [optional] [multiple] remarks: [optional] [multiple] changed: [mandatory] [multiple] source: [mandatory] [single] Each attribute has the following syntax: inet-rtr: The fully qualified domain name of the router. localas: The Autonomous System to which the router belongs. ifaddr: An interface IPv4 address of the router. mpeer: A multicast peering of the router. Format: <mpeer address> <mpeer treshold> <mpeer metric> Example: mpeer: 192.87.108.13 16 1 Status: mandatory, multiple instances allowed. admin-c: Full name or uniquely assigned NIC-handle of a contact person for administrative matters. tech-c: Full name or uniquely assigned NIC-handle of a contact person for technical matters. notify: An e-mail address to which notifications of changes to this object should be send. remarks: Remarks or comments, for clarification purposes only. changed: The e-mail address and date of a change. source: Source of the information. 5. Acknowledgements This specification, being an addition to ripe-122, leans on the specification done by the author of ripe-122. Credits go to Tony Bates. Furthermore, the RIPE Mbone WG has done reviewing of this document and they receive credits as well. 6. Security considerations Security is not considered in this document. 7. References [1] Bates, Tony, "Specifying an Internet Router in the Routing Registry", ripe-122, October 1994. On-line at URL: ftp://ftp.ripe.net/ripe/docs/ripe-122.txt [2] PRIDE Tools Release 1. On-line at URL: ftp://ftp.ripe.net/pride/tools/pride-tools-1.tar.Z [3] Merit Inc. RRDB Tools. On-line at URL: ftp://rrdb.merit.edu/pub/meritrr [4] Douglas Comer, "Internetworking with TCP/IP", Prentice-Hall, 1988. ISBN: 0-13-470188-7. --- End of document __ Erik-Jan. --------------------------------------------------------------------------------

1 0

RIPE Action 21.9: proposal for an ext. of inet-rtr (Mbone R.)
by Wilfried Woeber, UniVie/ACOnet 25 Jan '96

25 Jan '96

There is a fairly old action on Eric-Jan and me to circulate a proposal on extending the definition for the RIPE Database router object inet-rtr: The original definition is documented in ripe-122. The background for the proposed extension is the discussion about documenting the routing of "overlay" networks, most prominently the Mbone. Quite a while ago Erik-Jan Bos circulated a proposal to extend inet-rtr: with an mpeer: attribute. This proposed mpeer: attribute is/was intended to specifically document Mbone DVMRP tunnels. [ I'm going to re-distribute this paper in a separate message for those of you who don't have a copy readily available ] Further discussion revealed that by rearranging and extending the definition of the *existing* peer: attribute there is a possibility to make the concept even more general and potentially covering IP over IP, STUN, whatever. At the same time we could avoid inventing just another attribute. The current use of the attribute is: peer: <Peer address> <Peer AS> <Routing Protocol> [localAS ASnumber] The generalisation would involve changing that definition to peer: <Peer address> <Peer protocol> <peer-proto-specific info> So for the good old BGP peering this might then look like: peer: 192.87.4.6 BGP4 AS2122 localAS AS2121 for an Mbone tunnel this might be peer: 192.87.4.6 DVMRP metric thresh and for an IP-over-IP even peer: 192.87.4.6 IP Unfortunately this approach would require a non-compatible change to the existing peer: attribute. How many tools would be affected? What's the expected effort to fix these tools? Your opinions and input wrt to the concept and the proposal to change the peer: definiton for BGP peerings is appreciated - before we spend too much effort on the details.... Regards Wilfried -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

1st draft: proposed agenda - DB-WG at RIPE 23, Amsterdam
by Wilfried Woeber, UniVie/ACOnet 25 Jan '96

25 Jan '96

This is the 1st proposal of a draft agenda for the Database-WG at RIPE 23 in Amsterdam. **Message to the NCC WG scheduling department: If at all possible - please have the DB-WG meeting slot(s) scheduled near the end of the WG stream(s). Thank you! I'd propose to have 2 sessions, - one for the more formal items (A. - D., Y., Z.) and - another one for the more general aspects (E., F., G.). The "general aspects" session should probably precede the formal one. As always, additons, comments, etc. welcome! Apologies if I missed something obvious... See you, Wilfried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Draft Agenda: Database-WG, RIPE 23, Amsterdam, NL ------------------------------------------------------ A. Administrative stuff - volunteering of the scribe - WG-agenda bashing B. DB-SW report - general status report - "realtime" shadowing - hierarchical authorisation for creation and update - backlink implementation - automatic handle assignment C. DB-Objects and attributes - referral mechanisms and distribution of authoritative data - stored/processed attribute (A: 19.12) - do we want/need a registry object? - mcast extensions for inet-rtr:, peer: attribute (A: ) - ROLE/NOC object, handling of lookup recursion - URL attribute? (credits for the idea to Erik-Jan Bos) D. Copyright for the RIPE-DB proposal to have every whois query return % data is copyrighted, and a pointer to the (C) definition of comment and/or meta-characters (%, #, *) ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ E. Databases and registries interoperation brainstorming about needs, methods,... the 192 review project by B.Manning quality control of data, duplicates alert, fuzzy matching... uniqueness of names across databases (AS macros, route) references to data in a different database common update mechanism for "all" databases (multiple source: values? auto forwarding?) proposal for a coordinated development project? F. User Interfaces Tools online documentation G. Authentication and security ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Y. Input from other WGs Z. AOB Draft 1.0, 23-JAN-1996 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 1

2nd draft: proposed agenda - DB-WG at RIPE 23, Amsterdam
by Wilfried Woeber, UniVie/ACOnet 24 Jan '96

24 Jan '96

This is the 2nd proposal of a draft agenda for the Database-WG at RIPE 23 in Amsterdam. Thanks to David who identified the lack of an item on the country: attribute. For consistency reasons we propose to move the item on the use of URLs next to "referral" and to aggregate stuff that requires input from other WGs at the end. Changes are marked with the bar "|" character. I'd propose to have 2 sessions, - one for the more formal items (A. - D., Y., Z.) and - another one for the more general aspects (E., F., G.). The "general aspects" session should probably precede the formal one. As always, additons, comments, etc. welcome! See you, Wilfried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Draft Agenda: Database-WG, RIPE 23, Amsterdam, NL ------------------------------------------------------ A. Administrative stuff - volunteering of the scribe - WG-agenda bashing B. DB-SW report - general status report - "realtime" shadowing - hierarchical authorisation for creation and update - backlink implementation - automatic handle assignment C. DB-Objects and attributes - referral mechanisms and distribution of authoritative data | - URL attribute? (credits for the idea to Erik-Jan Bos) - stored/processed attribute (A: 19.12) | - country: attribute, semantics (and syntax?) - ROLE/NOC object, handling of lookup recursion D. Copyright for the RIPE-DB proposal to have every whois query return % data is copyrighted, and a pointer to the (C) definition of comment and/or meta-characters (%, #, *) ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ E. Databases and registries interoperation brainstorming about needs, methods,... the 192 review project by B.Manning quality control of data, duplicates alert, fuzzy matching... uniqueness of names across databases (AS macros, route) references to data in a different database common update mechanism for "all" databases (multiple source: values? auto forwarding?) proposal for a coordinated development project? F. User Interfaces Tools online documentation G. Authentication and security ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Y. Input from other WGs | - combined registry/maintainer object? (input from the Local-IR WG) | - mcast extensions for inet-rtr:, peer: attribute (A: ) Z. AOB Draft 1.1, 24-JAN-1996 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0