Send arin-tech-discuss mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.arin.net/mailman/listinfo/arin-tech-discuss
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of arin-tech-discuss digest..."


Today's Topics:

   1. Some undefined tags in Net Payload (Marcus Hightower)
   2. Re: Some undefined tags in Net Payload (Brian Rak)
   3. Re: Some undefined tags in Net Payload (Andy Newton)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Jun 2013 11:20:30 -0500
From: Marcus Hightower <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [arin-tech-discuss] Some undefined tags in Net Payload
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I'm trying to create a NET Payload to do a detailed reassignment.
After reading the documentation I'm not real sure how many of the tags are 
needed to do the reassignment.
Do I need to include/update the following tags with values?
originAS
pocLinkRef

Currently the payload looks like:
<net xmlns="http://www.arin.net/regrws/core/v1";>
    <version>4</version>
    <comment>
        <line number=""/>
    </comment>
    <registrationDate></registrationDate>
    <orgHandle>~~~~~</orgHandle>
    <handle></handle>
    <netBlocks>  
      
<netBlock><type>A</type><description>~~~~~~r</description><startAddress>~~~~~~~</startAddress><cidrLength>~~</cidrLength></netBlock>
   </netBlocks>
    <parentNetHandle>~~~~~~~~~</parentNetHandle>
    <netName>~~~~~~~</netName>
    <originASes>
        <originAS/>
    </originASes>
    <pocLinks>
        <pocLinkRef>
        </pocLinkRef>
    </pocLinks>
</net>

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-tech-discuss/attachments/20130618/41223b3b/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 18 Jun 2013 12:39:47 -0400
From: Brian Rak <[email protected]>
To: Marcus Hightower <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-tech-discuss] Some undefined tags in Net Payload
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Not as far as I know.  We send requests with only the following fields:

version
netBlocks
parentNetHandle
netName
orgHandle OR customerHandle

This appears to be the minimum number of entries to get reassignments 
working properly.


On 6/18/2013 12:20 PM, Marcus Hightower wrote:
> I'm trying to create a NET Payload to do a detailed reassignment.
> After reading the documentation I'm not real sure how many of the tags 
> are needed to do the reassignment.
> Do I need to include/update the following tags with values?
> originAS
> pocLinkRef
>
> Currently the payload looks like:
> <net xmlns="http://www.arin.net/regrws/core/v1";>
> <version>4</version>
>     <comment>
>         <line number=""/>
>     </comment>
> <registrationDate></registrationDate>
> <orgHandle>~~~~~</orgHandle>
> <handle></handle>
>     <netBlocks>
> <netBlock><type>A</type><description>~~~~~~r</description><startAddress>~~~~~~~</startAddress><cidrLength>~~</cidrLength></netBlock>
>    </netBlocks>
> <parentNetHandle>~~~~~~~~~</parentNetHandle>
> <netName>~~~~~~~</netName>
>     <originASes>
> <originAS/>
> </originASes>
>     <pocLinks>
> <pocLinkRef>
> </pocLinkRef>
>     </pocLinks>
> </net>
>
> Thanks
>
>
> _______________________________________________
> arin-tech-discuss mailing list
> [email protected]
> http://lists.arin.net/mailman/listinfo/arin-tech-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-tech-discuss/attachments/20130618/44be67f0/attachment-0001.html>

------------------------------

Message: 3
Date: Tue, 18 Jun 2013 17:52:02 +0000
From: Andy Newton <[email protected]>
To: Brian Rak <[email protected]>, Marcus Hightower
        <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-tech-discuss] Some undefined tags in Net Payload
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Thanks, Brian. You beat me to it. Neither originAS nor the pocLinks are 
required.

Andy Newton,
Chief Engineer, ARIN

From: Brian Rak <[email protected]<mailto:[email protected]>>
Date: Tuesday, June 18, 2013 12:39 PM
To: Marcus Hightower <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [arin-tech-discuss] Some undefined tags in Net Payload

Not as far as I know.  We send requests with only the following fields:

version
netBlocks
parentNetHandle
netName
orgHandle OR customerHandle

This appears to be the minimum number of entries to get reassignments working 
properly.


On 6/18/2013 12:20 PM, Marcus Hightower wrote:
I'm trying to create a NET Payload to do a detailed reassignment.
After reading the documentation I'm not real sure how many of the tags are 
needed to do the reassignment.
Do I need to include/update the following tags with values?
originAS
pocLinkRef

Currently the payload looks like:
<net xmlns="http://www.arin.net/regrws/core/v1";>
    <version>4</version>
    <comment>
        <line number=""/>
    </comment>
    <registrationDate></registrationDate>
    <orgHandle>~~~~~</orgHandle>
    <handle></handle>
    <netBlocks>
      
<netBlock><type>A</type><description>~~~~~~r</description><startAddress>~~~~~~~</startAddress><cidrLength>~~</cidrLength></netBlock>
   </netBlocks>
    <parentNetHandle>~~~~~~~~~</parentNetHandle>
    <netName>~~~~~~~</netName>
    <originASes>
        <originAS/>
    </originASes>
    <pocLinks>
        <pocLinkRef>
        </pocLinkRef>
    </pocLinks>
</net>

Thanks



_______________________________________________
arin-tech-discuss mailing list
[email protected]<mailto:[email protected]>http://lists.arin.net/mailman/listinfo/arin-tech-discuss



-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-tech-discuss/attachments/20130618/895955e3/attachment-0001.html>

------------------------------

_______________________________________________
arin-tech-discuss mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-tech-discuss


End of arin-tech-discuss Digest, Vol 29, Issue 9
************************************************

Reply via email to