From Ron.Grimes at qwest.com Tue Jun 7 13:45:19 2011 From: Ron.Grimes at qwest.com (Grimes, Ronald) Date: Tue, 7 Jun 2011 12:45:19 -0500 Subject: [arin-tech-discuss] Restful web service for Swipping Message-ID: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B517@qtomaexmbm22.AD.QINTRA.COM> Hi Tim, I work with Centurylink/ Qwest Communications we are working on getting our systems ready to support swipping under the restful webservice process ARIN is implementing. One of the questions we have is what we could possibly see as responses to our call to the webservice? Could you all assist with information around that? Thanks, Ron ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From timc at arin.net Thu Jun 9 08:04:21 2011 From: timc at arin.net (Tim Christensen) Date: Thu, 9 Jun 2011 12:04:21 +0000 Subject: [arin-tech-discuss] Restful web service for Swipping In-Reply-To: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B517@qtomaexmbm22.AD.QINTRA.COM> Message-ID: Greetings Ron, The responses to the Registration RWS are outlined in the Methods document, with greater detail regarding response content in the Payload document, found at https://www.arin.net/resources/restful-interfaces.html (see the box on the right, ?RESTful Provisioning Downloads?). These documents are undergoing revision at this time to improve their clarity and utility, and will be published soon. Your question is context-dependent, i.e., the responses will depend on how and what you?re asking the web service for. As a general rule, your response will take the form of: * An HTTP status 200 series response, indicating success; your response will contain a payload of the type indicated by the Methods document * An HTTP status 400 series response, indicating a client error, such as a bad request or content problem * An HTTP status 500 series response, indicating a server error, such as Service Unavailable (we try not to let this happen, obviously) For SWIPs, see the Methods document section labeled ?Create Recipient Org? (for Reallocates and Detail-Reassigns), ?Create Recipient Customer? (for Simple-Reassigns), ?Reallocate?, and ?Reassign?. Note that each method denotes that a successful request will return both an HTTP response and an attached Payload, specific to the call that you make to the service. Best regards, Tim Christensen ARIN Engineering On 6/7/11 1:45 PM, "Grimes, Ronald" said: Hi Tim, I work with Centurylink/ Qwest Communications we are working on getting our systems ready to support swipping under the restful webservice process ARIN is implementing. One of the questions we have is what we could possibly see as responses to our call to the webservice? Could you all assist with information around that? Thanks, Ron ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ron.Grimes at qwest.com Thu Jun 9 08:11:26 2011 From: Ron.Grimes at qwest.com (Grimes, Ronald) Date: Thu, 9 Jun 2011 07:11:26 -0500 Subject: [arin-tech-discuss] Restful web service for Swipping In-Reply-To: References: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B517@qtomaexmbm22.AD.QINTRA.COM> Message-ID: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B52D@qtomaexmbm22.AD.QINTRA.COM> Do you know how long it will be before these documents will be updated to be more user friendly? From: Tim Christensen [mailto:timc at arin.net] Sent: Thursday, June 09, 2011 8:04 AM To: Grimes, Ronald; 'arin-tech-discuss at arin.net' Cc: Zhao, Sean Subject: Re: Restful web service for Swipping Greetings Ron, The responses to the Registration RWS are outlined in the Methods document, with greater detail regarding response content in the Payload document, found at https://www.arin.net/resources/restful-interfaces.html (see the box on the right, "RESTful Provisioning Downloads"). These documents are undergoing revision at this time to improve their clarity and utility, and will be published soon. Your question is context-dependent, i.e., the responses will depend on how and what you're asking the web service for. As a general rule, your response will take the form of: * An HTTP status 200 series response, indicating success; your response will contain a payload of the type indicated by the Methods document * An HTTP status 400 series response, indicating a client error, such as a bad request or content problem * An HTTP status 500 series response, indicating a server error, such as Service Unavailable (we try not to let this happen, obviously) For SWIPs, see the Methods document section labeled "Create Recipient Org" (for Reallocates and Detail-Reassigns), "Create Recipient Customer" (for Simple-Reassigns), "Reallocate", and "Reassign". Note that each method denotes that a successful request will return both an HTTP response and an attached Payload, specific to the call that you make to the service. Best regards, Tim Christensen ARIN Engineering On 6/7/11 1:45 PM, "Grimes, Ronald" said: Hi Tim, I work with Centurylink/ Qwest Communications we are working on getting our systems ready to support swipping under the restful webservice process ARIN is implementing. One of the questions we have is what we could possibly see as responses to our call to the webservice? Could you all assist with information around that? Thanks, Ron ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ron.Grimes at qwest.com Thu Jun 9 08:29:25 2011 From: Ron.Grimes at qwest.com (Grimes, Ronald) Date: Thu, 9 Jun 2011 07:29:25 -0500 Subject: [arin-tech-discuss] Restful web service for Swipping In-Reply-To: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B52D@qtomaexmbm22.AD.QINTRA.COM> References: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B517@qtomaexmbm22.AD.QINTRA.COM> <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B52D@qtomaexmbm22.AD.QINTRA.COM> Message-ID: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B52E@qtomaexmbm22.AD.QINTRA.COM> Hi Tim, I went through the document and saw the following on page 22 (in attachment). These are some of the details we are looking for. We are not seeing error messages like this come back in production. Do you know if this is currently working? Do you know if there are any plans to make these error messages more specific? Thanks, Ron From: Grimes, Ronald Sent: Thursday, June 09, 2011 8:11 AM To: 'Tim Christensen'; 'arin-tech-discuss at arin.net' Cc: Zhao, Sean Subject: RE: Restful web service for Swipping Do you know how long it will be before these documents will be updated to be more user friendly? From: Tim Christensen [mailto:timc at arin.net] Sent: Thursday, June 09, 2011 8:04 AM To: Grimes, Ronald; 'arin-tech-discuss at arin.net' Cc: Zhao, Sean Subject: Re: Restful web service for Swipping Greetings Ron, The responses to the Registration RWS are outlined in the Methods document, with greater detail regarding response content in the Payload document, found at https://www.arin.net/resources/restful-interfaces.html (see the box on the right, "RESTful Provisioning Downloads"). These documents are undergoing revision at this time to improve their clarity and utility, and will be published soon. Your question is context-dependent, i.e., the responses will depend on how and what you're asking the web service for. As a general rule, your response will take the form of: * An HTTP status 200 series response, indicating success; your response will contain a payload of the type indicated by the Methods document * An HTTP status 400 series response, indicating a client error, such as a bad request or content problem * An HTTP status 500 series response, indicating a server error, such as Service Unavailable (we try not to let this happen, obviously) For SWIPs, see the Methods document section labeled "Create Recipient Org" (for Reallocates and Detail-Reassigns), "Create Recipient Customer" (for Simple-Reassigns), "Reallocate", and "Reassign". Note that each method denotes that a successful request will return both an HTTP response and an attached Payload, specific to the call that you make to the service. Best regards, Tim Christensen ARIN Engineering On 6/7/11 1:45 PM, "Grimes, Ronald" said: Hi Tim, I work with Centurylink/ Qwest Communications we are working on getting our systems ready to support swipping under the restful webservice process ARIN is implementing. One of the questions we have is what we could possibly see as responses to our call to the webservice? Could you all assist with information around that? Thanks, Ron ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. ________________________________ This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Error Codes.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 11564 bytes Desc: Error Codes.docx URL: From timc at arin.net Thu Jun 9 10:04:10 2011 From: timc at arin.net (Tim Christensen) Date: Thu, 9 Jun 2011 14:04:10 +0000 Subject: [arin-tech-discuss] Restful web service for Swipping In-Reply-To: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B52E@qtomaexmbm22.AD.QINTRA.COM> Message-ID: On 6/9/11 8:29 AM, "Grimes, Ronald" said: > I went through the document and saw the following on page 22 (in attachment). > These are some of the details we are looking for. We are not seeing error > messages like this come back in production. Do you know if this is currently > working? Yes. These messages appear in the Error Payload that is returned in the *body* of the HTTP Response. For example, I tried to perform a GET on a POC record to which a bogus API key does not have access (e.g., would produce an authentication failure) by issuing a GET such as: http://www.arin.net/rest/poc/ARIN-HOSTMASTER?apikey=API-BOGUS And received an HTTP response of "400 Bad Request", containing the following Error Payload in the HTTP body: E_AUTHENTICATION The API key specified was missing or invalid. > Do you know if there are any plans to make these error messages more specific? These messages are intended to provide a categorical indication of the problem. The reason for the specific error is informed by examining the specific URI, inbound payload, and comparison to the published XML schemas that are available in the same location where you found the Methods and Payloads documents. > Do you know how long it will be before these documents will be updated to be > more user friendly? One focus of the document update is to address this particular issue: how to contextually correlate an error using the Payload, XML Schema, and other documentation so that you can understand and resolve errors readily. Revising the document is an active work item right now, but must also go thru publishing and approval. In the meantime, you may continue to ask questions here on ARIN-Tech-Discuss. Please know that your questions and feedback are very valuable: they indicate to us what areas of the documentation need to be improved or refined. Best regards, Tim Christensen ARIN Engineering From Ron.Grimes at qwest.com Thu Jun 9 16:28:29 2011 From: Ron.Grimes at qwest.com (Grimes, Ronald) Date: Thu, 9 Jun 2011 15:28:29 -0500 Subject: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7, Issue 3 In-Reply-To: <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB247A@qtdenexmbm20.AD.QINTRA.COM> References: <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB247A@qtdenexmbm20.AD.QINTRA.COM> Message-ID: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B53F@qtomaexmbm22.AD.QINTRA.COM> Hi Tim, Could you please look at the below. We do not seem to be receiving the "Codes" for errors below? Could you help us out with this concern? Thanks, Ron -----Original Message----- From: Zhao, Sean Sent: Thursday, June 09, 2011 4:24 PM To: Grimes, Ronald Subject: RE: arin-tech-discuss Digest, Vol 7, Issue 3 Ron, I sent an xml with an empty I got an exception instead of error message. Here is the xml I sent 4 NET-208-44-0-0-1 Q0609-208-44-99-48 S 208.44.99.48 29 209 But instead of getting an xml error message, I got this, "Server returned HTTP response code: 400 for URL: https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey" Second time I sent an xml with orgHandle, 4 BNO NET-63-144-0-0-1 Q0609-63-146-48-0 S 63.146.48.0 29 209 I got a good an xml returned, like following, 29 Reassigned 063.146.048.007 063.146.048.000 S NET-63-146-48-0-1 Q0609-63-146-48-0 BNO AS209 NET-63-144-0-0-1 2011-06-09T16:11:13.059-04:00 4 Thanks, Sean Zhao Sean.Zhao at CenturyLink.com -----Original Message----- From: arin-tech-discuss-bounces at arin.net [mailto:arin-tech-discuss-bounces at arin.net] On Behalf Of arin-tech-discuss-request at arin.net Sent: Thursday, June 09, 2011 12:00 PM To: arin-tech-discuss at arin.net Subject: arin-tech-discuss Digest, Vol 7, Issue 3 Send arin-tech-discuss mailing list submissions to arin-tech-discuss at arin.net 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 arin-tech-discuss-request at arin.net You can reach the person managing the list at arin-tech-discuss-owner at arin.net When replying, please edit your Subject line so it is more specific than "Re: Contents of arin-tech-discuss digest..." Today's Topics: 1. Re: Restful web service for Swipping (Tim Christensen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Jun 2011 14:04:10 +0000 From: Tim Christensen To: "Grimes, Ronald" , "'arin-tech-discuss at arin.net'" Cc: "Zhao, Sean" Subject: Re: [arin-tech-discuss] Restful web service for Swipping Message-ID: Content-Type: text/plain; charset="us-ascii" On 6/9/11 8:29 AM, "Grimes, Ronald" said: > I went through the document and saw the following on page 22 (in attachment). > These are some of the details we are looking for. We are not seeing error > messages like this come back in production. Do you know if this is currently > working? Yes. These messages appear in the Error Payload that is returned in the *body* of the HTTP Response. For example, I tried to perform a GET on a POC record to which a bogus API key does not have access (e.g., would produce an authentication failure) by issuing a GET such as: http://www.arin.net/rest/poc/ARIN-HOSTMASTER?apikey=API-BOGUS And received an HTTP response of "400 Bad Request", containing the following Error Payload in the HTTP body: E_AUTHENTICATION The API key specified was missing or invalid. > Do you know if there are any plans to make these error messages more specific? These messages are intended to provide a categorical indication of the problem. The reason for the specific error is informed by examining the specific URI, inbound payload, and comparison to the published XML schemas that are available in the same location where you found the Methods and Payloads documents. > Do you know how long it will be before these documents will be updated to be > more user friendly? One focus of the document update is to address this particular issue: how to contextually correlate an error using the Payload, XML Schema, and other documentation so that you can understand and resolve errors readily. Revising the document is an active work item right now, but must also go thru publishing and approval. In the meantime, you may continue to ask questions here on ARIN-Tech-Discuss. Please know that your questions and feedback are very valuable: they indicate to us what areas of the documentation need to be improved or refined. Best regards, Tim Christensen ARIN Engineering ------------------------------ _______________________________________________ arin-tech-discuss mailing list arin-tech-discuss at arin.net http://lists.arin.net/mailman/listinfo/arin-tech-discuss End of arin-tech-discuss Digest, Vol 7, Issue 3 *********************************************** This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. From timc at arin.net Thu Jun 9 18:52:38 2011 From: timc at arin.net (Tim Christensen) Date: Thu, 9 Jun 2011 22:52:38 +0000 Subject: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7, Issue 3 In-Reply-To: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B53F@qtomaexmbm22.AD.QINTRA.COM> Message-ID: Hello Ron, On 6/9/11 4:28 PM, "Grimes, Ronald" said: > Hi Tim, > > Could you please look at the below. We do not seem to be receiving the > "Codes" for errors below? Could you help us out with this concern? > > I sent an xml with an empty > I got an exception instead of error message. Here is the xml I sent > > > > 4 > > NET-208-44-0-0-1 > Q0609-208-44-99-48 > > > S > 208.44.99.48 > 29 > > > > 209 > > > > But instead of getting an xml error message, I got this, "Server returned HTTP > response code: 400 for URL: > https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey" Along with this HTTP 400 response, you would have received an Error Payload in the body of the response. (I just ran your transaction, and got the Error Payload below). It is possible that the client you are using may not be providing these Error Payloads if the HTTP response is not in the 200 group; if that is so, you will need to use a REST client that properly provides Error Payloads on all HTTP responses. Check the BODY to see if it was returned. This Error Payload would have contained the following content: element "netBlock" not allowed in this context element "originAS" not allowed in this context E_SCHEMA_VALIDATION The XML payload did not validate against the defined schema. Please see the documentation for details. Note that the error indicates that the XML payload you sent did not validate against the schema definition, and refers you to the documentation. In examining this particular issue, refer to the Methods document, page 10 and following regarding the "Reassign" method (specifically, the Detailed Reassignment), which indicate that the orgHandle is required, and other rules applicable to a Detailed Reassignment (middle of page 11). As an aside, the reason that the message does not come back with "orgHandle is not provided" or something like that, is because many different things (different methods, containing different payload elements) are serviced by any given XML schema. The software is making its best guess at what might be wrong in the "additionalInfo" collection (e.g., netBlock and originAS not allowed), under the assumption that what you provided was accurate. In this case, though, following the referral to the documentation and ensuring conformance to the Methods, Payloads, and XML Schemas is your best bet (which is what Sean did next, by providing the required orgHandle.) Continuing... > > Second time I sent an xml with orgHandle, > > > > 4 > BNO > NET-63-144-0-0-1 > Q0609-63-146-48-0 > > > S > 63.146.48.0 > 29 > > > > 209 > > > > I got a good an xml returned, like following, > > > > > > > 29 > Reassigned > 063.146.048.007 > 063.146.048.000 > S > > > NET-63-146-48-0-1 > Q0609-63-146-48-0 > BNO > > AS209 > > NET-63-144-0-0-1 > > 2011-06-09T16:11:13.059-04:00 > 4 > > This indicates that your client IS returning payloads when the HTTP status is in the 200 group. As I mentioned earlier, your client may not be supporting payloads in the body when the HTTP status is in the 400 or 500 class (client error, server error). You'll have to use one that properly supports response bodies under all HTTP status codes. For testing one-off REST submissions, you may want to consider using a client that is known to provide the proper responses. Among those that we use internally at ARIN are RESTClient from WizTools and the Simple Rest Client for Chrome. Best regards, Tim Christensen ARIN Engineering From Sean.Zhao at qwest.com Mon Jun 13 16:37:33 2011 From: Sean.Zhao at qwest.com (Zhao, Sean) Date: Mon, 13 Jun 2011 14:37:33 -0600 Subject: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7, Issue 3 In-Reply-To: References: <78E7F8A80646E842BE3AD5D0B0F1D3EB36C9E8B53F@qtomaexmbm22.AD.QINTRA.COM> Message-ID: <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB272A@qtdenexmbm20.AD.QINTRA.COM> Ron, That is cool. I modify my research code. It does return an error xml after throw me an exception 400. I closed the connection right after I got an exception. The error xml is like this E_BAD_REQUESTPlease specify only one, either orgHandle or customerHandle.customerHandle/orgHandleThis method requires certain parameters. Please see the documentation for details. Tim, thanks for your info. Very, very helpful. Thanks, Sean Zhao Sean.Zhao at CenturyLink.com -----Original Message----- From: Tim Christensen [mailto:timc at arin.net] Sent: Thursday, June 09, 2011 6:53 PM To: Grimes, Ronald; 'arin-tech-discuss at arin.net' Cc: Zhao, Sean; Ravibalan Pillai, Mithun Subject: Re: arin-tech-discuss Digest, Vol 7, Issue 3 Hello Ron, On 6/9/11 4:28 PM, "Grimes, Ronald" said: > Hi Tim, > > Could you please look at the below. We do not seem to be receiving the > "Codes" for errors below? Could you help us out with this concern? > > I sent an xml with an empty > I got an exception instead of error message. Here is the xml I sent > > > > 4 > > NET-208-44-0-0-1 > Q0609-208-44-99-48 > > > S > 208.44.99.48 > 29 > > > > 209 > > > > But instead of getting an xml error message, I got this, "Server returned HTTP > response code: 400 for URL: > https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey" Along with this HTTP 400 response, you would have received an Error Payload in the body of the response. (I just ran your transaction, and got the Error Payload below). It is possible that the client you are using may not be providing these Error Payloads if the HTTP response is not in the 200 group; if that is so, you will need to use a REST client that properly provides Error Payloads on all HTTP responses. Check the BODY to see if it was returned. This Error Payload would have contained the following content: element "netBlock" not allowed in this context element "originAS" not allowed in this context E_SCHEMA_VALIDATION The XML payload did not validate against the defined schema. Please see the documentation for details. Note that the error indicates that the XML payload you sent did not validate against the schema definition, and refers you to the documentation. In examining this particular issue, refer to the Methods document, page 10 and following regarding the "Reassign" method (specifically, the Detailed Reassignment), which indicate that the orgHandle is required, and other rules applicable to a Detailed Reassignment (middle of page 11). As an aside, the reason that the message does not come back with "orgHandle is not provided" or something like that, is because many different things (different methods, containing different payload elements) are serviced by any given XML schema. The software is making its best guess at what might be wrong in the "additionalInfo" collection (e.g., netBlock and originAS not allowed), under the assumption that what you provided was accurate. In this case, though, following the referral to the documentation and ensuring conformance to the Methods, Payloads, and XML Schemas is your best bet (which is what Sean did next, by providing the required orgHandle.) Continuing... > > Second time I sent an xml with orgHandle, > > > > 4 > BNO > NET-63-144-0-0-1 > Q0609-63-146-48-0 > > > S > 63.146.48.0 > 29 > > > > 209 > > > > I got a good an xml returned, like following, > > > > > > > 29 > Reassigned > 063.146.048.007 > 063.146.048.000 > S > > > NET-63-146-48-0-1 > Q0609-63-146-48-0 > BNO > > AS209 > > NET-63-144-0-0-1 > > 2011-06-09T16:11:13.059-04:00 > 4 > > This indicates that your client IS returning payloads when the HTTP status is in the 200 group. As I mentioned earlier, your client may not be supporting payloads in the body when the HTTP status is in the 400 or 500 class (client error, server error). You'll have to use one that properly supports response bodies under all HTTP status codes. For testing one-off REST submissions, you may want to consider using a client that is known to provide the proper responses. Among those that we use internally at ARIN are RESTClient from WizTools and the Simple Rest Client for Chrome. Best regards, Tim Christensen ARIN Engineering This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. From jenmar3434 at yahoo.com Tue Jun 14 13:14:03 2011 From: jenmar3434 at yahoo.com (Jen) Date: Tue, 14 Jun 2011 12:14:03 -0500 Subject: [arin-tech-discuss] arin-tech-discuss Jennifer marshall In-Reply-To: References: Message-ID: <9F02BC29-EF38-4A44-9297-334BBA098268@yahoo.com> could someone tell me what my iP address is my Internet provider keeps telling me it starts with 184. but when I use the utilities on my Mac it says I am redirected to 192.168.78. 2. I am not a computer savy person at all. but why am I getting redirected does that mean something?? any help would be appreciated. also I printed out something that looks strange it appears that 64.4.61.212 through port 1863 has been trying to connect to me On Jun 14, 2011, at 11:00 AM, arin-tech-discuss-request at arin.net wrote: > Send arin-tech-discuss mailing list submissions to > arin-tech-discuss at arin.net > > 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 > arin-tech-discuss-request at arin.net > > You can reach the person managing the list at > arin-tech-discuss-owner at arin.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of arin-tech-discuss digest..." > > > Today's Topics: > > 1. Re: arin-tech-discuss Digest, Vol 7, Issue 3 (Zhao, Sean) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Jun 2011 14:37:33 -0600 > From: "Zhao, Sean" > To: "'Tim Christensen'" , "Grimes, Ronald" > , "'arin-tech-discuss at arin.net'" > > Cc: "Ravibalan Pillai, Mithun" > Subject: Re: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7, > Issue 3 > Message-ID: > <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB272A at qtdenexmbm20.AD.QINTRA.COM> > > Content-Type: text/plain; charset="iso-8859-1" > > Ron, > That is cool. I modify my research code. It does return an error xml after throw me an exception 400. I closed the connection right after I got an exception. The error xml is like this > E_BAD_REQUESTPlease specify only one, either orgHandle or customerHandle.customerHandle/orgHandleThis method requires certain parameters. Please see the documentation for details. > > Tim, thanks for your info. Very, very helpful. > > > Thanks, > > Sean Zhao > Sean.Zhao at CenturyLink.com > > > -----Original Message----- > From: Tim Christensen [mailto:timc at arin.net] > Sent: Thursday, June 09, 2011 6:53 PM > To: Grimes, Ronald; 'arin-tech-discuss at arin.net' > Cc: Zhao, Sean; Ravibalan Pillai, Mithun > Subject: Re: arin-tech-discuss Digest, Vol 7, Issue 3 > > Hello Ron, > > On 6/9/11 4:28 PM, "Grimes, Ronald" said: > >> Hi Tim, >> >> Could you please look at the below. We do not seem to be receiving the >> "Codes" for errors below? Could you help us out with this concern? >> > >> I sent an xml with an empty >> I got an exception instead of error message. Here is the xml I sent >> >> >> >> 4 >> >> NET-208-44-0-0-1 >> Q0609-208-44-99-48 >> >> >> S >> 208.44.99.48 >> 29 >> >> >> >> 209 >> >> >> >> But instead of getting an xml error message, I got this, "Server returned HTTP >> response code: 400 for URL: >> https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey" > > Along with this HTTP 400 response, you would have received an Error Payload > in the body of the response. (I just ran your transaction, and got the Error > Payload below). It is possible that the client you are using may not be > providing these Error Payloads if the HTTP response is not in the 200 group; > if that is so, you will need to use a REST client that properly provides > Error Payloads on all HTTP responses. Check the BODY to see if it was > returned. > > This Error Payload would have contained the following content: > > > > element "netBlock" not allowed in this context > element "originAS" not allowed in this context > > E_SCHEMA_VALIDATION > > The XML payload did not validate against the defined > schema. Please see the documentation for details. > > > Note that the error indicates that the XML payload you sent did not validate > against the schema definition, and refers you to the documentation. > > In examining this particular issue, refer to the Methods document, page 10 > and following regarding the "Reassign" method (specifically, the Detailed > Reassignment), which indicate that the orgHandle is required, and other > rules applicable to a Detailed Reassignment (middle of page 11). > > As an aside, the reason that the message does not come back with "orgHandle > is not provided" or something like that, is because many different things > (different methods, containing different payload elements) are serviced by > any given XML schema. The software is making its best guess at what might > be wrong in the "additionalInfo" collection (e.g., netBlock and originAS not > allowed), under the assumption that what you provided was accurate. In this > case, though, following the referral to the documentation and ensuring > conformance to the Methods, Payloads, and XML Schemas is your best bet > (which is what Sean did next, by providing the required orgHandle.) > Continuing... > >> >> Second time I sent an xml with orgHandle, >> >> >> >> 4 >> BNO >> NET-63-144-0-0-1 >> Q0609-63-146-48-0 >> >> >> S >> 63.146.48.0 >> 29 >> >> >> >> 209 >> >> >> >> I got a good an xml returned, like following, >> >> >> >> >> >> >> 29 >> Reassigned >> 063.146.048.007 >> 063.146.048.000 >> S >> >> >> NET-63-146-48-0-1 >> Q0609-63-146-48-0 >> BNO >> >> AS209 >> >> NET-63-144-0-0-1 >> >> 2011-06-09T16:11:13.059-04:00 >> 4 >> >> > > This indicates that your client IS returning payloads when the HTTP status > is in the 200 group. As I mentioned earlier, your client may not be > supporting payloads in the body when the HTTP status is in the 400 or 500 > class (client error, server error). You'll have to use one that properly > supports response bodies under all HTTP status codes. > > For testing one-off REST submissions, you may want to consider using a > client that is known to provide the proper responses. Among those that we > use internally at ARIN are RESTClient from WizTools and the Simple Rest > Client for Chrome. > > Best regards, > Tim Christensen > ARIN Engineering > > > This communication is the property of Qwest and may contain confidential or > privileged information. Unauthorized use of this communication is strictly > prohibited and may be unlawful. If you have received this communication > in error, please immediately notify the sender by reply e-mail and destroy > all copies of the communication and any attachments. > > > ------------------------------ > > _______________________________________________ > arin-tech-discuss mailing list > arin-tech-discuss at arin.net > http://lists.arin.net/mailman/listinfo/arin-tech-discuss > > > End of arin-tech-discuss Digest, Vol 7, Issue 5 > *********************************************** From andy at arin.net Tue Jun 14 13:31:51 2011 From: andy at arin.net (Andy Newton) Date: Tue, 14 Jun 2011 17:31:51 +0000 Subject: [arin-tech-discuss] arin-tech-discuss Jennifer marshall In-Reply-To: <9F02BC29-EF38-4A44-9297-334BBA098268@yahoo.com> References: <9F02BC29-EF38-4A44-9297-334BBA098268@yahoo.com> Message-ID: Jennifer, RFC 1918 defines all addresses within 192.168.xxx.xxx as private IP space. This address is most likely being supplied to your computer from your cable or wireless router. Your router translates and aggregates requests from these addresses into a single, publicly routable IP address given to your router from your ISP. To find the publicly routable IP address your router is using, go to http://www.arin.net and look at the very top where it says "Your IP address is". Andy Newton Chief Engineer, ARIN On Jun 14, 2011, at 1:14 PM, Jen wrote: > could someone tell me what my iP address is my Internet provider keeps telling me it starts with 184. but when I use the utilities on my Mac it says I am redirected to 192.168.78. 2. I am not a computer savy person at all. but why am I getting redirected does that mean something?? any help would be appreciated. also I printed out something that looks strange it appears that 64.4.61.212 through port 1863 has been trying to connect to me > > > > On Jun 14, 2011, at 11:00 AM, arin-tech-discuss-request at arin.net wrote: > >> Send arin-tech-discuss mailing list submissions to >> arin-tech-discuss at arin.net >> >> 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 >> arin-tech-discuss-request at arin.net >> >> You can reach the person managing the list at >> arin-tech-discuss-owner at arin.net >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of arin-tech-discuss digest..." >> >> >> Today's Topics: >> >> 1. Re: arin-tech-discuss Digest, Vol 7, Issue 3 (Zhao, Sean) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 13 Jun 2011 14:37:33 -0600 >> From: "Zhao, Sean" >> To: "'Tim Christensen'" , "Grimes, Ronald" >> , "'arin-tech-discuss at arin.net'" >> >> Cc: "Ravibalan Pillai, Mithun" >> Subject: Re: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7, >> Issue 3 >> Message-ID: >> <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB272A at qtdenexmbm20.AD.QINTRA.COM> >> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Ron, >> That is cool. I modify my research code. It does return an error xml after throw me an exception 400. I closed the connection right after I got an exception. The error xml is like this >> E_BAD_REQUESTPlease specify only one, either orgHandle or customerHandle.customerHandle/orgHandleThis method requires certain parameters. Please see the documentation for details. >> >> Tim, thanks for your info. Very, very helpful. >> >> >> Thanks, >> >> Sean Zhao >> Sean.Zhao at CenturyLink.com >> >> >> -----Original Message----- >> From: Tim Christensen [mailto:timc at arin.net] >> Sent: Thursday, June 09, 2011 6:53 PM >> To: Grimes, Ronald; 'arin-tech-discuss at arin.net' >> Cc: Zhao, Sean; Ravibalan Pillai, Mithun >> Subject: Re: arin-tech-discuss Digest, Vol 7, Issue 3 >> >> Hello Ron, >> >> On 6/9/11 4:28 PM, "Grimes, Ronald" said: >> >>> Hi Tim, >>> >>> Could you please look at the below. We do not seem to be receiving the >>> "Codes" for errors below? Could you help us out with this concern? >>> >> >>> I sent an xml with an empty >>> I got an exception instead of error message. Here is the xml I sent >>> >>> >>> >>> 4 >>> >>> NET-208-44-0-0-1 >>> Q0609-208-44-99-48 >>> >>> >>> S >>> 208.44.99.48 >>> 29 >>> >>> >>> >>> 209 >>> >>> >>> >>> But instead of getting an xml error message, I got this, "Server returned HTTP >>> response code: 400 for URL: >>> https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey" >> >> Along with this HTTP 400 response, you would have received an Error Payload >> in the body of the response. (I just ran your transaction, and got the Error >> Payload below). It is possible that the client you are using may not be >> providing these Error Payloads if the HTTP response is not in the 200 group; >> if that is so, you will need to use a REST client that properly provides >> Error Payloads on all HTTP responses. Check the BODY to see if it was >> returned. >> >> This Error Payload would have contained the following content: >> >> >> >> element "netBlock" not allowed in this context >> element "originAS" not allowed in this context >> >> E_SCHEMA_VALIDATION >> >> The XML payload did not validate against the defined >> schema. Please see the documentation for details. >> >> >> Note that the error indicates that the XML payload you sent did not validate >> against the schema definition, and refers you to the documentation. >> >> In examining this particular issue, refer to the Methods document, page 10 >> and following regarding the "Reassign" method (specifically, the Detailed >> Reassignment), which indicate that the orgHandle is required, and other >> rules applicable to a Detailed Reassignment (middle of page 11). >> >> As an aside, the reason that the message does not come back with "orgHandle >> is not provided" or something like that, is because many different things >> (different methods, containing different payload elements) are serviced by >> any given XML schema. The software is making its best guess at what might >> be wrong in the "additionalInfo" collection (e.g., netBlock and originAS not >> allowed), under the assumption that what you provided was accurate. In this >> case, though, following the referral to the documentation and ensuring >> conformance to the Methods, Payloads, and XML Schemas is your best bet >> (which is what Sean did next, by providing the required orgHandle.) >> Continuing... >> >>> >>> Second time I sent an xml with orgHandle, >>> >>> >>> >>> 4 >>> BNO >>> NET-63-144-0-0-1 >>> Q0609-63-146-48-0 >>> >>> >>> S >>> 63.146.48.0 >>> 29 >>> >>> >>> >>> 209 >>> >>> >>> >>> I got a good an xml returned, like following, >>> >>> >>> >>> >>> >>> >>> 29 >>> Reassigned >>> 063.146.048.007 >>> 063.146.048.000 >>> S >>> >>> >>> NET-63-146-48-0-1 >>> Q0609-63-146-48-0 >>> BNO >>> >>> AS209 >>> >>> NET-63-144-0-0-1 >>> >>> 2011-06-09T16:11:13.059-04:00 >>> 4 >>> >>> >> >> This indicates that your client IS returning payloads when the HTTP status >> is in the 200 group. As I mentioned earlier, your client may not be >> supporting payloads in the body when the HTTP status is in the 400 or 500 >> class (client error, server error). You'll have to use one that properly >> supports response bodies under all HTTP status codes. >> >> For testing one-off REST submissions, you may want to consider using a >> client that is known to provide the proper responses. Among those that we >> use internally at ARIN are RESTClient from WizTools and the Simple Rest >> Client for Chrome. >> >> Best regards, >> Tim Christensen >> ARIN Engineering >> >> >> This communication is the property of Qwest and may contain confidential or >> privileged information. Unauthorized use of this communication is strictly >> prohibited and may be unlawful. If you have received this communication >> in error, please immediately notify the sender by reply e-mail and destroy >> all copies of the communication and any attachments. >> >> >> ------------------------------ >> >> _______________________________________________ >> arin-tech-discuss mailing list >> arin-tech-discuss at arin.net >> http://lists.arin.net/mailman/listinfo/arin-tech-discuss >> >> >> End of arin-tech-discuss Digest, Vol 7, Issue 5 >> *********************************************** > _______________________________________________ > arin-tech-discuss mailing list > arin-tech-discuss at arin.net > http://lists.arin.net/mailman/listinfo/arin-tech-discuss From markk at arin.net Fri Jun 17 16:15:13 2011 From: markk at arin.net (Mark Kosters) Date: Fri, 17 Jun 2011 20:15:13 +0000 Subject: [arin-tech-discuss] Maintenance Notice on the OT&E/Beta Registration System Message-ID: On June 20, 2011 from 8:00AM until 12:00PM EDT, the OT&E/Beta Registration System will be down for maintenance. All production services will remain in operation before, during, and after this maintenance period. Regards, Mark Kosters ARIN CTO